Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation lacking how to handle scenario for pre-bootstrapped environments... #7482

Open
seawolf-qrs opened this issue May 4, 2024 · 2 comments
Labels
amplify/cli Issues tied to CLI amplify/gen2 p3 missing info

Comments

@seawolf-qrs
Copy link

Amplify Docs - Bootstrap your AWS account

The documentation doesn't provide information on the error that will present in the console if the AWS account already has a CDKToolkit: Stack [CDKToolkit] already exists

If the account was bootstrapped previously, the option to initiate the first-time setup does not appear when going through the steps to create an Amplify application. The option does not appear before clicking through to create the new app, which then leads to the Stack [CDKToolkit] already exists error.

I found that this GitHub issue provides a solution to move past this error. You can open Cloudshell and run cdk bootstrap aws://ACCOUNT-NUMBER-1/REGION-1to update the bootstrap stack to a new version. Once this is done, the error no longer appears, and the app creates successfully.

I think it would benefit users of the Amplify service to have a section in the documentation that mentions this error and how to move past it.

@timngyn timngyn added amplify/cli Issues tied to CLI amplify/gen2 labels May 6, 2024
@kmonihen
Copy link

kmonihen commented May 7, 2024

We are running into this same issue. We bootstrap accounts in our organization using stacksets with specific guardrails so the CDK resources are already present, but amplify is trying to bootstrap the account with the CDKToolkit stack anyway.

Update 1: I've updated our bootstrap template to the latest version (v. 20) and we'll see if that helps.
Update 2: That didn't help, it's still trying to bootstrap the account with the CDKToolkit stack.

@josefaidt josefaidt added the p3 missing info label May 8, 2024
@josefaidt
Copy link
Contributor

Hey @seawolf-qrs 👋 thanks for raising this! Agreed, we should add a section in the troubleshooting docs and improve this error message 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
amplify/cli Issues tied to CLI amplify/gen2 p3 missing info
Projects
None yet
Development

No branches or pull requests

4 participants