Best Ways to Transfer S3 and DynamoDB Data Between AWS Accounts

For moving large datasets, S3 batch replication is a solid option for S3 transfers. Just keep in mind, if you're pulling from Deep Archive, it could take up to 24 hours to bring everything back. For your DynamoDB tables, you’ll probably need to write some custom code. A simple scan and insert script should do the trick, and if you're dealing with large batches, some multi-threading might be necessary. Also, consider setting up a dedicated EC2 instance in the appropriate region to help save on costs and improve transfer speeds.

Just a heads up, there’s no way to transfer ownership of S3 buckets directly—it's likely similar with DynamoDB. But you can use AWS DataSync for data transfers, though keep an eye on costs if you’re dealing with large amounts of data. It’s worth asking why you want to switch accounts in the first place, too.

You might want to check out AWS Backup, as it supports cross-account operations. This could be a straightforward way to handle your data transfer without a ton of hassle.

For DynamoDB data, if you've got a lot to move, one approach is to alter your code to let it write to both accounts temporarily while you're transitioning. You could back up your DynamoDB in one account, give access to the backup for the other account, and restore it there. This could save you costs compared to performing a full global scan.