Fixing "fail: No bucket named" when bootstrapping using --bootstrap-bucket-name

[reikje]

I have used the --bootstrap-bucket-name flag when running cdk bootstrap. Now cdk deploy fails because it cannot find the right bucket.

[100%] fail: No bucket named 'xyz-123456789-us-east-1'. Is account 123456789 bootstrapped?

I understand that I should provide a custom stack synthesizer but what is the property I should set? Can I use cdk.json instead, as I have already set a custom qualifier there - and if I can, what is the option I should set in that file?

[nagkumar]

+1 same issue for me.. none of CDK examples are working.. may be due to security policy issue, no CDK developer guide or anywhere it is told.. pulumi was a cakewalk.. cdk seem to be too painful

[indrora]

You'll need to adjust your app stack slightly.

// where your stack is set up:
new MyStack(this, 'MyStack', {
  synthesizer: new DefaultStackSynthesizer({
    fileAssetsBucketName: 'MySuperSpecialBoostrapBucket',
    bucketPrefix: '',
  }),
});

Details are here under the heading "Changing the resource names".

[silver-mx]

I solved my issue by deleting the CDKToolkit stack created in Cloudformation. The stack existed and was in an inconsistent state. So this was the solution for me:

aws cloudformation delete-stack --stack-name CDKToolkit --profile my-profile

and then bootstrap again:

cdk bootstrap aws://ACCOUNT/REGION --profile my-profile

Source: https://stackoverflow.com/a/71283964/677096

[orimslala]

Thank you! worked for me

[VishalVinayRam]

Thank you , it worked for me