Skip to main content
TrustRadius
AWS CloudFormation

AWS CloudFormation

Overview

What is AWS CloudFormation?

AWS CloudFormation gives developers and systems administrators a way to create and manage a collection of related AWS resources, provisioning and updating them in a predictable fashion. Use AWS CloudFormation’s sample templates or create templates to describe the AWS resources,…

Read more
Recent Reviews

Aws

5 out of 10
December 30, 2021
Incentivized
Our organization has a decision that to migrate from on-premises infrastructure to cloud this was one of the best decisions ever happened …
Continue reading
Read all reviews
Return to navigation

Pricing

View all pricing

Free Tier - 1,000 Handler Operations per Month per Account

$0.00

On Premise

Handler Operation

$0.0009

On Premise
per handler operation

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://aws.amazon.com/cloudformation/p…

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Demos

Demo AWS Lambda with boto3

YouTube
Return to navigation

Product Details

What is AWS CloudFormation?

AWS CloudFormation provides a common language for users to model and provision AWS and third party application resources in a cloud environment. AWS CloudFormation allows users to use programming languages or a simple text file to model and provision, in an automated and secure manner, all the resources needed for applications across all regions and accounts. This provides a single source of truth for AWS and third party resources.

AWS CloudFormation Features

  • Supported: Model infrastructure and application resources
  • Supported: Automate & deploy
  • Supported: Infrastructure as code
  • Supported: Extensibility
  • Supported: Authoring with JSON/YAML
  • Supported: Authoring with familiar programming languages
  • Supported: Safety controls
  • Supported: Preview changes to your environment
  • Supported: Dependency management
  • Supported: Cross account & cross-region management

AWS CloudFormation Screenshots

Screenshot of CloudFormation - How it works overviewScreenshot of CloudFormation - High level how it worksScreenshot of CloudFormation - Template exampleScreenshot of CloudFormation - Template inputs overview

AWS CloudFormation Videos

Introduction to AWS CloudFormation
Governance with AWS

AWS CloudFormation Competitors

  • HashiCorp Terraform
  • Oracle Cloud Infrastructure (OCI)
  • Puppet Enterprise (formerly Puppet Data Center Automation)

AWS CloudFormation Technical Details

Deployment TypesOn-premise
Operating SystemsWindows, Linux, Mac
Mobile ApplicationNo
Supported CountriesAmericas, Europe, Middle East, Africa, Asia Pacific

Frequently Asked Questions

AWS CloudFormation gives developers and systems administrators a way to create and manage a collection of related AWS resources, provisioning and updating them in a predictable fashion. Use AWS CloudFormation’s sample templates or create templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run an application. Users don’t need to figure out the order for provisioning AWS services or the subtleties of making those dependencies work. CloudFormation takes care of this. After the AWS resources are deployed, users can modify and update them in a controlled and predictable way, in effect applying version control to AWS infrastructure as with software.

HashiCorp Terraform are common alternatives for AWS CloudFormation.

The most common users of AWS CloudFormation are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(101)

Reviews

