Cloud-native deployment for cloud-native deployers
May 21, 2022

Cloud-native deployment for cloud-native deployers

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with AWS CodeDeploy

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.
  • Integration with other AWS services
  • No administration required
  • Unified and easy process for dev teams
  • 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
  • No extra costs of licensing and handling them
  • Ease of provisioning the tooling for new projects and teams
  • Part of unified toolchain for the whole AWS infrastructure
  • 1-2 months per year of working time was saved from administration compared to on-prem legacy solution.
  • Teams can trust more on the CI/CD pipeline and the deployments are faster, so the teams can deploy 10-15% more often compared to on-prem legacy solutions.
  • Developers tend to desire more bells and whistles than CodeDeploy can offer, there has been some critique but this can be seen also as "editor war" (everyone has their opinion).
Jenkins has been the reliable workhorse but it has aged quite a bit. The biggest issue with open source Jenkins is the requirement of hosting it by yourself, as it is not available inside AWS context as a service. That does fit into cloud-native thinking where you want to focus on the product, not on the manufacturing equipment.

Do you think AWS CodeDeploy delivers good value for the price?


Are you happy with AWS CodeDeploy's feature set?


Did AWS CodeDeploy live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of AWS CodeDeploy go as expected?


Would you buy AWS CodeDeploy again?


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.