We performed a comparison between AWS CloudFormation and Spring Cloud 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."It is a very stable and scalable cloud-only solution."
"I believe that the solution is actually in Gartner's top quadrant at the moment for mobile device management."
"The solution has reduced the risk of security breaches by 30%."
"While I don't think you can ever have full visibility and control, Intune certainly allows us to see the applications being used and tells us if things like Windows patches aren't applied to machines. It does a good job. That visibility makes life a little easier."
"The initial setup is not overly complex or difficult."
"We are using the mobile feature, and we are also using MDM to lock the devices, to push restrictions, et cetera"
"With on-premises Active Directory, the main challenge was that we had no control when a user was working from home. We didn't know what exactly a user was doing and whether the AV was up to date or not. Intune provides better control of their machines."
"The biggest thing for us is enforcing logins only from devices that are managed by Intune."
"Since AWS CloudFormation integrates well with the AWS platform, it facilitates faster deployment. Building templates for AWS services within the solution is also straightforward, making the process easier."
"CloudFormation gives us control of AWS and any Cloud infrastructure. It creates the whole stack for Cloud services technologies so it's easy to manage the whole system."
"The nested stacks would be one of the more valuable features."
"I would rate the scalability a nine out of ten. We use it every day."
"With CloudFormation, there is no need to use complicated coding."
"Versioning makes our work easy."
"It is easy to work from the console and deploy new database services."
"Automations make it pretty easy to provision AWS, development, or deployment environments."
"It offers excellent scalability."
"Spring Cloud integrates well."
"The solution's initial setup is straightforward. The deployment process took me around ten minutes to fifteen minutes."
"Areas for improvement in Intune include expanding support beyond Samsung devices to accommodate other Android manufacturers like Redmi and Motorola."
"The synchronization could be improved."
"I expect Microsoft Intune to have more features in the cloud because there are two major functionalities that we need to be added. This is software metering and license management. These functionalities, for now, must be on-premise. For this purpose, we have set up a SQL Server and I hope that in near future this option will be in the cloud in Microsoft Intune."
"Regarding mobile devices, Intune is good, but there are other services that I would say are ahead of Intune from an administration and reporting point of view."
"It needs incorporation of Knox, ZeroTouch, etc."
"They should make it easier to order it, however, that's generally true for everything from Microsoft."
"It should be easier to define policies and comply with those policies."
"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."
"If you are a developer or a more technical person, it's very difficult to learn the complete syntax or because CloudFormation includes a new way to write infrastructure code."
"There could be better error handling. It would be a good way to improve the solution."
"As soon as they manage to parametrize the whole thing and to implement parameters at all levels, it will become automatically a lot more flexible."
"Provisioning a large environment or a large number of services takes a bit more time than with Terraform."
"The conditions that can be added in AWS CloudFormation are not as powerful as any programming language."
"The product should be made cloud-agnostic, allowing users to deploy the same environment with minimal tweaks across different cloud platforms, similar to Terraform. Additionally, it would be beneficial to have the ability to manage templates outside of the AWS environment."
"For a beginner, it's kind of difficult to set up. So, the user does need some knowledge in order to do it."
"They could improve the product's capability to handle circular dependencies more effectively."
"Stability is one area in the solution that needs to improve."
"It would be beneficial for the framework to become more lightweight and efficient when transitioning to the cloud."
"If there's a dashboard like the ones provided by Apigee or Kong, that will be useful."
AWS CloudFormation is ranked 8th in Configuration Management with 28 reviews while Spring Cloud is ranked 19th in Configuration Management with 3 reviews. AWS CloudFormation is rated 8.4, while Spring Cloud is rated 6.6. The top reviewer of AWS CloudFormation writes "Pretty easy setup with great automations for provisioning that save time and money". On the other hand, the top reviewer of Spring Cloud writes "Highly scalable development of cloud-native applications that offers an extensive range of tools and features, with significant learning curve and complex configurations". AWS CloudFormation is most compared with AWS Systems Manager, Red Hat Satellite, Red Hat Ansible Automation Platform and Microsoft Configuration Manager, whereas Spring Cloud is most compared with HashiCorp Terraform and Red Hat Ansible Automation Platform. See our AWS CloudFormation vs. Spring Cloud 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.
