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 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."
"The most valuable feature of AWS Amplify is authentication."
"It is all modular-based. If there is not a module for it today, someone will write it."
"The automation is the most valuable feature."
"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."
"The most valuable features of Red Hat Ansible Automation Platform are the agentless platform and writing the code is simple using the Yaml computer language."
"It is very extensible. There are many plugins and modules out there that everybody helps create to interact with different cloud providers as well."
"There are so many models that I don't have to create one."
"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."
"AWS can implement multiple web applications, and cross-platform applications, like iOS."
"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 could improve in the deployment. It would be beneficial to have more methods, such as automation."
"The communication on it is not probably where it could be. We could use some real life examples where we could point customers to them and say, "This is what you are trying to do. If you follow these steps, it would at least get you started a bit quicker.""
"Performance has been an issue on larger environments, but it has gotten a lot better over the past two years."
"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 area which I feel can be improved is the custom modules. For example, there are something like 106 official modules available in the Ansible library. A year ago, that number was somewhere around 58. While Ansible is improving day by day, this can be improved more. For instance, when you need to configure in the cloud, you need to write up a module for that."
"I have seen indications that the documentation needs improvement. They are providing a "How to Improve Your Documentation" presentation at this conference."
"What I would like to see is a refined Dashboard to see, when I log in: Here are all my jobs, here are how many times they've executed; some kind graphical stitching-together of the workflows and jobs, and how they're connected. Also, those "failed hosts," what does that mean? We have a problem, a failed host can be anything. Is SSH the reason it failed? Is the job template why it failed? It doesn't really distinguish that."
"There needs to be improvement in the orchestration."
"For a couple of the API integrations, there has been a lack of documentation."
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 "Its agentless, making the deployment fast and easy". AWS Amplify is most compared with AWS CodeDeploy, Microsoft Azure DevOps, AWS CodeStar, Ozone and GitLab, 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.
