Amplify update broke deployed applications

0

I was hosting a next.js application on Amplify, but the Amplify 2.0 update seems to be broken. I tried to redeploy on the new UI, but keep running into a "Stack [CDKToolkit] already exists" error. When i try to delete the CDK toolkit (having to skip s3 and bootstrap in the deletion process), the cloud stack tries to rollback and throws a "rollback in progress" error prevents me from deploying again. I know many people are having issues with Amplify since the update as well. I don't know if permissions have changed and I don't even know what I need to do because the errors aren't helpful. If anyone can point me in the right direction I'd really appreciate it.

  • sounds like alotta issues to me. check out the answer im gonna submit

1 Answer
0

It sounds like you're encountering multiple issues with the Amplify 2.0 update, including errors related to the CDK toolkit stack and deployment failures. Here are some steps you can take to troubleshoot and potentially resolve these issues:

  1. Review Documentation and Release Notes: Check the Amplify documentation and release notes for any information related to the Amplify 2.0 update. There may be specific changes or requirements that you need to be aware of when upgrading.

  2. Check IAM Permissions: Ensure that your IAM user or role has the necessary permissions to deploy and manage Amplify resources. The permissions required may have changed with the update, so it's worth reviewing the updated documentation to confirm the required permissions.

  3. Verify Amplify CLI Version: Make sure you're using the latest version of the Amplify CLI. You can update the CLI by running npm install -g @aws-amplify/cli if you haven't already done so.

  4. Check AWS CDK Toolkit Stack: If you're encountering errors related to the CDK toolkit stack already existing, you may need to manually delete the stack from the AWS CloudFormation console. Make sure to carefully follow the steps to delete the stack, ensuring that you skip deletion of S3 buckets and bootstrap resources as needed.

  5. Resolve Rollback in Progress: If you're unable to delete the CDK toolkit stack due to a "rollback in progress" error, you may need to wait for the rollback to complete before attempting to delete the stack again. You can monitor the stack events in the CloudFormation console to track the progress of the rollback.

  6. Review CloudFormation Stack Events: Check the CloudFormation stack events for the CDK toolkit stack to identify any specific errors or issues that are preventing the stack from being deleted or updated. This can help you pinpoint the root cause of the problem.

  7. Contact AWS Support: If you're still unable to resolve the issues after trying the above steps, consider reaching out to AWS Support for assistance. They can provide additional guidance and troubleshooting steps based on the specifics of your situation.

Overall, upgrading to a new version of a service can sometimes introduce unexpected issues, but by carefully reviewing the documentation, verifying permissions, and troubleshooting specific errors, you should be able to resolve the issues and successfully deploy your application on Amplify 2.0.

Mustafa
answered 5 months ago
  • your chatGPT response is not useful unfortunately.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions