Source: aws.amazon.com
Configuration driven dynamic multi-account CI/CD solution on AWS
Many organizations require durable automated code delivery for their applications. They leverage multi-account continuous integration/continuous deployment (CI/CD) pipelines to deploy code and run automated tests in multiple environments before deploying to Production.
Traditional pipeline stages are predefined and static in nature, and once the pipeline stages are defined it’s hard to update them.
New code deployments will be delivered with custom pipeline stages based on the pipeline configuration that you create.
To avoid ongoing charges for the resources that you created following this post, you should delete the following: The pipeline configuration stored in the DynamoDB The CloudFormation stacks deployed in the target CI/CD accounts The AWS CDK app deployed in the main CI/CD account Empty and delete the retained S3 buckets.
Traditional pipeline stages are predefined and static in nature, and once the pipeline stages are defined it’s hard to update them.
New code deployments will be delivered with custom pipeline stages based on the pipeline configuration that you create.
To avoid ongoing charges for the resources that you created following this post, you should delete the following: The pipeline configuration stored in the DynamoDB The CloudFormation stacks deployed in the target CI/CD accounts The AWS CDK app deployed in the main CI/CD account Empty and delete the retained S3 buckets.
Related Articles
Community Partners
DevOps Careers