AWS CodeDeploy Reviews & Insights

Deployment of an update in different servers became easier. For other regions, the methodology was to go to each server, create the package, deploy it in the staging server, verify it, and then send it to production. We can make it on one server and replicate it on the others. This allowed for a more streamlined update and increased efficiency.

Getting the code from Git Hub, uploading it to the repository, making changes, and deploying it to a specific environment makes AWS tremendous and easy to work with. Once you know how to do it, it is easy to replicate. On the other hand, if you are new, it gets confusing, and you need guidance on the steps to take not to compromise the application.

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.