TrustRadius: an HG Insights company

AWS CodeDeploy Reviews and Ratings

Rating: 10 out of 10
Score
10 out of 10

Reviews

5 Reviews

Improved and is expanding.

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

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.

Pros

  • Deployment group.
  • Deployment automation.
  • Deployment versioning.

Cons

  • Create a code environment.
  • Adding AI to assist with possible errors.
  • More videos to instruct newcomers.

Likelihood to Recommend

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.

Vetted Review
AWS CodeDeploy
4 years of experience

Cloud-native deployment for cloud-native deployers

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

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.

Pros

  • Integration with other AWS services
  • No administration required
  • Unified and easy process for dev teams

Cons

  • Hybrid deployments to both cloud & on-prem may be difficult depending on stack used
  • Not as feature-rich like some competitors specializing on deployment
  • Legacy builds may turn difficult to migrate to CodeDeploy, so alternative may still be required for those

Likelihood to Recommend

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.

Vetted Review
AWS CodeDeploy
2 years of experience

My Review for AWS - CodeDeply

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

With AWS CodeDeploy we were able to automate our software deployments. With CodeDeploy, we deploy our applications and upgrades across Dev, Test, and Prod Env. AWS CodeDeploy helps minimizing application downtimes and improves stability. That is one of the major overcome.

Pros

  • Minimize downtime and improved Stability
  • Centralized
  • Easy to integrate with other AWS Services

Cons

  • Would Love to have more traceability when troubleshooting

Likelihood to Recommend

AWS CodeDeploy complies and supports EC2, OnPrem, AWS Lambda (Serverless) as well as ECS. And we were able to deploy our application on any of them. Another advantage was it was really easy to roll back the deployment whenever we wanted to revert the change that we performed.

Vetted Review
AWS CodeDeploy
4 years of experience

Excellent Automate Deployment tool

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

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.

Pros

  • Automate to deploy to AWS cloud environments
  • Maximize application availability during product deployment
  • AWS CodeDeploy provides CLI or web management console which can be viewed or edited at any environment

Cons

  • There is one limitation is it can't do multi-tier apps
  • It is not possible to control the order in which deployment occurs if more than one deployment attempts to run at the same time
  • AWS CodeDeploy does not integrate with GitHub

Likelihood to Recommend

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.

Vetted Review
AWS CodeDeploy
3 years of experience

A simplified way to manage complex code pipelines

Rating: 7 out of 10
Incentivized

Use Cases and Deployment Scope

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.

Pros

  • Simplifies checking the status of code branches
  • Streamlines the deployment process
  • Integrates into our Slack workflow for reserving environments

Cons

  • When deploying a branch, sometimes the repository won't auto-populate, and you have to add the source manually

Likelihood to Recommend

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.