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."Being able to manage the devices remotely is most valuable. We can push security requirements through Microsoft Intune."
"The many policies available in Microsoft Intune for managing our devices are valuable."
"I like the group policy management feature, which performs application monitoring and device enrollment."
"The most valuable features in Microsoft Intune for me are application deployment, Defender deployment, and asset management."
"The solution has reduced the risk of security breaches by 30%."
"The technical support of Microsoft Intune is good."
"Fortunately, now everything is streamlined into a single, unified platform."
"It supports end-users who tend to lock their devices quite frequently. Its conditional access policy helps us keep the users logged into their devices."
"The nested stacks would be one of the more valuable features."
"AWS CloudFormation has automated the resource-building process, thereby removing the scope of human errors. We can tag the resources which help the billing process."
"Scripting does what we need to reinstall something from scratch."
"With CloudFormation, there is no need to use complicated coding."
"The most valuable features of AWS CloudFormation are all the resources documentation is located in one location, simple resource reverting, and ease of use of the full package for new users."
"It allows defining the infrastructure as code using templates, which describe the desired state of the infrastructure."
"The most beneficial aspect lies in its capability to handle input acquisition and assessment."
"I appreciate the flexibility of infrastructure as code. With CloudFormation, we can define ground rules, control usage limits, and scale our infrastructure up or down programmatically. Having this level of control through code on infra is a major benefit. That's the beauty of CloudFormation."
"The solution's initial setup is straightforward. The deployment process took me around ten minutes to fifteen minutes."
"It offers excellent scalability."
"Spring Cloud integrates well."
"It would be beneficial to have a more straightforward understanding of Intune's capabilities, presented in a simplified manner."
"Microsoft Intune lags market leaders, such as Apperian, in its MAM capabilities."
"The biggest problem we ever have is when something goes out of date after 30 days when nobody has logged into it. We do have a problem trying to get those back online. We've been working with Microsoft to resolve that problem, but that's been the only issue that we've had in the last few years."
"The feature that allows us to import the business application from the configuration manager to Intune is not very good at this time."
"The add-ons must be integrated into the solution."
"Deploying an app can be a complex process due to dependencies."
"Technical support is not that great."
"Once it's configured it is unobtrusive, but it does take some hands-on to configure and deploy it properly."
"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."
"They could improve the product's capability to handle circular dependencies more effectively."
"The code we write in AWS CloudFormation is pretty big compared to Terraform. We need to have more modules in the solution. A library should also be there where we can save code lines. A dashboard feature would be good for designers."
"There could be better error handling. It would be a good way to improve the solution."
"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."
"Provisioning a large environment or a large number of services takes a bit more time than with Terraform."
"The solution must enable more hands-on designing of the templates."
"Including certain examples of templates would be advantageous."
"If there's a dashboard like the ones provided by Apigee or Kong, that will be useful."
"It would be beneficial for the framework to become more lightweight and efficient when transitioning to the cloud."
"Stability is one area in the solution that needs to improve."
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.
