We performed a comparison between AWS Amplify and Chef 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."
"The most valuable feature of AWS Amplify is authentication."
"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."
"Chef can be scaled as needed. The Chef server itself can scale but it depends on the available resources. You can upgrade specific resources to meet the demand. Similarly, with clients, you can add as many clients as you need. Again, this depends on the server resources. If the server has enough resources, it can handle the number of servers required to manage the infrastructure. Chef can be scaled to meet the needs of the infrastructure being managed."
"Automation is everything. Having so many servers in production, many of our processes won't work nor scale. So, we look for tools to help us automate the process, and Chef is one of them."
"Chef recipes are easy to write and move across different servers and environments."
"The most valuable feature is the language that it uses: Ruby."
"I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles."
"If you're handy enough with DSL and you can present your own front-facing interface to your developers, then you can actually have a lot more granular control with Chef in operations over what developers can perform and what they can't."
"The most valuable feature is automation."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"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."
"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."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"If they can improve their software to support Docker containers, it would be for the best."
"In the future, Chef could develop a docker container or docker images."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"I would rate this solution a nine because our use case and whatever we need is there. Ten out of ten is perfect. We have to go to IOD and stuff so they should consider things like this to make it a ten."
"The agent on the server sometimes acts finicky."
"I would also like to see more analytics and reporting features. Currently, the analytics and reporting features are limited. I'll have to start building my own custom solution with Power BI or Tableau or something like that. If it came with built-in analytics and reporting features that would be great."
AWS Amplify is ranked 5th in Release Automation with 3 reviews while Chef is ranked 12th in Release Automation with 18 reviews. AWS Amplify is rated 8.4, while Chef is rated 8.0. The top reviewer of AWS Amplify writes "Amplify CLI acts as a single source of truth". On the other hand, the top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". AWS Amplify is most compared with AWS CodeDeploy, Microsoft Azure DevOps, AWS CodeStar, Ozone and GitLab, whereas Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and BigFix. See our AWS Amplify vs. Chef 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.
