Skip to main content
AWS CodeDeploy

AWS CodeDeploy


What is AWS CodeDeploy?

AWS CodeDeploy is a fully managed deployment service that automates software deployments to a variety of compute services such as Amazon EC2, AWS Fargate, AWS Lambda, and on-premises servers. AWS CodeDeploy aims to make it easier for users to rapidly…

Read more
Recent Reviews
Read all reviews
Return to navigation


View all pricing

AWS CodeDeploy


per on-premises instance

Entry-level set up fee?

  • No setup fee


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Demos

AWS Code Deploy Setup (EC2, IAM, Github) - Amazon Web Services Tutorial


AWS CodeDeploy | AWS Certified DevOps Engineer Training | Edureka

Return to navigation

Product Details

What is AWS CodeDeploy?

AWS CodeDeploy Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings



(1-4 of 4)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
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
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.
  • 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.
Score 8 out of 10
Vetted Review
Verified User
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.
  • Minimize downtime and improved Stability
  • Centralized
  • Easy to integrate with other AWS Services
  • Would Love to have more traceability when troubleshooting
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.
  • Minimized Downtime
  • Automated deployments
  • Ability to control with CLI
  • Less Customer Complaints due to minimized Downtime
  • Less resource requirement due to simple rollback ability
  • Supportability of other AWS Services
Jenkins supports a lot of plugings. Also with Jenkins, it is possible to manage everything through our own server. Those are 2 points where I rate Jenkins as one of the best DevOps Tool.
Score 9 out of 10
Vetted Review
Verified User
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.
  • 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
  • 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
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.
  • CI/CD support
  • Automate code deployment to AWS EC2
  • AWS management console and CLI tools
  • Definite positive impact
  • This tool provides automate features which reduce the dev ops work load
  • This tool works in many different languages so we can have a generic setup code for different languages
  • No negative impact
The most important reason we use AWS CodeDeploy was we use Amazon Web Services and our ecosystem platform. We want all the software components seamlessly integrated together. The CI/CD is always an issue to our software process, and also, we don't want to have any downtime when we deploy a new feature. With AWS CodeDeploy, our process becomes more agile, and we can even deploy new changes when the market is open. That's very important for us.
GitLab, PDQ Deploy, Microsoft Endpoint Manager (Microsoft Intune + SCCM)
Philippa Schwarzkopf | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
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.
  • Simplifies checking the status of code branches
  • Streamlines the deployment process
  • Integrates into our Slack workflow for reserving environments
  • When deploying a branch, sometimes the repository won't auto-populate, and you have to add the source manually
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.
  • Branching code deployments
  • Environment management
  • Status and progress indicators on code pipeline
  • AWS CodeDeploy has reduced the engineer involvement in deployments
  • Our QA team has been able to effectively deploy tickets for testing, and our Release Managers can manage production deployments
  • Progress indicators have given us a better baseline for deployment times, which is helpful for time-sensitive releases
Return to navigation