AWS CloudFormation Reviews

It serves as an automation framework for deploying infrastructure by using templates.

The most beneficial aspect lies in its capability to handle input acquisition and assessment. This feature allows users to input information, essentially functioning as a vendor, where values can be inserted and interest can be derived from the system.

Including certain examples of templates would be advantageous.

I have been working with for four years.

It is very stable. I would rate it nine out of ten.

I would rate its scalability capabilities nine out of ten. Our team exclusively relies on CloudFormation templates, and it consists of five to six individuals.

The level of technical support provided by AWS is excellent. I would rate it ten out of ten.

Positive

While currently working with Azure, we utilize distinct solutions tailored to the platform. However, it's worth noting that when we were using AWS previously, CloudFormation stood out as the preferred and superior choice for configuration.

The initial setup was fairly easy and I would rate it nine out of ten.

We handled the deployment internally with a team of four or five members. While maintenance typically only needs one person, it is currently managed by multiple individuals.

The pricing is not notably high. I would rate it two out of ten.

Overall, I would rate it ten out of ten.

We use AWS CloudFormation to build resources. 

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. 

I like the tool's updation capability for versions. The solution is good for scalability as well. 

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. 

I have been working with the product since 2016. 

I rate the tool's stability a ten out of ten. 

I rate AWS CloudFormation's scalability a ten out of ten. 

The solution is a service by AWS and does not involve deployment. We have installed the tool over the cloud. 

The solution's cost is normal, neither cheap nor expensive. 

I rate the solution a nine out of ten. You need to leverage AWS CloudFormation as much as possible to automate workflows.

I use AWS CloudFormation to create various types of resources like app servers, web servers, and S3 buckets. I know how to deploy these resources and understand how CloudFormation works, including best practices and different configuration options.

What I like best about AWS CloudFormation is that it is a quick and simple way to deploy various applications, like WordPress. You can use predefined templates, and if you are new to CloudFormation, it is easy to get started without much stress.

One area where AWS CloudFormation could improve is by offering more flexibility in creating custom templates. Currently, you can use default templates, but having easier ways to design your own templates, whether in JSON or YAML format, would be a helpful enhancement for users.

I have been using AWS CloudFormation for a year and a half.

It is a stable solution. I would rate it a nine out of ten in terms of stability. We have not had any issues with it.

It is a highly scalable solution. I would give the scalability a ten out of ten. In our organization, we don't have an exact user count, but AWS CloudFormation is widely used and popular. It is appreciated for its speed and user-friendliness when using template scripts with parameters. It also enhances security with encryption and permission features. CloudFormation is flexible for making infrastructure changes and is considered a valuable asset for our organization.

I had some issues with the technical support, but they were mainly because I had some experience with AWS CloudFormation. When creating a new stack and provisioning resources, you need to be careful with services that require global uniqueness, like S3 bucket names. If you don't use unique names in your code or template, it can cause errors. If you are not familiar with this, you might contact support, but often it is a simple fix by just changing the name yourself. So, having some technical know-how can help you avoid unnecessary support calls.

The initial setup of AWS CloudFormation is very easy and straightforward; you don't need any complex configurations or proxies. It takes less than a minute to deploy. I would rate the easiness of the setup a nine out of ten. If you receive clear instructions, using AWS CloudFormation is pretty straightforward. However, if you have to figure things out on your own, having some experience is important. Without experience, you might create resources that cause issues and encounter various challenges along the way.

My advice to new users is to have some prior knowledge before using AWS services. It is important to understand these concepts to make the most of AWS. I love AWS because it makes resource provisioning easier, especially with the user-friendly dashboard for creating various things. Overall, I would rate it a ten out of ten.

Our primary use case for the solution is mapping. We have used AWS CloudFormation and its components. We have used the mapping block resources, like AMI, to a particular region. The mapping block enables us to map keys to a corresponding name value that we specify in a conditional parameter. We have also used the output block to import resources, such as a security group, from one CloudFormation template to another. In a template, the output section describes the output value we can use in other stacks or the value returned when we need to review my stack properties.

Firstly the solution is reusable. The CloudFormation template can be reused to create multiple stacks, reducing duplications and improving our infrastructure and the parameter section maintainability. The parameter section is so essential and assists with automation. So with a single click, most of the resources have been deployed in the environment we want.

The parameter section is valuable.

A few areas need improvement, like enhancing error handling and integrating with other AWS services.

We have been using the solution for approximately three years.

I rate the stability as eight out of ten.

The solution is scalable. However, sometimes the issue is that it is not cloud agnostic. It's only used in AWS, unlike other solutions using a multi-cloud. I rate the scalability an eight out of ten.

The initial setup is straightforward.

I rate the price an eight out of ten, with ten being the most expensive.

I rate the solution a nine out of ten. The solution is good, but error-handling features can be improved.

I usually use AWS to deploy serverless solutions. I use API Gateways, Lambda functions, and Route Fifty-three for custom domains. I use everything from AWS services, including Glue jobs for ETL and integration with Databricks.

CloudFormation is a great tool for infrastructure as code, which makes my job very easy.

I love CloudFormation as it's a great tool for infrastructure as code. This makes my job very easy.

There could be more tools for conditional outputs in CloudFormation. Although YAML syntax is structured and AWS has CDK, perhaps more validations could be added to make the work easier.

I have been using AWS services for more than ten years, maybe.

I do not remember any problems with stability, so I haven't had any issues.

The scalability of CloudFormation is very good. I have never had a problem, and the service runs perfectly.

I had contact with Amazon support when I lived in Brazil. We had a technical account manager, and the support was very helpful.

Positive

I recommend CloudFormation to friends and family because it's a great tool. Explaining CloudFormation to them is very easy, like explaining a restaurant process.

I'd rate the solution ten out of ten.

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.

I use it to automate the creation of infrastructure using AWS CloudFormation templates. In my project, I must create infrastructure for SaaS-based applications hosted in the AWS cloud. Whenever I onboard a new customer, I need to create the same architectural infrastructure for them, as it's a multitenant architecture, so a lot of the setup remains the same.

By using AWS CloudFormation, I can automate tasks like creating VPCs and load balancers instead of doing them manually each time. The features I like most include improved scalability, resource management, ease of deployment, template creation, and resource provisioning.

There are some limitations with JSON, as the code is written in JSON, which doesn't support commands, looping, or conditionals. This can make the code difficult to read and share across teams. Moreover, the tool only supports AWS. 

Another challenge is related to cost, which I feel could be reduced as it's a bit on the higher side. Additionally, the documentation could be improved, as there is room for enhancement.

I have been working with the product for three years. 

I haven't faced any stability issues with AWS CloudFormation, and I would rate its stability as nine out of ten.

As for scalability, I see improved scalability with no issues, and I would rate it an eight out of ten. In my organization, around 18 people are using AWS CloudFormation.

AWS support is fine and prompt. It is paid. 

The initial setup is quite easy, like filling out a form and submitting it, making the deployment straightforward.

I rate the overall product an eight out of ten and would recommend it to others. 

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.