We performed a comparison between AWS Config and AWS Systems Manager 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."The initial setup is not overly complex or difficult."
"Users can make screenshots, and devices only need the minimal version of iOS."
"We can manage and standardize security across your environment, identify problems, receive alerts, and so on. That's its purpose, and that's also why it's so good."
"In terms of technical support, you will get an immediate response."
"Autopilot is the most valuable feature."
"Agile and easy to deploy MDM solution that covers the maximum number of policies. Stable, scalable, and with knowledgeable technical support."
"Internet-based access with security is what I have found to be most valuable. It is also a stable and scalable solution."
"The Asset Management and Auto Pilot are valuable features."
"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."
"The scalability is a ten out of ten."
"Installing the instances and performing upgrades is smooth and clean."
"Systems Manager has a feature where it analyzes the logs and gives us a performance overview in the form of a graph. We know when it's taking up more resources and when there are spikes, so we can predict the usability."
"With AWS Systems Manager, our company can patch our systems directly from it, so we don't need to patch our systems manually."
"When we do the automation in the cloud, we use the SSM agent. This helps us to test our automation and documents, and monitor the cloud."
"Has a variety of automation options."
"The solution is user-friendly"
"AWS provides Auto Scaling groups."
"The solution's ability to scale is good."
"Additional application deployment options e.g. MSI deployment with more complex parameters or additional side-by-side files, and non-MSI deployment options."
"There can be more logs. I do not have any other requirements."
"One big problem with Microsoft is that they're changing the names of the products quite often, or they're quite consistently doing so. Intune is now Endpoint administration. Constantly switching the user interface or the administrative interface makes it quite hard to keep pace. If you are on a two-week holiday and you come back and look at the same screen you have looked at for the last couple of months, it looks different, which is annoying. Changing things around all the time doesn't make it easy."
"The solution could improve its flexibility."
"Its configuration is fairly complicated. You have to do quite a bit of discovery to be able to deploy it for a customer. You have to ask them a lot of questions. So, its initial deployment is the biggest challenge. They should make it easier to deploy with the use of Wizards or something else. During the deployment stage, there could be profiles for the customers who are particularly wanting to use certain feature sets of Intune."
"The initial setup is a little bit complex."
"While Intune works perfectly well, the only potential downside is that the deployment could be a bit complex for some users."
"An area for improvement is the absence of seamless integration, particularly with external dashboards."
"Improvements are needed as per customer requirements."
"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."
"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."
"AWS does not have EKS cluster backup."
"The AWS UIs are not the most intuitive. Also, the usability needs room for improvement."
"The current challenge is that we can't pull any incidents from other accounts."
"The fact that AWS Systems Manager takes time to complete the patching process, makes it an area where improvements are required."
"Lacks sufficient integrations."
"We formerly used third-party products to analyze the log, give us information, and find bottlenecks. Systems Manager could provide more tools that conduct this analysis, so we don't have to do it ourselves."
"Additional features can be added as per customer requirements."
AWS Config is ranked 15th in Configuration Management with 4 reviews while AWS Systems Manager is ranked 6th in Configuration Management with 7 reviews. AWS Config is rated 9.0, while AWS Systems Manager 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 AWS Systems Manager writes "Offers a variety of automation options; simplifies governance and administration ". AWS Config is most compared with Spring Cloud, whereas AWS Systems Manager is most compared with Microsoft Configuration Manager, Red Hat Ansible Automation Platform, Red Hat Satellite, AWS CloudFormation and SUSE Manager. See our AWS Config vs. AWS Systems Manager 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.