AWS CodeDeploy Information Reviews & Insights

AWS CodeDeploy was used as the CI/CD tool throughout a large customer AWS cloud-based service containing 200+ code repositories managed by 8 developer teams. It replaced the old Jenkins-based solution upon migration from on-premises to the cloud. CodeDeploy was chosen mostly because of its easiness of purchase & licensing.

For greenfield projects built on AWS there are very few reasons why not to choose AWS CodeDeploy. It works out of the box and integrates seamlessly into your cloud environment. If you plan to migrate your existing legacy builds away e.g. from Jenkins, you may need to reserve a substantial amount of time for that and the benefits gained may not be worth the effort.

We use AWS CodeDeploy to manage our deployment pipeline. Several squads often have competing branches for features that need to be deployed into various environments for code checks and testing. AWS CodeDeploy gives us a tool to ensure that we do not deploy over one another and makes it clear to our QA/UAT teams when and where features are available so we can test them expediently.

AWS CodeDeploy is helpful for managing multiple code pipelines and deployments to multiple environments. I use it primarily with help from our QA team when we need to ensure that branches get merged into environments with certain feature sets so the code changes can be tested appropriately. Aside from a few obtuse steps involved with loading the repository, it is straightforward to use and gives clear progress indicators.