Copying a file or a folder into another bucket used to work only when the two buckets were close relatives. Now one question decides every copy: can S3 do this itself?

• •Across regions now works. S3 refuses a plain server-side copy between regions, and that refusal used to surface as a failure with no useful explanation. Those copies now take the route that does work.
• •Across accounts works from the file browser, for buckets connected under different credentials.
• •It is much faster. When S3 can do the copy itself, we ask it to and the data does not pass through BucketPilot on that path. Measured on a cross-region copy: 10.7 MB/s before, 96 MB/s after, across eight parallel lanes.

The same helper now decides this for backup and migration jobs, which had been assuming the opposite answer — so a same-account backup that S3 could have done for free no longer pays to move the data through us.

Copies between different providers — S3 to R2, Azure, or one of your own servers — still run as a job, because there is no provider that can do that copy on its own.