landing-zone-accelerator-on-aws: Code Pipeline fails using reference sample config
Describe the bug Code Pipeline Prepare stage failed with error message
[Container] 2022/07/19 13:22:49 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: if [ ! -z “${ACCELERATOR_STAGE}” ]; then yarn run ts-node --transpile-only cdk.ts synth --stage $ACCELERATOR_STAGE --require-approval never --config-dir $CODEBUILD_SRC_DIR_Config --partition aws; fi. Reason: exit status 1
To Reproduce After initial deployment of landing-zone-accelerator I then utilised the reference sample configuration, replacing aws region and email addresses in the relevanlt configuration yaml files. I then went to the codepipline and performed a release change
Expected behavior Using the reference sample configuration I expected the codepipeline to deploy the relevant configuration
Please complete the following information about the solution:
- [Version: v1.0.1
To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, “(SO0021) - Video On Demand workflow with AWS Step Functions, MediaConvert, MediaPackage, S3, CloudFront and DynamoDB. Version v5.0.0”. If the description does not contain the version information, you can look at the mappings section of the template:
Mappings:
SourceCode:
General:
S3Bucket: "solutions"
KeyPrefix: "video-on-demand-on-aws/v5.0.0"
- Region: sa-east-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 sevices this solution uses? No… Is there any particular service and I need to check
- Were there any errors in the CloudWatch Logs? No
Screenshots If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context Add any other context about the problem here.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 23 (2 by maintainers)
@boyobejamin I managed to fix this. I had the wrong emails entered when using the CloudFormation template. Steps I took to fix this:
It is a weird fix, but that’s what worked for me. I hope this helps. And don’t use AWS Organizations. Use Control Tower.