You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The codepipline fails "An error occurred (ValidationError) when calling the DescribeStacks operation: Stack with id AWSAccelerator-CDKToolkit does not exist"
Expected behavior
CDK bootstrap should be done by default with Codepipeline. This error does not occur if deployed with github as a source reporitory
Please complete the following information about the solution:
Version: v1.11.1
To get the version of the solution, you can look at the description of the created AWS CloudFormation stack used to install the LZA (AWSAccelerator-InstallerStack). For example, "(SO0199) Landing Zone Accelerator on AWS. Version 1.5.1.". If the description does not contain the version information, you can look at the Parameters of the stack for the RepositoryBranchName as that should contain the version number.
Region: [eu-central-1]
Was the solution modified from the version published on this repository? --> No
If the answer to the previous question was yes, are the changes available on GitHub?
Have you checked your service quotas for the services this solution uses?
Were there any errors in the CloudWatch Logs? --> Yes . "An error occurred (ValidationError) when calling the DescribeStacks operation: Stack with id AWSAccelerator-CDKToolkit does not exist"
Screenshots
Additional context
Only occurs with s3 deployment as source repo.
The text was updated successfully, but these errors were encountered:
Describe the bug
CDK Bootstrap does not work in the management account with s3 deployment as source repository for LZA
To Reproduce
> yarn build && yarn cdk synth --context use-s3-source=true
Expected behavior
CDK bootstrap should be done by default with Codepipeline. This error does not occur if deployed with github as a source reporitory
Please complete the following information about the solution:
Screenshots
Additional context
Only occurs with s3 deployment as source repo.
The text was updated successfully, but these errors were encountered: