G2 Crowd builds the world's largest business commerce platform fueled by $100M in funding šŸš€

AWS CloudFormation

4.2
(27)

AWS CloudFormation allows you to use a simple text file to model and provision, in an automated and secure manner, all the resources needed for your applications across all regions and accounts.

Work for AWS CloudFormation?

Learning about AWS CloudFormation?

We can help you find the solution that fits you best.

AWS CloudFormation Reviews

Chat with a G2 Advisor
Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • Industry
Ratings
Company Size
User Role
Industry
Showing 27 AWS CloudFormation reviews
LinkedIn Connections
AWS CloudFormation review by Travis G.
Travis G.
Validated Reviewer
Verified Current User
Review Source

"CloudFormation - Dead easy DevOps"

What do you like best?

My favorite part of CFN (CloudFormation), is the ability to use YAML for the templates. Originally templates needed to be valid JSON documents. From a programmatic standpoint JSON would be better, but from a human readable/ease of use standpoint I greatly prefer YAML over JSON for my templates. However, the most important features of CloudFormation is that, 1) It allows for extremely rapid resource deployments and tear downs; Ideal for testing environments or Blue/Green capable infrastructure. This is because CFN will evaluate your configuration template and determine which resources can be created simultaneously and the correct order in which to deploy resources, so you are far less likely to run into "non-existent dependency" issues with your deployments. 2) The ability to create multiple "stacks", as they're called, and have other stacks reference output data from a previously created stack. A simple example would be: creating a stack to build a VPC, subnets, routes, and basic security groups. Setup the stack to output the subnets and security group(s) information so then if you create a new stack for creating servers you can quickly retrieve subnet and security group resource information without having to input that data manually.

What do you dislike?

CloudFormation has a lot of little gotcha's. Anyone new to DevOps or configuration management will really need to be on the look out for 'optional' (but 'required') settings when creating CFN templates. An example that comes to mind is the Security Group resource. It has an optional setting to specify a "VPC ID". This setting is optional because early AWS didn't have VPC's and Security Groups were just created and attached to instances directly. However, any environment where there is a VPC requires that you specify the VPC ID in the CFN template otherwise you'll create a "legacy Security Group" a.k.a. An EC2 Security Group instead of the proper "VPC Security Group". While learning about CloudFormation I spent enough time banging my head to want to advise anyone reading this to watch out for things like that. The documentation provided by AWS is solid and will inform you of those gotcha's but when quickly skimming the pages it's easy to miss.

Recommendations to others considering the product

Beware of template gotcha's! If your stack doesn't pass validation you won't have to worry about an infrastructure breaking change being made to your environment. However, you will spend a ton of time banging your head against your desk if you miss them. If something in your CloudFormation template isn't working, re-read the documentation for the resource you are trying to create and be on the lookout for those gotcha's. If it's still not clicking Google with be your next best friend.

What business problems are you solving with the product? What benefits have you realized?

I've recently rebuilt my VPC from sratch using CloudFormation for my company. The best solution that I have realized already is that I was able to deploy an Identical VPC for my testing environment, the only change being the IP addressing. I'm still working through templating the rest of my infrastructure to CloudFormation so I can redeploy as IaC (infrastructure-as-code). Another, problem I am solving by having my infrastructure setup as code is that any changes made, can be setup and tracked with tools like github/bitbucket and and damaging changes can be quickly reverted to a working version. DevOps for the Win!

Sign in to G2 Crowd to see what your connections have to say about AWS CloudFormation
AWS CloudFormation review by Sabitha M.
Sabitha M.
Validated Reviewer
Verified Current User
Review Source

"Building on demand infrastructure through Cloud Formation"

What do you like best?

