We performed a comparison between AWS Config and Chef based on real PeerSpot user reviews.
Find out in this report how the two Configuration Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Intune's feature that I have found most valuable is its auto-pilot feature."
"For Windows services, there are multiple options within Intune to modernize it to be more internet-facing and dynamic."
"The most important thing for me is the autopilot feature."
"The solution is stable."
"The key benefit of Intune is its integration with the Microsoft ecosystem."
"Maturity makes it a stable product."
"The most valuable feature is the UEM capabilities."
"The synchronization of Intune with other Microsoft solutions is a valuable feature."
"Installing the instances and performing upgrades is smooth and clean."
"The solution is scalable and provides over 100 rules."
"The initial setup is super easy, it takes like two minutes. Literally a one-click deployment."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"The scalability of the product is quite nice."
"Chef recipes are easy to write and move across different servers and environments."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"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."
"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."
"Stable and scalable configuration management and automation tool. Installing it is easy. Its most valuable feature is its compliance, e.g. it's very good."
"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."
"The add-ons must be integrated into the solution."
"The security features should be improved."
"I'd suggest adding more features for macOS in Intune. There should be more functionality for managing macOS. There should be a better capability for pushing things down on macOS. Currently, Intune is not capable of managing macOS at the same level as Windows."
"The reporting and cost have room for improvement."
"Microsoft Intune fails a lot when it comes to device compliance."
"Microsoft Intune's support for Mac devices is lacking and could be improved."
"The closest Microsoft Intune can be to GPOs, the better. There needs to be more granularity on application deployments. However, they have done better recently with the application deployments."
"The scalability could be improved, and like most other MDM products, Intune is good but not 100% there yet."
"The solution is missing a configuration that can assist us when writing our programming languages."
"There is room for improvement in built-in tools, they are not up to the mark."
"The reboot process for AWS instances could be improved. Microsoft Azure does not have this problem, so AWS could consider making their instances more robust. You would not need to reboot your instances frequently to replace the hardware and stuff. They can look for a better approach or mechanism to improve in the future. The concern is that you need to plan for the outage when you reboot an instance. You need to have a maintenance window where you can properly reboot the instance without affecting your application. When Amazon announces that you need to reboot an instance and are not ready, this becomes a problem."
"In the future, Chef could develop a docker container or docker images."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"Since we are heading to IoT, this product should consider anything related to this."
"The time that it takes in terms of integration. Cloud integration is comparatively easy, but when it comes to two-link based integrations - like trying to integrate it with any monitoring tools, or maybe some other ticketing tools - it takes longer. That is because most of the out-of-the-box integration of the APIs needs some revisiting."
"It is an old technology."
"Support and pricing for Chef could be improved."
"They could provide more features, so the recipes could be developed in a simpler and faster way. There is still a lot of room for improvement, providing better functionalities when creating recipes."
"I would like to see more security features for Chef and more automation."
AWS Config is ranked 16th in Configuration Management with 3 reviews while Chef is ranked 15th in Configuration Management with 18 reviews. AWS Config is rated 9.0, while Chef is rated 8.0. The top reviewer of AWS Config writes "A cloud solution to host application with smooth instance installation and performance upgrade". On the other hand, the top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". AWS Config is most compared with AWS Systems Manager, whereas Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and BigFix. See our AWS Config vs. Chef report.
See our list of best Configuration Management vendors.
We monitor all Configuration Management 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.
