AWS CodeDeploy Finance and Insurance 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.

AWS CodeDeploy is very helpful to use AWS cloud solutions. We use AWS to deploy our software to AWS EC2, Fargate, and Lamda. AWS CodeDeploy can also be used to deploy on our data center (On-premises servers). They can be used as CI/CD automate software deployments, eliminating the need for error-prone manual operations. We are very happy with the service provided by Amazon Web Services.

The best use case to use AWS CodeDeploy is using to deploy on AWS cloud environment. It makes the software deployment lifecycle easier to release new features on the AWS cloud. The downtime is usually a couple of seconds instead of multiple hours. The only draw is that it lacks the support of GitHub, which is a little bit inconvenient. We need to create an extra layer to make this work.