Cloud formation helps one to put infrastructure as code .Individual Amazon resource can be put together as code in cloud formation template and create infrastructure with minimum effort and within time. Cloud formation template is easily understandable , it is written in json or yaml. Once cloud formation template is launched it shows user to select parameters from console. These parameters are defined in cloud formation templates . User can build complex infrastructure through CFT's and easily viewed on cloud formation services on AWS.If stack deployment is failed cloud formation template has capability to roll out the infrastructure and user can select to delete. User can easily update the new changes to existing stack through update option , if any failures stack with automatic roll out and delete the new changes which reduces lot of time on individual user to check . Errors can be easily view on the console, resource creation can be view and directly linked to the resources. Output of cloud formation can be configured in templates so that new user can able to understand what as configured. Using CFT user can create IAM roles,policies, Auto scaling group,Elastic load balancers and application code can be excuted when instance is getting started or at boot time through User data. User can automate application deployment through user date and make common tools available while bringing up the service.

Cloud formation is easily integrated with Jenkins for automation and errors can ve validated through error state codes through aws cli commands so that one can view the status onJenkins. Charges are applicable for the resource usage

What do you dislike?

writing conditions is little difficult in cloud formation templates

Recommendations to others considering the product

Recommened

What business problems are you solving with the product? What benefits have you realized?

It solved manual effort to create infrastructure in repeatable manner.User can build their own VPC, Instances,Autoscaling groups, And new IAM roles with small change in code

And new instances are having common tools tools installed before they start using through USer data.On the AWS cloud formation control every one can sed the resources created as part of stack creation and see who has access to what

What Continuous Deployment solution do you use?

Thanks for letting us know!
AWS CloudFormation review by Dan O.
Dan O.
Validated Reviewer
Verified Current User
Review Source

"Infrastructure as Code. Great, but there is a learning curve. "

What do you like best?

It's effectively a documented build sheet, except all of your infrastructure can be built automatically from code. Cloudformation is able to setup resources across the AWS stack and across all regions, it's free and you only pay for the resources that you use/deploy. It can be managed from a CLI or API. Code (JSON) can be built from a drag and drop GUI or by hand.

What do you dislike?

Whilst you can export the output values of a stack, you can't export the Cloudformation script of the infrastructure that you have built. Whilst Cloudformation will help you create and provision infrastructure, you've still got to build and deploy the applications on those infrastructures - it's only part of the puzzle of tools that you'll need to gain familiar with on the AWS stack.

What business problems are you solving with the product? What benefits have you realized?

Automatic creation of website infrastructure, provides the ability to build an instance for development work to proceed and stop using it overnight thus lowering the overall hosting cost.

AWS CloudFormation review by Konstantin V.
Konstantin V.
Validated Reviewer
Verified Current User
Review Source

"CloudFormation as a virtual applience"

What do you like best?

I like the idea of creating a self-containing CloudFormation templates (with inline Lamnbdas) to solve a business task. Just send CFN template as an attachment to an email.

What do you dislike?

I think Amazon should provide a marketplace for pure CloudFormation solutions. So we should be able to sell them and track the usage at the same time. So some surrounding with licensing is required to unfold the whole new market of cloud "paper-based" appliances.

Size limit for a CloudFormation template when run within inside a AWS CodePipeline

Recommendations to others considering the product

CloudFormation is integral part of server-less Ci/CD on AWS. I would recommend to anyone to use AWS CloudFormation + AWS CodePipeline + AWS CodeBuild stack.

What business problems are you solving with the product? What benefits have you realized?

CloudFormation is a part of our CI/CD strategy; Cloud appliances;

AWS CloudFormation review by Manil C.
Manil C.
Validated Reviewer
Verified Current User
Review Source

"CloudFormation is great but sadly supported only on AWS"

What do you like best?

It is become more and more difficult to choose the right provisioning tool to build even the relatively complex infrastructure on any Cloud provider. For AWS, what you would be looking for is the ability to provision resources (e.g. EC2, VPC) and the ability to reuse the same configuration to build multiple environments (e.g. development, staging and production). CloudFormation address these two concerns, it is a template driven that can be used to leverage the infrastructure as code paradigm. It is provided by AWS and thus garante the ability to automate the provisioning of any AWS service with their respective latest configuration parameters unlike other tools like terraform that tend to provide generic resource representation despite the target Cloud provider. CloudFormation handles failure nicely, it gives you the possibility to rollback changes to the infrastructure to a last stable configuration.

What do you dislike?

CloudFormation is tide to AWS and cannot be used to provision resources on any other Cloud provider. CloudFormation is maintained by Amazon and no community involvement is possible. Also, the templates writing for CloudFormation tend to be too long (it is a JSON document) compared to other tools that provide a concise DSL (Domain Specific Language). Furthermore, some AWS services (especially new one) are not fully supported by the CloudFormation syntax.

Recommendations to others considering the product

CloudFormation is the right tool for building infrastructures on AWS but if you need a provisioning tool that support multi-cloud environment than it's not the way to go.

What business problems are you solving with the product? What benefits have you realized?

We were charged by a client to migrate some services from it's own data center to the AWS cloud. The task consisted of building similar environment one for each delivery stage (staging and production). The team was mostly composed of DevOps consultants, a handful of ops guys and a solution architect. We ended up choosing CloudFormation as our migration tool thanks for its deep integration with AWS which made the task less painful for us.

AWS CloudFormation review by Austin C.
Austin C.
Validated Reviewer
Verified Current User
Review Source

"basic deployment orchestration service"

What do you like best?

Everything can be deployed with cloudformation in an AWS environment.

What do you dislike?

Communication between cloudformation deployments is growing, but still incomplete.

Recommendations to others considering the product

If you're doing deployment orchestration in AWS you will need cloudformation. If you have complicated deployments, you will need some sort of system to augment cloudformation, because it won't cover everything.

What business problems are you solving with the product? What benefits have you realized?

Repeatable deployment orchestration in an AWS environment has to be done with cloudformation, and it does a good job of handling it.

AWS CloudFormation review by Joshua P.
Joshua P.
Validated Reviewer
Verified Current User
Review Source

"A powerful tool, broadly applicable to other AWS services"

What do you like best?

Nearly every service AWS offers can be enumerated and configured using CloudFormation. For simple syntax checking, JSON is a great format. The available tools for working with CloudFormation templates in IDEs or browser editors is steadily growing, and AWS has released their own visual editing tool which allows less-experienced users to quickly create an environment template and deploy it using CloudFormation. For more advanced users, CloudFormation templates are a powerful and complete means of deploying entire environments in AWS.

What do you dislike?

CloudFormation does not always receive the very latest features for every AWS service when they are launched. This diminishes the effectiveness of this tool for describing and building entire environments from CloudFormation templates, which can increase the time it takes to perform a rebuild or recovery.

Recommendations to others considering the product

Manage your templates in a revision control (source control) system.

Ensure any iterative changes or extensions to existing configuration (e.g. new security group rules, new systems, everything really) make it into the appropriate CloudFormation template.

Make use of variable declarations and run-time template inputs: do not hard-code resource names or other attributes. You never know when you will want to stand up an exact copy of your environment, and name-space conflicts will prevent you from doing that with CloudFormation!

If you have a production environment which leverages more than 1-2 AWS services, but lack hands-on experience with CloudFormation, definitely enlist the expertise of an AWS Certified consultant or an Amazon Partner Network member who has deployed production environments with CloudFormation before.

Do not try to enumerate an entire environment in a single template. Instead, use at least one template per AWS service: have a template file solely for each type of resource such as RDS, EC2, VPCs. Subnets and security groups within a VPC should go in the template for that VPC (keep dependent resources together in a single template). If you have resources which may be changed or replaced frequently, separate them from resources that change little and absolutely keep templates for database systems separate from all other resource types.

What business problems are you solving with the product? What benefits have you realized?

CloudFormation permits the teams we work with to track changes to an environment's infrastructure as code, and provides a simple disaster recovery mechanism in cases where resources might be mistakenly or maliciously deleted. Strictly enforcing infrastructure configuration changes in CloudFormation means we never have to worry about whether a change will persist, and lets us quickly re-deploy entire environments "from scratch" with minimal effort.

AWS CloudFormation review by Ricardo A.
Ricardo A.
Validated Reviewer
Verified Current User
Review Source

"Excellent tool for bringing up multiple AWS services at once, but challenging to debug"

What do you like best?

The fact the with one click of a button I can bring a full stack of services for my application. Just fire and forget, generally if the cloudformation template is bug free.

What do you dislike?

