Try our new research platform with insights from 80,000+ expert users

AWS CodeDeploy vs Red Hat Ansible Automation Platform comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AWS CodeDeploy
Ranking in Release Automation
4th
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
13
Ranking in other categories
No ranking in other categories
Red Hat Ansible Automation ...
Ranking in Release Automation
3rd
Average Rating
8.6
Reviews Sentiment
7.3
Number of Reviews
69
Ranking in other categories
Configuration Management (1st), Network Automation (1st)
 

Mindshare comparison

As of June 2025, in the Release Automation category, the mindshare of AWS CodeDeploy is 3.2%, up from 2.9% compared to the previous year. The mindshare of Red Hat Ansible Automation Platform is 5.7%, up from 4.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Release Automation
 

Featured Reviews

MuhammadBilal7 - PeerSpot reviewer
Effective communication with seamless integration improves deployment but tool diversity raises usability questions
There are many tools in the market that cover different aspects, such as the GitOps methodology of deployment. I have not used CodeDeploy with EKS, although I have used it with ECS. I am not sure if CodeDeploy can be used with EKS, and I see this as a deficiency for end users. Easier implementation would be beneficial.
Muralitharan KS - PeerSpot reviewer
Efficient server management and detailed reporting with flexible deployment capabilities
We are primarily using Ansible for automation purposes as it is a configuration management tool. It is utilized for various activities such as DNS activity, changes to web servers, virtual host settings, and other day-to-day tasks, all of which are templated in Ansible Ansible allows us to manage…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It is very flexible."
"I can integrate it with other AWS services."
"The most valuable features of AWS CodeDeploy are its integration with other AWS services to deploy applications."
"It's just like every other AWS resource I use. It gets the job done."
"The biggest feature of AWS CodeDeploy is its scalability."
"I found the default settings of AWS CodeDeploy to be highly beneficial for my deployment workflows. For instance, when deploying a Node.js application, I manually installed the necessary components on my AWS instance, such as the web server required by developers. Then, I created deployment scripts for starting and stopping instances and performing the deployment itself. These scripts were stored alongside my code in GitHub, ensuring they executed seamlessly with the CI/CD pipeline. Since the project wasn't overly complex, I opted for the default settings, which proved to be efficient and straightforward for deployment."
"The product is easy to use."
"AWS CodeDeploy operates on an on-demand basis. This means that you only pay for the exact duration of the deployment process. Whether it takes one minute, two minutes, or even longer, you're only charged for the time it takes to complete the deployment. You're not locked into paying for dedicated servers."
"It is very extensible. There are many plugins and modules out there that everybody helps create to interact with different cloud providers as well."
"It does not require staff for deployment and maintenance. It just works."
"I like the agentless feature. This means we don't install any agent in worker nodes."
"RBAC is great around Organizations and I can use that backend as our lab. Ingesting stuff into the JSON logs, into any sort of logging collector; it works with Splunk and there are other collectors as well. It supports Sumo and that helps, I can go create reports in Sumo Logic. Workflows are an interesting feature. I can collect a lot of templates and create a workflow out of them."
"The biggest thing I liked about Ansible is the check mode so that we can verify, after we've pushed, that the config there is actually what we intended."
"It's nice to have the Dashboard where people can see it, have it report to our ELK stack. It's far more convenient, and we can trigger it with API and schedules, which is better than doing it with a whole bunch of scripts."
"Red Hat Ansible Automation Platform is valuable due to the simplicity of the YAML language."
"There are no agents by default, so adding a new server is a matter of a couple lines of configuration (on a new server and the configuration master)."
 

Cons

"The documentation could be more detailed, especially for new users."
"The support and those things are lacking compared to others."
"I faced some stability issues."
"Deployment and stability should be improved."
"There will always be room for improvement, however, I cannot think of any specific improvements at the moment."
"Improvements could be made to AWS CodeDeploy in terms of its agent's compatibility across different operating systems. Currently, there are instances where the agent may not work seamlessly with certain integrations, leading to issues with registering protocols on authorized servers."
"The documentation could be more detailed, especially for new users."
"An improvement for the end users would be easier implementation, especially regarding local testing tools for deployment."
"I have seen indications that the documentation needs improvement. They are providing a "How to Improve Your Documentation" presentation at this conference."
"There have been some differences between the operating systems that we have noticed. It could be down to cryptographic policies, but we have noticed some speed issues. They should work on the speed of deployment on different operating systems."
"We are not using the Dashboard a lot because we have higher expectations from it. The default Dashboard from Tower doesn't give that much information. We really want to get down into more than if the job succeeded or what was the percentage of success. We want to get down to task-level success. If, in a job, there are ten tasks, we want to see this task was a success, and this was not, and how many were not. That's the kind of granularity we are looking for, that Tower does not give right now."
"For Ansible Tower, there are three tiers with ten nodes. I would like them to expand those ten nodes to 20, because ten nodes is not enough to test on."
"It is a little slow on the network side because every time you call a module, it's initiating an SSH or an API call to a network device, and it just slows things down."
"The solution is slightly expensive, and its pricing could be improved."
"There could be more stuff in the workflows. I hope that if I have ten templates with different services on it, workflow could auto-populate all the template-based services."
"Improvements should be made in terms of execution speed, which is, I believe, the most lacking feature. Aside from that, re-triggering a failed task is another useful feature."
 

Pricing and Cost Advice

"It is costly."
"Since we are using a dedicated AWS environment, the solution's pricing is fine."
"The product is free with EC2."
"The product's price is normal."
"AWS CodeDeploy has proven to be a cost-effective solution for us, especially considering the benefits we gain from using it. In terms of pricing, AWS is quite affordable, providing excellent value for the features and services it offers."
"Users have to pay a per-node cost of around $ 100 per node."
"I don't see the pricing or licensing features, but from what I understand, it is fairly reasonable."
"Ansible Tower is free. Until they lower the cost, we are holding off on purchasing the product."
"Customers need to pay yearly for the license."
"We're charged between $8 to $13 a month per license."
"The pricing is pretty standard."
"Red Hat's open source approach was a factor when choosing Ansible, since the solution is free as of right now."
"Ansible Tower is pretty expensive."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
856,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Financial Services Firm
13%
University
11%
Comms Service Provider
6%
Educational Organization
21%
Financial Services Firm
17%
Computer Software Company
11%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What is your experience regarding pricing and costs for AWS CodeDeploy?
Evaluating cost, it is important to note that the services provided by CodeDeploy can be expensive to purchase from other cloud platforms. However, depending on the services, it might be worth the ...
What is your primary use case for AWS CodeDeploy?
I remember it was a Node.js API that I deployed to some EC2 instances. I was trying to use PM2, a process manager, to deploy the application to the end users.
What is the difference between Red Hat Satellite and Ansible?
Red Hat Satellite has proven to be a worthwhile investment for me. Both its patch management and license management have been outstanding. If you have a large environment, patching systems is much ...
How does Ansible compare to Microsoft Endpoint Configuration Manager (SCCM)?
Microsoft Endpoint Configuration Manager takes knowledge and research to properly configure. The length of time that the set up will take depends on the kind of technical architecture that your org...
What do you like most about Red Hat Ansible Automation Platform?
The most valuable features of the solution are automation and patching.
 

Also Known As

No data available
Ansible
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
HootSuite Media, Inc., Cloud Physics, Narrative, BinckBank
Find out what your peers are saying about AWS CodeDeploy vs. Red Hat Ansible Automation Platform and other solutions. Updated: June 2025.
856,873 professionals have used our research since 2012.