Thank you for the additional detail and feedback – I’ve shared it with our Product Management team. And yes, to your point, perhaps not ideal for your need but you can replicate a bucket and then delete the original so you’re then only using the newer bucket.

Thanks for the reply. I looked at the new feature and it doesn’t quite seem to fit the “migration” usevase. From what I gather from the blogpost, one still needs to create a new bucket in the new DC and replicate the files there. Then (I assume) the replication could be disabled and the original bucket removed. However, I would still need to make sure to update all app keys, paths to the bucket etc wherever it’s used. What I’m looking for is a transparent migration of data from one DC to the other, without needing to change app keys, bucket names etc. Also, as a feedback for the replication, I would prefer that to be the case as well. Why do I need 2 different buckets with their own access control just because it’s in two different regions at the same time?

Thanks for the shoutout about Universal Data Migration. Regarding your use case of copying from US to EU DC, we’re currently private beta testing Cloud Replication service that can easily support this – you can see our May 10 blog post for more info, and we hope you’ll let us know what you think of it.