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."While Microsoft Intune boasts a wide range of features, its user-friendliness and bundled licensing cost are key considerations for me."
"I can reach devices or computers over the internet. I don't need to worry about the network connectivity between the offices. I can manage any device. That is the most important part."
"It is helpful for managing devices anytime and any place without requiring dependency on the local networks."
"It is a very stable and scalable cloud-only solution."
"One of the main features of the solution is it allows the management of many devices in different ways."
"A great solution for anyone wanting a modern endpoint device management solution."
"It is a very helpful solution."
"The solution appears to be stable and scalable."
"The solution is scalable and provides over 100 rules."
"Installing the instances and performing upgrades is smooth and clean."
"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."
"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."
"Chef recipes are easy to write and move across different servers and environments."
"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."
"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 product is useful for automating processes."
"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."
"The most valuable feature is automation."
"In an upcoming release, I would like to see some kind of analytics report."
"Lacking ability to leverage more iOS device management internally."
"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."
"An area for improvement is the absence of seamless integration, particularly with external dashboards."
"Intune's third-party patch management could be better. It should be easier for the average system admin to keep non-Microsoft applications updated."
"The installation could be improved to be simplified."
"Integration with Mac devices requires some improvement."
"It would be nice to have a location tracker for the mobile device management tool. I'm not sure if it exists but hasn't been configured or if it's missing, but we've been unable to utilize the location features."
"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."
"There is room for improvement in built-in tools, they are not up to the mark."
"The solution is missing a configuration that can assist us when writing our programming languages."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"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."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"I would like them to add database specific items, configuration items, and migration tools. Not necessarily on the builder side or the actual setup of the system, but more of a migration package for your different database sets, such as MongoDB, your extenders, etc. I want to see how that would function with a transition out to AWS for Aurora services and any of the RDBMS packages."
"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."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"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 Config is ranked 15th in Configuration Management with 3 reviews while Chef is ranked 16th 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 SaltStack. 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.
