I deleted the LZA CDK bootstrap CloudFormation stack. How can I regenerate it?

0

I was getting an error during LZA pipeline execution complaining about missing cdk S3 bucket. Therefore I deleted the CF stack and ran CDK bootstrap from cloudshell which created the S3 buckets again (I used the latest CDK version). However the pipeline complains about "is this environment even bootstrapped?" because it needs the original stack. How can I re-create the original stack from LZA?

Building assets failed: Error: Building Assets Failed: Error: AWSAccelerator-PrepareStack-##########-ca-central-1: SSM parameter /cdk-bootstrap/accel/version not found. Has the environment been bootstrapped? Please run 'cdk bootstrap' (see https://docs.aws.amazon.com/cdk/latest/guide/bootstrapping.html) at buildAllStackAssets

Thank you.

sabpro
asked 10 months ago367 views
2 Answers
1

Hi

Please confirm if the following have been deleted if not please delete

AWSAccelerator-CDKToolkit stack in the home region

The Staging bucket in the AWSAccelerator-CDKToolkit stack confirm if the bucket was not retained and its deleted

If the above has been performed already please re run the installer pipeline and advise if you are still experiencing the issue

AWS
answered 10 months ago
  • I deleted the stack and re-ran the installer successfully. Which in turn created the S3 bucket. Thank you. I would say that your reply solved my issue. However the "AWSAccelerator-Pipeline” still failed as it is looking another bucket which wasn’t created. It is looking for this bucket:

    cdk-accel-assets-123456789012-us-east-1

    error message: fail: No bucket named 'cdk-accel-assets-123456789012-us-east-1'. Is account 123456789012 bootstrapped?

    If I create it manually, it will also fail as it is expecting a key in there. I would like to also note that, if I recall correctly, the bucket in us-east-1 used to get created before i disabled the "Region Deny" setting in Control Tower, which is the setting I want.

0

Hi

Thank you for your prompt response and confirming that the previous suggestion was helpful

Please confirm if you have us-east-1 as part of your deny region if yes

Kindly please disable region deny for us-east-1

The pipeline most likely failed during the installer pipeline in us-east-1 because of the Control Tower region deny enabled

us-east-1 needs to be enabled for access to global API endpoints.

Access to the bootstrap bucket and key, and CloudFormation actions are needed as well so CDK can work in us-east-1.

I would advise modifying the region deny to allow the LZA solution to create resources in us-east-1

I understand that you want us-east-1 as part of your deny regions however the LZA solution is causing failures as it is calling resources in the us-east-1 region

Adding us-east-1 as a governed region should resolve the issue

If the above does not resolve the issue, I would suggest reaching out to AWS Premium Support team so that they can deep dive the issue

https://support.console.aws.amazon.com/support/home?region=eu-central-1#/case/create

Thanks in advance

AWS
answered 10 months ago

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