In this post we will discuss the key parts of a well architected aws codepipeline, and what that looks like.
We will break apart an existing pipeline, and use some ninja commands and methods to put it back together better, including scaling pipelines horizontally to assemble enterprise grade stacks.
We will also add some controls for governance & approval mechanisms to ensure successful & true CI/CD with our 100% native AWS CodePipeline.
This article is a sub-section of the bigger topic & Series: The Anatomy of a Well Architected AWS Project .
[TODO]
TODO: visual annotated codepipeline
TODO: backup pipeline.json file explanation
Comments