AWS CloudFormation Reviews

The solution provides the most simplified way of managing resources.

AWS CloudFormation has improved our organization because it provides quick replication of all the infrastructure, and we can automate every process on the DevOp.

The most valuable feature of AWS CloudFormation is the simple tracking of infrastructure.

The speed of the replication process could improve. It can take some time to replicate that could use a speed increase.

In a new release, they should add multiple optimization release features.

I have been using AWS CloudFormation for approximately three years.

I rate the stability of AWS CloudFormation a ten out of ten.

I plan to increase the use of the solution in the future.

I rate the scalability of AWS CloudFormation a nine out of ten.

I rate the support of AWS CloudFormation a nine out of ten.

Positive

The initial setup of AWS CloudFormation is straightforward.

I have seen a return on investment using this solution after three years.

The price of the solution is good because it is scalable.

This is a powerful tool and you are able to increase efficiency and return employee workloads.

I rate AWS CloudFormation a nine out of ten.

AWS CloudFormation is being used for landing zone creation and DR purposes.

What I found most valuable in AWS CloudFormation is its configurability. The solution is easy to configure. I also like its change management configuration because that's also good.

What could be improved in AWS CloudFormation is its user interface, in terms of graphical design, I prefer WYSIWYG.

I've been working with AWS CloudFormation for several years now.

AWS CloudFormation has good stability and performance.

AWS CloudFormation is a scalable product.

The technical support for AWS CloudFormation is always good and fast. I would rate it five out of five.

The initial setup for AWS CloudFormation was easy.

We had some support from Amazon for the deployment of AWS CloudFormation. The deployment took a day to complete.

AWS CloudFormation doesn't have any cost because it's only the resources that you deploy with the solution that'll incur costs.

We didn't evaluate other options. AWS CloudFormation is our first solution.

I've been working with the latest version of AWS CloudFormation, as it's updated regularly.

My company deploys AWS CloudFormation for multiple customers, and I can't give an exact figure in terms of how many people use the solution.

My rating for AWS CloudFormation is ten out of ten.

My company is a partner of AWS CloudFormation, in particular, an advanced consulting partner.

My advice to new users of the solution is to go through the free online documentation and the video training on the AWS training site. This will help in evaluating and deploying AWS CloudFormation.

CloudFormation is infrastructure as code. For example, if you create an environment in an existing world, you can renew that code and implement the environment in another area.

Infrastructure as code enables AWS resources in the app configuration. The template file can be pressure-controlled. You could renew the code used for another section or environment and deploy it on another site. I also have automated resources management, which updates and rolls back.

CloudFormation's most valuable feature is infrastructure as code.

CloudFormation has languages like YAML. If it were applicable, I would like to work with other languages like Python.

I've worked with the solution for almost five years. I am using the latest version of CloudFormation.

I rate the solution's stability an eight out of ten.

I rate the solution's scalability an eight out of ten.

The initial setup is somewhat easy.

I have seen a return on investment.

I recommend that others go ahead and use CloudFormation. It will help them be sure that if their environments are done, they can renew that code and deploy it in another environment.

I rate CloudFormation a nine out of ten.

We use AWS CloudFormation for any migration tasks, such as service catalog services, Amazon EC2 instances, and load balancers.

The solution can be deployed on-premise, such as in data centers, and on the cloud, such as VPNs and gateways.

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. 

The conditions that can be added in AWS CloudFormation are not as powerful as any programming language.

I have been using AWS CloudFormation for approximately four years.

The solution has been working well.

We have approximately three people using the solutions.

My clients have used AWS CloudFormation support. 

I have used Terraform and it has similar benefits as AWS CloudFormation. We are using AWS CloudFormation mainly because all of the other services we use are from Amazon AWS.

We had a vendor that set up the solution for our company.

If you compared serverless and container-based, serverless is less expensive. If you use certain instances the price can increase and become too expensive.

I rate AWS CloudFormation a seven out of ten.

I create cloud infrastructure using CloudFormation. It helps us a lot to manage or monitor the whole infrastructure.

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. If we are creating a platform which includes certain services of AWS, it is very difficult for us to see or manage the whole service related to that specific platform.

CloudFormation provides us with a single and easy way to handle those services of that particular application. If I want to shut down the whole system, I don't want to go to each single service related to that specific particular product. Using this solution, I just run the command to the CloudFormation to shut down the whole system. It will shut down each and every service related to that particular system.

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 is a technology called CDK and it provides a unique way to handle the infrastructure of every Cloud technology. 

CloudFormation should include compatibility with the programming languages or latest technologies. 

I have been using this solution for three a half years. 

We have experienced some issues with stability with current incidents we are developing on a server level. 

I would rate the scalability for this solution an eight out of ten. 

I have collaborated with AWS support many times for big data but not related to CloudFormation. I would rate the support for this solution a ten out of ten. 

Positive

It is very easy to set up. We just have to create a file or the stack for the related services that we are currently working on. Deployment time depends on the stack and on the services. It takes a longer time if done manually. When setting up a simple service, I would rate the set up a ten out of ten. 

