✅ - Best strategy for migrating an Amplify Gen 2 backend to a new AWS account

[supple dirge]

Hi everyone,

We have an Amplify Gen 2 project with authentication, data, functions, and storage that we need to migrate to a different AWS account. The backend is live and includes:

Users (Cognito)
Data (DynamoDB)
Media files (S3)

What would be the best strategy to ensure a smooth migration while minimizing downtime and preserving user data and configurations? Any insights or best practices would be greatly appreciated.

Thanks in advance!

[limpid glade]

Hey, for Data migrations its generally recommended to work with a solutions architect or account manager on the account if you are part of org.
but as following some resource that may help with this.
Cognito does provide a migrate user and import user trigger that may help with this, refer to https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-lambda-migrate-user.html
You could use services such as AWS DataSync with help with transferring S3 data between accounts: https://docs.aws.amazon.com/datasync/latest/userguide/tutorial_s3-s3-cross-account-transfer.html
For DynamoDB this post should information on couple of options you could use: https://repost.aws/knowledge-center/dynamodb-cross-account-migration
but on a general note, i would suggest throughly evaluating options that bets fit your case and also the cost implications in moving data across.

[supple dirge]

Thanks a lot for the info, will try.

[proper hound]

✅ - Best strategy for migrating an Amplify Gen 2 backend to a new AWS account