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

AWS Amplify 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 Amplify
Ranking in Release Automation
5th
Average Rating
7.4
Reviews Sentiment
7.4
Number of Reviews
7
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 Amplify is 2.6%, down from 2.7% 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

Krishna Vishwakarma - PeerSpot reviewer
Has good documentation but takes time for a beginner to learn
The only tricky part I experienced was during the initial installation. I followed the documentation, but it wasn't working for some reason. I had to modify some local files in the CLI-generated folder to get it to work. I had to dig deep to find the issue, and it wasn't mentioned in the docs. So, some issues could be better highlighted in the AWS CLI documentation, which would help developers integrate other services more easily. AWS needs to improve its support.
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

"Typically, whenever we make changes and need to switch environments (e.g., dev to production), it's easy for our developers to maintain the state of each environment and make customizations as needed. They don't necessarily need to involve the cloud team for basic management."
"One of the things I like best about AWS Amplify is its ease of use and strong integration with other AWS services, which enhances efficiency."
"The link with Figma is very nice. You can create your design in Figma, and then you can import it into AWS Amplify and use it. You can link it to your data source and data bindings."
"The only tricky part I experienced was during the initial installation. I followed the documentation, but it wasn't working for some reason. I had to modify some local files in the CLI-generated folder to get it to work. I had to dig deep to find the issue, and it wasn't mentioned in the docs. So, some issues could be better highlighted in the AWS CLI documentation, which would help developers integrate other services more easily. AWS needs to improve its support."
"The most valuable feature is user management, which includes authentication and authorization."
"I didn't host my application but have used their backend as a service. It was a complete package with authentication, AWS AppSync, DynamoDB, and GraphQL. AWS Amplify is great if you don't know backend development and don't want to struggle with other backend services like MongoDB. You don't have to worry about what backend language or database to use. If you're confused, enroll with AWS Amplify. I also recommend Google Firebase for similar purposes."
"The most valuable feature of AWS Amplify is authentication."
"Role-based access control and agentless architecture are the main features which may attract users."
"The most valuable features of the solution are automation and patching."
"I like Ansible's ease of use. If you have Linux skills, you can create a reusable template for the dependencies and other configurations. I can store the templates in a repository and share them with my customers or other developers. It's a popular solution, so there is a large user base that can share templates."
"One of the most valuable features is that Ansible is agentless. It does not have dependencies, other than Python, which is very generic in terms of dependencies for all systems and for any environment. Being agentless, Ansible is very convenient for everything."
"The most valuable feature is that Ansible is agentless."
"The easy-to-read syntax for YAML files and the interoperability between modules are valuable."
"The most valuable features of the solution are its configuration management, drift management, workflow templates with the visual UI, and graphical workflow representation."
"The solution is very simple to use."
 

Cons

"The documentation needs improvement, as it is not user-friendly and can be challenging for novices."
"Its capability to handle big projects needs to be improved. If you generate a user interface in Figma and import everything where all components are in one directory, currently, it is complicated. It isn't able to cope with that. For small projects, it is not an issue, but if you have big projects and you want to use AWS Amplify, then it gets more difficult. That is the most important point for me. It should be improved to cope better with bigger projects."
"AWS Amplify can be improved in some areas, particularly in providing more robust documentation and easier customization options."
"AWS Amplify could improve in the deployment. It would be beneficial to have more methods, such as automation."
"AWS can implement multiple web applications, and cross-platform applications, like iOS."
"I like AWS Amplify's documentation. It's comprehensive and includes many examples, so you don't need to ask for help much - you can refer to the docs. It's easy to use. I also appreciate the cost structure. You only pay for what you use. For example, if you use 100 GB, you're charged for that, but if you don't use it, you pay the maintenance cost."
"I don't think there are major issues, but there is room for improvement in the UI/UX of AWS Amplify. The UI still needs to be more polished and user-friendly. It's currently a bit like drag-and-drop initially, but there should be more options to customize the UI based on our needs."
"In Community, there's a lot of effort towards testing, standardizing, and testing for module development to role development, which is why Molecule is now becoming real. Same thing with Zuul, which we are starting to implement. Zulu tests out modules from third-party sources, like ourselves, and verifies that the modules work before they are committed to the code. Currently, Ansible can't do this with all the modules out there."
"They should think of this product as an end-to-end solution and begin to develop it that way."
"The governance features could be improved."
"Accessibility. Ansible uses a CLI by default. Those accustomed to it can find their way and adopt the YAML files easily over time. But, some users are more comfortable using UIs..."
"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."
"We are very satisfied with what we have. From a management point of view, whatever makes it easier for my team to help customers write their own playbooks would be something very beneficial. Everything is going as a service. Creating playbooks can become much more consumer-oriented so that customers do not need to contact us to write their own playbooks."
"More library support for microservices architecture and Kubernetes would be helpful."
"There should be better Windows support. We have had to develop a lot of our own roles because of the Windows platform. The Red Hat Enterprise Linux ones existed but not the Windows versions, so I have had to develop a bunch of Windows ones."
 

Pricing and Cost Advice

"When you're just starting, it is free. You have to pay only when you reach a certain amount of usage. I'm still at the early stage. So, I don't have to pay a lot. At the moment, it is not too expensive for me. It is worth the money."
"The pricing depends on what your use case is and whether you're an existing AWS customer. It's a pay-as-you-go model, so not expensive."
"Customers need to pay yearly for the license."
"Like many Red Hat products, they have a no-cost version of the web application (AWX, formerly Ansible Tower), but you are on your own to install and it is a little more complicated than just installing Ansible."
"Users have to pay a per-node cost of around $ 100 per node."
"The cost is high, but it still works well."
"Ansible Tower is pretty expensive."
"It is a little pricey but it is affordable. It is not that bad."
"It’s an open-source tool."
"Red Hat's open source approach was a factor when choosing Ansible, since the solution is free as of right now."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
859,129 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Financial Services Firm
10%
Construction Company
9%
Healthcare Company
7%
Financial Services Firm
17%
Educational Organization
17%
Computer Software Company
11%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

How to estimate whether using the AWS services is worthwhile for saving time and money for manufacturing at a retailer company?
Estimating the cost-effectiveness of using AWS services for manufacturing at a retailer company involves a comprehensive analysis. To make an informed decision, you should consider factors like the...
What do you like most about AWS Amplify?
Typically, whenever we make changes and need to switch environments (e.g., dev to production), it's easy for our developers to maintain the state of each environment and make customizations as need...
What is your experience regarding pricing and costs for AWS Amplify?
I find the pricing of AWS Amplify reasonable, considering the value it provides, although opinions may vary based on usage.
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 Amplify vs. Red Hat Ansible Automation Platform and other solutions. Updated: June 2025.
859,129 professionals have used our research since 2012.