I have set up the whole CloudFormation infrastructure on my own because I'm AWS certified. 

We evaluated Terraform. It provides a single platform to manage all the Clouds. We just have to write a single stack code and it is compatible with each and every Cloud platform like AWS, GCP and Azure. The drawback of CloudFormation is that it is only compatible with AWS.

I would rate this solution an eight out of ten. 

We use this solution for application hosting and utilize the caching mechanisms. 

The cost of licensing could be reduced. 

We have been using this solution for one year. 

This is a stable solution. 

This is a scalable solution. 

For the cost point of this solution, the customer service and support is quite good.

Positive

The initial setup is straightforward and took approximately four weeks. 

The implementation was completed by an external consultant. 

I would recommend the use of this solution. 

I would rate it an eight out of ten.

We use it for deploying all the Infrastructure: VPCs, EC2 instances, storage solutions, most managed services. Providing IAM configuration, providing group account configurations, role management within IAM.

CloudFormation is THE Infrastructure as Code (IaC) solution AWS recommends.

Almost everything should, according to AWS, be automated and managed using CloudFormation - whenever possible. 

Within our organization, mostly the DevOps engineers use AWS CloudFormation — around 42 of them.

I don't really care how my organisation is functioning; I care about the way that my client's organisation functions. That's what I'm after. We host workshops teaching people the DevOps transformation process, how to do infrastructure automation — almost everything. 

Of course we do the same internally, but our internal needs and use-cases don't, even, come close to our Clients'.

First off, It's fairly easy to work with, although a bit verbose. It is legible. You can understand what you're doing. The introduction of "nested stacks" allows a modular design and repeatable  structures. The nested stacks would be one of the more valuable features. I am waiting for them to become much better with parameters as this is not quite up there.

The one bit of a drawback is that CloudFormation is, only, available in AWS.

When I have to work on other clouds or somebody has a configuration to be done on-prem Data Center, there's no way for me to use it.

It is what it is, AWS does not apparently intend to make this available all over.

The three big players in this area are Ansible, Terraform, and CloudFormation — except CloudFormation can only be used on AWS !

I would like to see less verbosity and better isolation.

One area that may be improved would be using variables as parameters in templates. This would make it a lot more flexible.

I don't know how soon that's going to happen because I'm trying to think from a developer's point of view - the guys that actually have to write and support all these features that I dream about.

Frankly, to evolve it but also maintain compatibility with what's in place now, may be a serious challenge.

I have been using AWS CloudFormation for just over one year.

It's definitely stable. If it's not a long-running service, and this one's not, it's very easy to verify that you've got it where you want it. 

Just run a deployment, then it's very easy to look at the configuration and see exactly what came out. The easiest verification is the intuitive visual check-out.

There are ways to test around in the sense that you're not forced to use CloudFormation to see that it's correct. You can literally, visually inspect the configurations with the console and other means not using CloudFormation. There's always a way to verify, and the fact that you have a verification method available is convenient.

If you want to deploy thousands of components - not only virtual machines, but, also, users, roles and services, in any of the AWS regions — it's not a problem.

Frankly, I never had a problem, with AWS CloudFormation, per se.

Something advertised that doesn't work and to require support, that actually has never happened.

I did use another solution, which is Ansible, but I didn't switch. I'm still using Ansible as a backup for those cases where CloudFormation does not cover. Also, outside AWS, where CloudFormation is not available.

CloudFormation is setup by AWS by default. It's easy and it doesn't require you to do anything.

When you create your infrastructure, there is no need for you to deploy anything like agents; everything is already in there.

It's very convenient in the sense that you don't need to worry about updating, upgrading, patching or monitoring for liabilities. AWS takes care of all of that.

There's probably a lot of people that are trying to work around it. Or, to avoid it. My advice would be: use it when Amazon says so because it's probably the most straightforward approach to your problem. Afterwards, then you can become creative, for it's worth putting in the effort.

On a scale from one to ten, I would give this solution a rating of seven.

That rating would, definitely, be higher if CloudFormation would be made available on other platforms, outside Amazon.

Once we build a CloudFormation template, we use it regularly. We use the solution to build the backend infrastructure of Amazon Connect.

The reusability of the solution is valuable. Once CloudFormation is built, we can reuse it as many times as we want. We can make changes and deploy it within seconds. We can deploy the whole infrastructure within minutes. If we build individual infrastructures, it would take much more time.

The solution must enable more hands-on designing of the templates. We take the backend services and design the templates. The design must be drag and drop.

I am happy with the support.

Positive

The installation was not challenging.

If someone wants to use the product for the first time, they must learn the basics of cloud infrastructure. It's not easy for a beginner to learn. We must know the basic infrastructures, our requirements, how Amazon functions, and how the cloud functions. Cloud infrastructures have their own way of functioning. We must set EC2 instances and private virtual clouds. We must be aware of such things. As a tool, AWS CloudFormation is very good. Overall, I rate the product an eight out of ten.