The template is purely in JSON (although JSON is a popular data representation format and generally is easy to read) which makes it difficult to debug if you missed a comma or close quotation, etc. It's also difficult to debug if you are have included the right services or right "String" configuration for your service. This actually gets a bit easier if you use tools like troposphere, but out the box is not that easy to debug.

Recommendations to others considering the product

You generally need to become an expert at debugging JSON with this tool but like I mentioned before there are open source tools that you can use for that such as troposphere. Also, once you move to CloudFormation you generally want to keep using it to bring up all your services for your application because there's no way to decouple parts of the services used in your application. Unless you create another service or microservice to handle parts of the functionality of your application.

What business problems are you solving with the product? What benefits have you realized?

Bring up full stack of services for a software solution in our company with just a click of button. The benefit there is that we reduce the chance of human error but fully automating the bring up of all the AWS services required instead of just bring them up one by one.

AWS CloudFormation review by Sheehan A.
Sheehan A.
Validated Reviewer
Review Source

"Great tool for automatically provisioning and deploying your cloud native apps"

What do you like best?

CloudFormation is a free service that comes with your AWS subscription that allows you to define a template for all of your cloud resources and launch them in a predictable and reliable way. You can write either JSON or YAML to define all of your instances, databases etc. and then launch them into production without having to do any manual operation. This is a great way to start diving into the world of devops and continuous delivery.

What do you dislike?

CloudFormation is not as robust as Chef, Terraform or other competitors. Specifically, what you configure is what you ultimately launch. Tools like Terraform will allow you to visualize your "Plan" before you launch it, in case you want to edit it before launching. This makes it easy to prototype and set configurations without having to launch them into production to test.

Recommendations to others considering the product

You can use other AWS tools such as AWS Config to get a baseline snapshot of your infrastructure. It will create a CloudFormation template for you, and then you can use that baseline to create other cloud formation templates for all of your applications. This will save time, from having to do the initial cloud formation creation up front.

What business problems are you solving with the product? What benefits have you realized?

We are trying to automate the deployment and setup of our cloud infrastructure using infrastructure as code. One of the biggest benefits of cloud computing is the ability to instantiate and terminate resources on demand. CloudFormation is a key pillar in providing these setup capabilities through code.

AWS CloudFormation review by Arjen S.
Arjen S.
Validated Reviewer
Verified Current User
Review Source

"CloudFormation is an excellent tool for organizing your AWS infrastructure"

What do you like best?

CloudFormation allows you to easily create an infrastructure, and most importantly it allows you to keep track of the changes you make. This also means that you can quickly copy the infrastructure for a different environment (QA for example) or even an entirely different region.

What do you dislike?

As the templates are written in JSON, it's impossible to put comments inside them. There are ways around that, but it is a limitation in the tool.

Recommendations to others considering the product

If you're going to be using AWS infrastructure, CloudFormation is probably the easiest way to manage it. There are 3rd party alternatives, but using Amazon's solution offers the best support.

What business problems are you solving with the product? What benefits have you realized?

With CloudFormation I can quickly set up new environments, making it far quicker to set this up for different clients. As it's all code, I can also easily reuse (parts of) a template for different uses.

AWS CloudFormation review by Paulo Vitor R.
Paulo Vitor R.
Validated Reviewer
Verified Current User
Review Source

"Making the infrastructure admin's life easier"

What do you like best?

CloudFormation is one of the amazing parts from the AWS ecosystem. The flexible and reusable way you can handle a group of services, like a template, makes any infrastructure admin's life much easier.

What do you dislike?

I don't think it's a huge limitation but so far it's not possible to name the resources once they are created by CloudFormation. The main reason for this is to avoid name collision between resources which is fair enough, but still, sometimes I miss it.

What business problems are you solving with the product? What benefits have you realized?

I would recommend this service for environment replication (easily allowing A/B tests and ephemeral environments). I used this service a couple of times to create environment templates and then I was able to recreate them many times. Very useful for building environments or even replicate production environments to debug problems.

AWS CloudFormation review by User
User
Validated Reviewer
Verified Current User
Review Source

"AWS CloudFormation"

What do you like best?

CloudFormation makes it easy to define Cloud Resources and perform consistent automation by creating resources via CloudFormation instead of manually creating things each time.

