We performed a comparison between AWS Amplify and Red Hat Ansible Automation Platform based on real PeerSpot user reviews.
Find out in this report how the two Release Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable feature of AWS Amplify is authentication."
"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."
"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."
"It is very easy to use, and there is less room for error."
"Some colleagues and other companies use it and comment that it is easy to use, easy to understand, and offers good features."
"It is agentless. I don't have to think about which client system my unit has understanding in or not, because I can execute from my system. It will go and configure it, and any module that it is looking for will be shipped out."
"The automation is the most valuable feature."
"I like the inventory management. It's a very nice, simple, concise way to keep all that data together. And the API allows us to use it even for things that are not Ansible."
"It has improved our organization through provisioning and security hardening. When we do get a new VM, we have been able to bring on a provisioned machine in less than a day. This morning alone, I provisioned two machines within an hour. I am talking about hardening, installing antivirus software on it, and creating user accounts because the Playbooks were predesigned. From the time we got the servers to the actual hand-off, it takes less than an hour. We are talking about having the servers actually authenticate Red Hat Satellites and run the yum updates. All of that can be done within an hour."
"The most valuable features of the solution are automation and patching."
"The most useful features are the playbooks. We can develop our playbooks and simplify them doing something like a cross platform."
"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 can implement multiple web applications, and cross-platform applications, like iOS."
"AWS Amplify could improve in the deployment. It would be beneficial to have more methods, such as automation."
"It would be helpful to have templates for common configurations. It would make it much easier and faster rather than creating a whole script. The templates would decrease the learning curve as well."
"The job workflow needs to be worked on. It's not really clear to how you actually link things together. What they probably could do is provide an example workflow on how to stitch things together. I think that would be very helpful."
"It can use some more credential types. I've found that when I go looking for a certain credential type, such as private keys, they're not really there."
"I have seen indications that the documentation needs improvement. They are providing a "How to Improve Your Documentation" presentation at this conference."
"There needs to be improvement in the orchestration."
"What I'm trying to figure out, personally, is, when doing mass updates, how I can parallelize that a little bit better. It seems right now - and maybe, it's a shortcoming on my end - that I run through one set of servers, and then another set of servers, ad then another set of servers, but it seems like I could throw a lot of these checks out. Different types of servers, like web servers and DB servers, if I could parallelize that a little bit to make everything run a little bit more efficiently, that would help."
"The support could be better."
"What we need is model-driven, declarative software infrastructure management. However, things tend to break with new versions, requiring a lot of work to fix…The focus should be on improving the support for Ansible in the area of AI coding."
More Red Hat Ansible Automation Platform Pricing and Cost Advice →
AWS Amplify is ranked 5th in Release Automation with 3 reviews while Red Hat Ansible Automation Platform is ranked 3rd in Release Automation with 62 reviews. AWS Amplify is rated 8.4, while Red Hat Ansible Automation Platform is rated 8.6. The top reviewer of AWS Amplify writes "Amplify CLI acts as a single source of truth". On the other hand, the top reviewer of Red Hat Ansible Automation Platform writes "Makes it easy to build playbooks and saves time and resources". AWS Amplify is most compared with AWS CodeDeploy, Microsoft Azure DevOps, AWS CodeStar and Ozone, whereas Red Hat Ansible Automation Platform is most compared with Red Hat Satellite, Microsoft Configuration Manager, VMware Aria Automation, Microsoft Azure DevOps and Microsoft Intune. See our AWS Amplify vs. Red Hat Ansible Automation Platform report.
See our list of best Release Automation vendors.
We monitor all Release Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