(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use AWS CloudFormation to deploy our infrastructure on AWS platform. We have different accounts for different customers with the services being deployed via CloudFormation templates. All we have to do is modify the respective values of stages, environment variables for deployments and you could use the same template for deployment to different customers which makes our life easy.
  • All resources can segregated based on stacks which provides greater visibility
  • A complete audit trail of what went wrong while deploying a particular resource
  • Automatically rollbacks if any service as part of CloudFormation results in an error
  • The UI tool is useful
  • Some services take a lot of time to create and it is frustrating after waiting for 20 mins some service fails, we have to retry whole process again.
  • Deleting some resources is bit tricky if they are dependent on other stacks which is again dependent on some s3 bucket not being deleted
  • Error description is not clear in some instances.
  • Documentation needs to be improved
AWS CloudFormation is well suited for scenarios where all of your resources need to be provisioned on AWS but it is not suited for hybrid cloud deployments. It's very easy for someone new to learn. The level of customization offered as part of the template specifically for AWS services is great. There is also a UI tool where we can drag and drop the services we want and it generates an yaml file which is very easy to use. The visibility of stacks and its resources and one place where we can track and identify the issues in deployment is great.
  • Reusability
  • Infrastructure Provisioning
  • AWS quick support for any issues related to CloudFormation deployments
  • Stack Visibility and segregation
  • Faster deployment
  • A one time setup which eliminates rework
  • Disaster Recovery
Since the product I'm involved is primarily hosted on AWS we use CloudFormation but in some other products where we have hybrid cloud deployments we prefer Terraform which is opensource.
December 30, 2021

Aws

Score 5 out of 10
Vetted Review
Verified User
Incentivized
Our organization has a decision that to migrate from on-premises infrastructure to cloud this was one of the best decisions ever happened to our company, it's changed the whole lifestyle in our company Cloning a virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource Management Guide. For information of us and we have to work on a new field for our team to get the information management Foundations for our team Work orders and to help us find out of all our requirements and to help me with your further details please let us if we need two keys to the house to let me try to get your keys in a few weeks before we received WO as I have to work on this and the other one I sent you with is a bit of an email with a B of my email to you to confirm me of your attendance to be there is a B hour course fee and the fee is paid by adding the extra extra extra amount to your invoice for mac bind so we received WO and a few of us have a good idea of what you are you doing for your Christmas and help
  • SaaS
  • Paas
  • Iaas
  • On promises
  • Jeddah
  • Riyadh
  • Neom
Cloning a virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the Cloning Cloning a virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource Management Guide. For information virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource. Management guide. For information virtual hardware, installed software cloning a virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource Management Guide. For information and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource Management Guide. For information.
  • ERP software
  • Email server exchange server
  • Dns
  • Speed
  • Save
  • Redundancy
Cloning a virtual machine creates a virtual machine that is cloning a virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Cloning a virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information. Management guide.For information copy of the original. The new virtual Cloning virtual machine creates a virtual machine that is a copy of the original. The new virtual machine is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource Management Guide. For information is configured with the same virtual hardware, installed software, and other properties that were configured for the original virtual machine. For information about persistent memory and PMem storage, see the vSphere Resource Management Guide. For information
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We are using AWS CloudFormation to provision infrastructure on AWS in different AWS accounts for different environments. It is being used by the whole company. We have a product that requires infrastructure on the cloud to make it run. It helps us in continuous delivery and fast infrastructure deployment. As we have more than 20 environments, AWS CloudFormation helps us in using the same templates with different values for each environment, resulting in reusability and saving time and effort.
  • Infrastructure Provisioning
  • Stack Visibility
  • Auto Rollback
  • Console for History and Tracking
  • Better Integration with AWS Services
  • Error Description upon Failure Needs to be Improved.
  • Slow to create, delete or update.
  • Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.
AWS CloudFormation is well suited when you have your whole infrastructure on AWS. It can be used to divide your whole infrastructure into multiple templates so you can redeploy variable infrastructure separately. It is good for infrastructure stack visibility and tracking. It is not good when you have resources on multiple clouds. Cloud-agnostic tools like Terraform can be used for such purposes.
  • Infrastructure Provisioning
  • Templating
  • Visibility
  • Reusability
  • IaC
  • Fast Delivery
  • Fast Environment Spin Up
  • IaC for Reusability and Disaster Recovery
As we have our whole infrastructure on AWS, that is why we selected AWS CloudFormation. AWS CloudFormation is better integrated with AWS services than other available products and also provides visibility and tracking on AWS. AWS CloudFormation is free while Terraform Enterprise is paid for teams. Terraform is good when we need to stay cloud-agnostic meaning multi-cloud infrastructure capability.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use it to expedite or deployment for VPCs. It creates almost all of the resources we need to for the most basic standup with a few parameters that get filled in. We can also use it to deploy smaller resources as well that don't require a full VPC standup. We're also looking into it for other use cases, but for the most part, it has greatly decreased the time to stand up a new VPC.
  • Logging errors
  • Template builder (for the more visually inclined).
  • General documentation
  • Better examples
  • There are oddities with the yaml aspects of it, that make it a bit cumbersome
  • A template for use cases that are easily fillable - or just some place to start.
I think repeatable tasks that require a lot of "clicking" are where it's best suited. Also, for VPC and smaller deployments, I think it's a great tool, but it does have some limitations. Not all resources are available, so sometimes you can only create the base part of your deployment, and manually have to input some values later on. From my understanding, Cloudformation is best while contained within individual regions of AWS.
  • Resource deployment
  • Logging
  • Rollback when needed.
  • + We can standup a VPC in minutes
  • - It took a lot of inital time to set up
  • + With logging/rollback, made testing much easier.
We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if it's a bit more complex, Terraform might be the way to go.
August 09, 2021

Robust Tool

Manuela Jacqueline Mercado Rodríguez | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
It has been used across the whole organization for doing stacks. It has helped us for doing specific environments for testing changes per branch (using GIT). In this way, fewer bugs are introduced to Production. It also allows preserving resources as it is very configurable. We can form stacks with just a basic configuration or with all of them.
  • Configuring Stacks
  • Deploying Stacks
  • Managing Stacks
  • Sometimes stacks are hard to delete due to the correlation of resources or configurations
  • It could be tricky at first time when doing configurations
It is really suited for professional environments. You can divide them into different stages, or with just specific changes. Those can be determined by the branch from the version control system (GIT, for example). If you are exploring and don't have too many resources this is not a very good option.
  • Creating Stacks
  • Managing Stacks
  • Doing specific configurations
  • It has a positive ROI
  • Less time inverted in bugs
  • More stable source code
AWS CloudFormation has more features and robustness. It is suited for professional projects since it provides stability and a wide variety of options for configurations. These include not only dividing stacks by specific code changes, but also in regions. This allows more granularity and control over all stacks. If you want to delete them all just by a region, you can do it.
Return to navigation