It supports both JSON & YAML which is nice as well.

What do you dislike?

While easy to use, digging down to finding the CloudFormation template documentation can be rather annoying- it's a bit hidden on the AWS website. But once you bookmark it, you're set!

What business problems are you solving with the product? What benefits have you realized?

Automation needs & it has saved us time and effort by being able to define a resource once and then consistently re-deploy a stack

AWS CloudFormation review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Review Source

"Creating/Deleting all AWS resources using single service"

What do you like best?

1) Cloud Formation has integration support with almost all the AWS services. You can create all the resources you need in one step using a cloud formation template. Deleting the appropriate template will also delete all the resources created by it. This way managing of AWS resources becomes very easy. Without Cloud Formation you have to individually make calls to either create/delete the resource and needs to track the related resources. CloudFormation is good at solving this problem.

What do you dislike?

1) Only JSON support.

2) Lot of eventual consistency issues while deleting some of the AWS resources created using CloudFormation. Need to invoke delete multiple times.

3) Cloud Formation for new services with the launch of new service would be great rather than to wait for sometime.

Recommendations to others considering the product

1) If you want to maintain multiple AWS resources at single place cloud formation is the place to go. Its like infrastructure as a code where you can specify all the infrastructure needed to run something as part of single template and let the template create all the resources you need. It also supports parametrization which is helpful for interactions between multiple resources.

What business problems are you solving with the product? What benefits have you realized?

Used this for creating or scaling multiple environments like testing, beta, gamma, prod. Not only creation but tearing down these environments.

Used this to setup services running in EC2 with all the VPCs, Security groups, subnets etc. These servers are used to hosting multiple websites.

Benefits:

1) Hassle free maintenance of multiple AWS resources using one service.

2) Scaling up/down is super easy with launching new templates or deleting the existing ones.

3) Good support in console with drag and drop support.

AWS CloudFormation review by Jonathan H.
Jonathan H.
Validated Reviewer
Review Source

"I've use cloudformation for about one and half year"

What do you like best?

I like the ability to create nested stack (using a stack to create another stack), this feature allows us to create a button up or top down design of the architecture and achieve the structure as code goal.

What do you dislike?

The document and the cloudformation function/feature is not always up to date with latest amazon features, so that sometimes we have to enable the feature from the AWS Web console manually or using AWS cli to enable that new feature.

Recommendations to others considering the product

It's hard to tell that cloudformation can do much if you are running small architecture at single environment. But if you run your business in different amazon regions with multiple environment, You should consider use cloudformation to manage all the architecture and deployment, it's quite easy to integrate with chef (or just shell script).

What business problems are you solving with the product? What benefits have you realized?

As an system engineer in a cellphone company, we have to handle multiple environment such as dev/test/staging/production. It become much more easy to create a new environment in new region or crate a sandbox environment during testing cycles with cloudformation template and chef, and it allows us to make both architecture and deployment changes at the same time which reduce both time and costs to deal with the inconsistence of different environments.

AWS CloudFormation review by Duncan H.
Duncan H.
Validated Reviewer
Review Source

"Cloudformation - infrastructure as code"

What do you like best?

Ability to manage our infrastructure in code, keeping it version controlled.

What do you dislike?

Some new parts felt a bit clunky, like the ability to export restful swagger for use in the template. Its improving rapidly though! Not a deterrent.

Recommendations to others considering the product

If you are bound to AWS this is great, if you have plans to move away you could look into Terraform

What business problems are you solving with the product? What benefits have you realized?

Moving this to code has enabled non devops engineers to understand the architecture without having to log into the console. At a high level it provides documentation of the setup.

AWS CloudFormation review by Simone S.
Simone S.
Validated Reviewer
Review Source

"Professional"

What do you like best?

I'm a JSON lover, and I like the idea to keep everything I need under control by simply describing the infrastructure. It may sounds a bit verbose (it is), but I'd rather prefer it than creating resources via the Console, since I can't reproduce it in case of disaster recovery or rollback.

What do you dislike?

