Can an S3 bucket be moved to another AWS account without changing its URL?

S3 does not provide a bucket-ownership transfer feature. The usual migration is to create a new bucket in your account, copy the objects and settings, update access policies, and switch the application and URLs. Deleting the old bucket and trying to recreate the same name is risky because another account could claim the name first.

Treat this as a migration and plan an overlap period if possible: copy the objects, replicate or recopy changes, test permissions and URLs, update consumers, and only then retire the old bucket. If the current owner can keep the old bucket available during the transition, that greatly reduces the chance of broken links.

For the application itself, centralize the bucket name or endpoint in configuration rather than hard-coding it throughout the codebase. A parameter store entry or another managed configuration value can point to the new bucket after the data has been copied. You will still need to handle existing externally published URLs, but this makes the application cutover much safer.

The bigger issue is that production systems are using raw S3 URLs as permanent identifiers. Move the content to a bucket you control, then put a stable layer such as a custom domain, CloudFront distribution, or application configuration in front of it. That way, a future bucket change does not require editing every stored URL.