Passer au contenu

Transfer amplify to another aws account

0

Hi, How can I transfer an amplify app and route 53 redirection from one aws account to another without using AIM? Should I disconnect everything on one account and create it on the other? is there an easier web?

Regards,

demandé il y a 6 mois105 vues
1 réponse
0

Transferring an Amplify app and Route 53 redirection from one AWS account to another without using IAM can be challenging, as there's no direct method to transfer these resources between accounts. However, you can follow a process to minimize downtime and recreate the setup in the new account. Here's an approach you can consider:

  1. For the Amplify app:

    • In the new AWS account, create a new Amplify app with the same configuration as your existing one.
    • Deploy your application code to this new Amplify app.
    • Ensure all environment variables and settings are correctly configured in the new app.
  2. For Route 53:

    • If you're using a custom domain, you'll need to transfer the domain registration to the new AWS account. This process is documented by AWS and can be done without downtime.
    • Copy the hosted zone from the old account to the new account. This ensures that all DNS records are identical.
    • After transferring the domain registration (if applicable), update the name servers for the domain to point to the hosted zone in the new account.
  3. Redirecting traffic:

    • Once your new Amplify app is set up and tested in the new account, update your DNS records in the new Route 53 hosted zone to point to the new Amplify app's URL.
  4. Cleanup:

    • After confirming that everything is working correctly in the new account, you can disconnect and delete the resources in the old account.

While this process involves recreating resources rather than a direct transfer, it allows you to move your setup to a new account with minimal downtime. The key is to set up the new environment completely before switching over the DNS, ensuring a smooth transition for your users.

Remember to test thoroughly in the new account before making the final DNS changes to redirect traffic. This approach, while more manual, allows you to move your resources without relying on IAM roles for cross-account access.
Sources
Migrating workloads from one AWS account to another | AWS re:Post
Cross-account deployments - React - AWS Amplify Gen 2 Documentation

répondu il y a 6 mois

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.