It's pretty powerful. Maybe the lack of versioning of the infrastructure. At the moment I'm implementing it by myself, by storing the templates along with the codebase on Git). The documentation cover all the aspects, but I would improve the examples. Sometimes I prefer look for a snippet on Google rather than using the official docs

Recommendations to others considering the product

Using a library that generates the template programmatically is tempting, and is often useful. But if you want full control of Cloudformation, better go plain JSON.

What business problems are you solving with the product? What benefits have you realized?

The entire infrastructure of the components I contributed to develop (stateless/stateful resources) has been described and set under revision control. The benefit is that I can reproduce my infrastructure, and gain more control over the rollback (which is not only a matter of codebase).

AWS CloudFormation review by User in Computer Software
User in Computer Software
Validated Reviewer
Verified Current User
Review Source

"If you love JSON, you'll love CloudFormation"

What do you like best?

My favorite feature of CloudFormation is the ability to natively group resources. As an operations engineer I often find that business requirements change fast, and you need to stand up services in a consistent and repeatable fashion.

Properly designed CloudFormation stacks serve this need. Although there are a number of frustrating limitations I still find it easier to use than something like boto/troposphere.

What do you dislike?

I wish that Amazon would offer CloudFormation resources for all of their services. As an example, they released ElasticSearch but have yet to provide any CloudFormation APIs to deploy these resources. It is also really confusing and frustrating to learn, especially things like data types in nested stacks and the proper usage of AWS::NoValue.

Recommendations to others considering the product

If you have a lot of resources and need to easily manage many stacks, look at a Cloudformation template management tool such as Ansible. Using the EC2 API to query things like security group IDs is helpful and can eliminate a lot of the drudgery of maintaining parameter files.

CloudFormation is JSON, but it's also still code. You can't really add comments, but you can define organizational standards and make sure that your team sticks to them. Peer review and VCS management of your CF stacks is essential.

What business problems are you solving with the product? What benefits have you realized?

It provides repeatability and consistency across team members. It really shines when you need to decommission infrastructure. You don't have to rely on tagging or tribal knowledge to find all of the resources to delete when shutting down resources.

AWS CloudFormation review by Bryan M.
Bryan M.
Validated Reviewer
Review Source

"AWS CloudFormation experience"

What do you like best?

Allows us to quickly implement true "infrastructure as code" on AWS; also, excellent documentation and examples really helped us climb the learning curve quickly.

What do you dislike?

I wouldn't call it a dislike but it seems like a graphical editor would allow users to visualize their environments while generating the required JSON in the background. The only other complaint I really have is the overall performance of complicated CloudFormation runs - the develop/debug process can be quite time-consuming.

Recommendations to others considering the product

If you are targeting deployment on AWS, CloudFormation is extremely powerful. The ability to merge core infrastructure with AWS platform services, all tied together with security groups, and network routing is extremely powerful.

What business problems are you solving with the product? What benefits have you realized?

We are building a new multitenant platform to support a suite of products for our public safety products. We are developing in public cloud regions but finalizing test, staging, and production in the AWS GovCloud region.

AWS CloudFormation review by Darun J.
Darun J.
Validated Reviewer
Review Source

"Why AWS CloudFormation?"

What do you like best?

AWS CloudFormation allows you to create a template using almost all the services from the AWS environment. This allows us to replicate any model within minutes.

What do you dislike?

The block design UI used to create a YAML template could be improved.

Recommendations to others considering the product

Best tool to replicate any architectural design

What business problems are you solving with the product? What benefits have you realized?

Created a chatbot with AWS lambda, Redshift and API gateway. Used CloudFormation to replicate this model for different clients

AWS CloudFormation review by Administrator in Computer Software
Administrator in Computer Software
Validated Reviewer
Verified Current User
Review Source

"AWS Cloudformation"

What do you like best?

it work well with many amazon components almost all amazon services as compared to its competitors like Chef Provisioning or Bosh.

it has capabilities to update the stack which is good.

What do you dislike?

work well with in AWS only, you can not reuse the work if you are not on AWS. like other tools chef provisioning or bosh which can work on other cloud provider.

Update do not update current machine user data which is good and bad

Recommendations to others considering the product

all in AWS solution CF is best .. in class and have most AWS services then any other tool

