aws-amplify / aws-amplify/amplify-studio
Migration between AWS accounts
- Dominant language
- No language data
- Stars
- 135
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the feature you'd like to request
For now there is no official documentation on how to migrate EVERYTHING from one AWS to another
I was struggling trying migrate our Amplify based infrastructure, which took days, I think there should be a button clicking on which it should bring everything from old account to the new one, Terraform could work under the hood
### Describe your use case and how the feature would improve your experience.
Very often companies need their production isolated from development and separating them not between regions or roles but between root accounts, that's where you need to migrate accounts, or you want to create a similar app, but for another client
### Describe alternatives you've considered
Alternatives are manually copying everything, what I did was to create an amplify project in the new account's console, pulled it, did some hardcodings on `team-provider-info.json` and similar files, pushed, than manually copied SNS, SQS, SES, OpenSearch, Route53, CloudFront and similar services
Or use Terraform, but you need some devops work to do which neither developer nor client can do
### Additional context
_No response_
Contributor guide
Research direction
No project files, tests, or entry points are identified. Start by reviewing how Amplify projects use team-provider-info.json and cataloging the requested AWS services, including SNS, SQS, SES, OpenSearch, Route53, and CloudFront. Done would require an agreed migration scope and an implementation or official documentation covering the complete account-to-account workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100