What business problems are you solving with the product? What benefits have you realized?

creating software stack on AWS with LB, machines DB's

AWS CloudFormation review by Administrator
Administrator
Validated Reviewer
Review Source

"Oh my god why?"

What do you like best?

AWS updates it; supports the latest features

What do you dislike?

My team found that once we started trying to break it apart and make it modular it was difficult to end up with anything that anyone enjoyed working with. We disliked it so much that we ended up writing our own python-based abstraction around it that allowed us to use simple and flat CloudFormation templates and connect them to each other via python code.

Recommendations to others considering the product

Supported by AWS so always up to date.

What business problems are you solving with the product? What benefits have you realized?

Infrastructure as Code. Allows us to use version control to store the templates.

AWS CloudFormation review by Tzu-Chi Y.
Tzu-Chi Y.
Validated Reviewer
Verified Current User
Review Source

"Easy to use with prepared configuration json"

What do you like best?

I like the way that we can design our infrastructure using pure GUI.

What do you dislike?

I may need better knowledge of the backend for fine-tuning the infrastructure.

Recommendations to others considering the product

Need better small examples for CloudFormation configurations, so that newbies get easier to learn it.

What business problems are you solving with the product? What benefits have you realized?

I just want to set up the private VPN to use in China.

AWS CloudFormation review by Consultant in Information Technology and Services
Consultant in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Invaluable tool for AWS resource provisioning"

What do you like best?

Ability to define infrastructure as code, apply versioning and other SDLC-like methods, ability to automate resource provisioning, creating a repeatable process, applicable across environments and locations.

What do you dislike?

JSON is a difficult format to work with. It's great for transporting data, but not for programming logic or defining structures.

Recommendations to others considering the product

It is a great tool, but do consider alternatives and tools to supplement it, e.g. terraform or troposphere

What business problems are you solving with the product? What benefits have you realized?

Repeatable process for instantiating environments. Development agility - new dev environments ready in minutes.

AWS CloudFormation review by Administrator in Computer Software
Administrator in Computer Software
Validated Reviewer
Verified Current User
Review Source

"Fantastic experience for automated system deployments and upgrade on AWS"

What do you like best?

Ability to fully embrace IaC (infrastructure as code) with the very powerful "descriptive" approach (as opposed to the imperative approach you usually use with scripting) that enables seamless updates to running infrastructures.

What do you dislike?

The awful JSON based syntax which is hard to maintain and validate.

Recommendations to others considering the product

Have a look at troposphere (a project for generating CloudFormation templates using a validating Python syntax)

What business problems are you solving with the product? What benefits have you realized?

System deployments and updates on AWS with top-level traceability on what's running.

AWS CloudFormation review by Anton B.
Anton B.
Validated Reviewer
Review Source

"I would not recommend to use cloudformation for infra provisioning automation"

What do you like best?

You can write specs of your systems and store those specs in a VCS

What do you dislike?

- Procedural DSL implemented using JSON

- Cascading resource removal does not work well

Recommendations to others considering the product

Have a look at Teraform

What business problems are you solving with the product? What benefits have you realized?

When trying to automate infrastructure provisioning no significant benefits were found over plain shell scripts.

AWS CloudFormation review by User in Internet
User in Internet
Validated Reviewer
Verified Current User
Review Source

"Build faster, grow up quickly."

What do you like best?

Ways to build everything I want on AWS just using unique file.

What do you dislike?

Learning curve is complicated.

What business problems are you solving with the product? What benefits have you realized?

Any problem, because when we try AWS we already thinking about CloudFormation to avoid problems. The benefits are greats because we can setup a new stack in seconds.

AWS CloudFormation review by User in Entertainment
User in Entertainment
Validated Reviewer
Verified Current User
Review Source

"cloud formation review"

What do you like best?

Its easy to use with a low learning curve

What do you dislike?

It does not have the ability to configure all aws services

Recommendations to others considering the product

Verify it can configure the aws services that you are using or want to be using.

What business problems are you solving with the product? What benefits have you realized?

Automation, automation, automation.

Kate from G2 Crowd

Learning about AWS CloudFormation?

I can help.
* We monitor all AWS CloudFormation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.