# AWS CloudFormation

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-cloudformation

> AWS CloudFormation is a service that enables users to model, provision, and manage AWS and third-party application resources in a safe, repeatable, and efficient manner using templates.

Practice exams covering AWS CloudFormation: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [MLA-C02 AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 8 key features of AWS CloudFormation

AWS CloudFormation provides an automated, efficient, and controlled manner for provisioning and managing AWS infrastructure through Infrastructure as Code, enabling the use of JSON or YAML templates for infrastructure modeling, integrated deployment capabilities, and custom resource support.

1. **Infrastructure as Code**: AWS CloudFormation allows users to model their entire infrastructure and application resources with either JSON or YAML templates. This approach enables version control of infrastructure in the same way as application source code, streamlining the deployment and management of AWS resources.
2. **Automated Deployment**: CloudFormation automates the provisioning and updating of your infrastructure in a safe, controlled manner, with rollback capabilities. This removes the need for manual operations or custom scripts, making the infrastructure management process both efficient and repeatable.
3. **Declarative Programming**: With AWS CloudFormation, you declare all your resources and dependencies in a template file, which the service then takes as an input to create and configure all the declared resources automatically, eliminating the need for manual provisioning.
4. **Custom Resources**: AWS CloudFormation offers the flexibility to create custom resources when existing resources or resource properties cannot fulfill specific requirements. This is achieved by integrating AWS Lambda with CloudFormation, providing a powerful way to extend CloudFormationâs capabilities.
5. **Safe and Controlled Updates**: CloudFormation provides features like change sets, which show the effects of proposed changes to your infrastructure before implementation. This allows teams to review changes in a controlled environment, minimizing the potential impact on running services or applications.
6. **Integrated with AWS Services**: CloudFormation is deeply integrated with AWS services, including Amazon EC2, Amazon S3, Amazon RDS, and others, allowing for comprehensive management of a wide range of AWS resources through a single tool.
7. **Resource Dependency Management**: CloudFormation automatically handles the sequencing of resource provisioning and takes care of dependencies between resources, ensuring that your infrastructure is deployed in an orderly and predictable manner.
8. **StackSets**: CloudFormation StackSets deploy resources across multiple AWS accounts and AWS Regions.

## Where AWS CloudFormation is used

AWS CloudFormation enables infrastructure as code, automated deployments, environment cloning for consistency, custom resource templating for tailored setups, and integrates with AWS configuration management for simplified maintenance and compliance.

1. **Infrastructure as Code**: AWS CloudFormation allows users to model and provision all their cloud infrastructure resources by using code. This makes it easier to create and manage a collection of related AWS resources, updating and replicating them in an orderly and predictable fashion.
2. **Automated Deployment**: By using AWS CloudFormation, teams can automate the deployment of AWS resources, ensuring that the infrastructure deployment is repeatable, scalable, and consistent. This reduces manual errors and increases efficiency in deploying applications across various environments.
3. **Environment Cloning and Consistency**: AWS CloudFormation enables organizations to clone whole cloud environments in a few steps, ensuring consistency across multiple environments. This capability supports disaster recovery strategies, efficient testing of new features, and rapid scaling of operations.
4. **Custom Resources and Templating**: The service provides a flexible templating language for defining custom AWS and third-party resources, allowing for the creation of specialized environment configurations as needed. This flexibility in defining custom resources makes CloudFormation a powerful tool for building complex, scalable, and tailored infrastructure setups.
5. **Integrated Configuration Management**: CloudFormation seamlessly integrates with other AWS services for configuration management, such as AWS Config and AWS Systems Manager. This integration allows for the centralized management of resource configurations and compliance, simplifying the maintenance of secure and efficient cloud environments.

## How AWS CloudFormation is priced

AWS CloudFormation's pricing models include a free tier for template deployments within service limits and a pay-as-you-go model for AWS resources provisioned using CloudFormation, with no extra charges for the CloudFormation service.

- **AWS CloudFormation Free Tier**: The free tier includes 1,000 handler operations per month per account, shared between Hook and third-party resource provider operations.
- **Pay-as-you-go Pricing**: There is no additional CloudFormation charge for resource providers in the AWS::* and Alexa::* namespaces. Resources provisioned through these providers are billed just as if they had been created manually, with no minimum fees or required upfront commitments.
- **Registry Extension Handler Operations**: Third-party resource providers outside AWS::* and Alexa::*, and custom Hooks outside AWS::*, incur charges of $0.0009 per billable handler operation. Handler execution beyond the first 30 seconds per operation costs $0.00008 per additional second. Managed Hooks in the AWS::* namespace have no additional CloudFormation Hooks charge.
- **Data Transfer**: Data transfer is billed at standard AWS data transfer rates.

## Services AWS CloudFormation works with

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Provides resizable compute capacity in the cloud. CloudFormation can launch and manage instances, volumes, and networking configurations.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Object storage built to store and retrieve any amount of data. CloudFormation uses S3 buckets to store templates and can manage bucket policies, configurations, and events.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Managed relational database service. CloudFormation can create, modify, and delete database instances, clusters, and subnet groups.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Virtual Private Cloud to provision logically isolated sections of AWS. CloudFormation can manage VPCs, subnets, route tables, gateways, and security groups.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Monitoring and observability service. CloudFormation can create alarms, log groups, and log streams, and configure metric-based actions.
- **[Amazon API Gateway](https://blowstack.com/tools/cloud-services-hub/amazon-api-gateway)**: CloudFormation provisions API Gateway REST, HTTP, and WebSocket APIs, including routes, integrations, authorizers, deployments, and stages. Templates can connect an API to its Lambda functions and configure the required permissions.
- **[Amazon AppFlow](https://blowstack.com/tools/cloud-services-hub/amazon-appflow)**: CloudFormation creates AppFlow flows and connector profiles, defining data sources, destinations, field mappings, and flow triggers in templates.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: CloudFormation provisions Athena workgroups, data catalogs, named queries, and prepared statements. Workgroup settings can enforce query-result locations and query usage controls.
- **[Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora)**: CloudFormation provisions Aurora DB clusters, database instances, parameter groups, and subnet groups, managing their dependencies within a stack.
- **[Amazon Aurora Serverless](https://blowstack.com/tools/cloud-services-hub/amazon-aurora-serverless)**: CloudFormation configures Aurora Serverless databases through RDS cluster and instance resources. Templates can specify Serverless v2 capacity ranges and serverless database instance classes.
- **[Amazon Bedrock](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock)**: CloudFormation provisions supported Bedrock resources, including agents, knowledge bases, guardrails, and flows. Templates can define these resources together with their storage and access permissions.
- **[Amazon Bedrock AgentCore](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock-agentcore)**: CloudFormation provisions supported Bedrock AgentCore resources, including agent runtimes, gateways, and memory resources, so agent infrastructure can be deployed through stacks.
- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: CloudFormation creates CloudFront distributions and associated resources such as cache policies, origin request policies, functions, and origin access controls.
- **[Amazon CodeGuru](https://blowstack.com/tools/cloud-services-hub/amazon-codeguru)**: CloudFormation creates CodeGuru Reviewer repository associations and CodeGuru Profiler profiling groups, allowing code analysis and profiling resources to be managed in stacks.
- **[Amazon Cognito](https://blowstack.com/tools/cloud-services-hub/amazon-cognito)**: CloudFormation provisions Cognito user pools, identity pools, application clients, identity providers, and related authentication settings.
- **[Amazon Comprehend](https://blowstack.com/tools/cloud-services-hub/amazon-comprehend)**: CloudFormation provisions Comprehend flywheels, including their task configuration, data lake location, and data access role, to manage custom-model training workflows as infrastructure.
- **[Amazon Connect](https://blowstack.com/tools/cloud-services-hub/amazon-connect)**: CloudFormation provisions supported Connect resources, including instances, contact flows, queues, routing profiles, and users. Templates can establish repeatable contact-center configurations.
- **[Amazon Data Firehose](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-firehose)**: CloudFormation creates Firehose delivery streams and configures their sources, destinations, buffering, transformation, encryption, and delivery logging.
- **[Amazon DataZone](https://blowstack.com/tools/cloud-services-hub/amazon-datazone)**: CloudFormation provisions DataZone domains, projects, environments, data sources, and related configuration to reproduce data-governance infrastructure across deployments.
- **[Amazon Detective](https://blowstack.com/tools/cloud-services-hub/amazon-detective)**: CloudFormation creates Detective behavior graphs and configures supported membership and organization settings.
- **[Amazon DevOps Guru](https://blowstack.com/tools/cloud-services-hub/amazon-devops-guru)**: CloudFormation provisions DevOps Guru resource collections and notification channels. DevOps Guru can also use CloudFormation stacks to select and group the application resources it analyzes for operational anomalies.
- **[Amazon DocumentDB (with MongoDB compatibility)](https://blowstack.com/tools/cloud-services-hub/amazon-documentdb-(with-mongodb-compatibility))**: CloudFormation provisions DocumentDB clusters, instances, parameter groups, subnet groups, and supported elastic-cluster resources.
- **[Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb)**: CloudFormation creates DynamoDB tables and global tables, including indexes, capacity settings, streams, encryption, and point-in-time recovery configuration.
- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: CloudFormation provisions Auto Scaling groups, scaling policies, lifecycle hooks, and scheduled actions. Creation and update policies can coordinate instance initialization and rolling replacements.
- **[Amazon ECS Anywhere](https://blowstack.com/tools/cloud-services-hub/amazon-ecs-anywhere)**: CloudFormation defines ECS task definitions with EXTERNAL launch compatibility and services that run on ECS Anywhere external instances. The external machines must be registered with the cluster separately.
- **[Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs))**: CloudFormation creates EBS volumes and volume attachments, specifying properties such as capacity, volume type, encryption, and snapshot source.
- **[Amazon Elastic Container Registry (Amazon ECR)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr))**: CloudFormation provisions ECR repositories and configures repository policies, lifecycle policies, encryption, and registry settings.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: CloudFormation provisions ECS clusters, task definitions, services, and capacity providers. Stack updates can deploy revised task definitions and service configurations.
- **[Amazon Elastic File System (Amazon EFS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-file-system-(amazon-efs))**: CloudFormation creates EFS file systems, mount targets, and access points, including encryption, lifecycle, backup, and file-system policy settings.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: CloudFormation provisions EKS clusters, managed node groups, Fargate profiles, add-ons, and access entries.
- **[Amazon ElastiCache](https://blowstack.com/tools/cloud-services-hub/amazon-elasticache)**: CloudFormation provisions ElastiCache caches and replication groups together with parameter groups, subnet groups, users, and user groups.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: CloudFormation provisions EMR clusters and supported EMR Serverless and EMR on EKS resources. Templates can define cluster applications, compute capacity, networking, and job-related configuration.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: CloudFormation creates EventBridge buses, rules, pipes, schedules, and other supported event-routing resources. EventBridge also receives CloudFormation stack and resource status events, which rules can route to automation or notification targets.
- **[Amazon Forecast](https://blowstack.com/tools/cloud-services-hub/amazon-forecast)**: CloudFormation provisions Forecast datasets and dataset groups, including schemas and domain settings used to organize forecasting data.
- **[Amazon Fraud Detector](https://blowstack.com/tools/cloud-services-hub/amazon-fraud-detector)**: CloudFormation provisions Fraud Detector resources such as detectors, event types, entity types, variables, labels, and outcomes.
- **[Amazon FSx](https://blowstack.com/tools/cloud-services-hub/amazon-fsx-(for-all-types))**: CloudFormation provisions FSx file systems and supported storage virtual machines, volumes, and snapshots. Templates can define networking, capacity, backups, and file-system-specific settings.
- **[Amazon GameLift](https://blowstack.com/tools/cloud-services-hub/amazon-gamelift)**: CloudFormation provisions GameLift resources such as fleets, builds, aliases, game session queues, and matchmaking configurations.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: CloudFormation configures GuardDuty detectors, filters, IP sets, threat intelligence sets, and other supported protection settings.
- **[Amazon HealthLake](https://blowstack.com/tools/cloud-services-hub/amazon-healthlake)**: CloudFormation provisions HealthLake FHIR data stores, including encryption and supported preload configuration.
- **[Amazon Inspector](https://blowstack.com/tools/cloud-services-hub/amazon-inspector)**: CloudFormation manages supported Inspector resources, including Inspector Classic assessment resources and Inspector filters or CIS scan configurations.
- **[Amazon Kendra](https://blowstack.com/tools/cloud-services-hub/amazon-kendra)**: CloudFormation provisions Kendra indexes, data sources, FAQs, and other supported search resources, including their access roles and synchronization settings.
- **[Amazon Keyspaces (for Apache Cassandra)](https://blowstack.com/tools/cloud-services-hub/amazon-keyspaces-(for-apache-cassandra))**: CloudFormation creates Keyspaces keyspaces and tables, configuring columns, keys, throughput, encryption, and recovery settings.
- **[Amazon Kinesis Data Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-streams)**: CloudFormation provisions Kinesis data streams and registered consumers, including capacity mode, retention, encryption, and enhanced fan-out resources.
- **[Amazon Kinesis Video Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-video-streams)**: CloudFormation creates Kinesis Video Streams streams and signaling channels, including retention, encryption, and signaling configuration.
- **[Amazon Lex](https://blowstack.com/tools/cloud-services-hub/amazon-lex)**: CloudFormation provisions Lex bots, bot versions, and aliases. Templates can define conversational intents, slots, locales, and supported runtime settings.
- **[Amazon Lightsail](https://blowstack.com/tools/cloud-services-hub/amazon-lightsail)**: CloudFormation provisions supported Lightsail resources, including instances, databases, disks, static IP addresses, load balancers, and container services.
- **[Amazon Location Service](https://blowstack.com/tools/cloud-services-hub/amazon-location-service)**: CloudFormation provisions Location Service maps, place indexes, route calculators, trackers, geofence collections, and API keys.
- **[Amazon Macie](https://blowstack.com/tools/cloud-services-hub/amazon-macie)**: CloudFormation configures Macie sessions, custom data identifiers, findings filters, allow lists, and supported classification settings.
- **[Amazon Managed Blockchain](https://blowstack.com/tools/cloud-services-hub/amazon-managed-blockchain)**: CloudFormation provisions supported Managed Blockchain networks, members, nodes, and accessors, managing their configuration and dependencies through stacks.
- **[Amazon Managed Grafana](https://blowstack.com/tools/cloud-services-hub/amazon-managed-grafana)**: CloudFormation provisions Managed Grafana workspaces and configures authentication, permissions, network access, and supported data sources.
- **[Amazon Managed Service for Apache Flink](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-apache-flink)**: CloudFormation provisions Managed Service for Apache Flink applications and configures application code locations, runtime settings, networking, logging, and snapshots.
- **[Amazon Managed Service for Prometheus](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-prometheus)**: CloudFormation provisions Prometheus workspaces, rule groups, alert manager definitions, and supported scrapers.
- **[Amazon Managed Streaming for Apache Kafka](https://blowstack.com/tools/cloud-services-hub/amazon-managed-streaming-for-apache-kafka)**: CloudFormation provisions MSK clusters and supported configurations, replicators, and MSK Connect resources.
- **[Amazon Managed Workflows for Apache Airflow (Amazon MWAA)](https://blowstack.com/tools/cloud-services-hub/amazon-managed-workflows-for-apache-airflow-(amazon-mwaa))**: CloudFormation provisions MWAA environments, configuring the DAG storage location, execution role, networking, logging, and environment capacity.
- **[Amazon MemoryDB for Redis](https://blowstack.com/tools/cloud-services-hub/amazon-memorydb-for-redis)**: CloudFormation provisions MemoryDB clusters, parameter groups, subnet groups, users, and access control lists.
- **[Amazon MQ](https://blowstack.com/tools/cloud-services-hub/amazon-mq)**: CloudFormation provisions Amazon MQ brokers and broker configurations, including engine selection, deployment mode, networking, logging, and users.
- **[Amazon Neptune](https://blowstack.com/tools/cloud-services-hub/amazon-neptune)**: CloudFormation provisions Neptune clusters, instances, parameter groups, and subnet groups, as well as supported Neptune Analytics graphs.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: CloudFormation provisions OpenSearch domains and supported OpenSearch Serverless collections, security policies, and access policies.
- **[Amazon Personalize](https://blowstack.com/tools/cloud-services-hub/amazon-personalize)**: CloudFormation provisions Personalize schemas, datasets, dataset groups, and solutions, defining the infrastructure used for recommendation training.
- **[Amazon Q](https://blowstack.com/tools/cloud-services-hub/amazon-q)**: CloudFormation manages supported Amazon Q Business infrastructure through resource types for applications, indexes, retrievers, data sources, and web experiences.
- **[Amazon Q Business](https://blowstack.com/tools/cloud-services-hub/amazon-q-business)**: CloudFormation provisions Q Business applications, indexes, retrievers, data sources, plugins, and web experiences. Templates can reproduce an enterprise assistant's supported infrastructure and access configuration.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: CloudFormation provisions QuickSight data sources, datasets, analyses, dashboards, templates, and themes, allowing analytics assets to be deployed between environments.
- **[Amazon RDS Proxy](https://blowstack.com/tools/cloud-services-hub/amazon-rds-proxy)**: CloudFormation provisions RDS proxies, target groups, and proxy endpoints, including authentication, network, and connection-pooling settings.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: CloudFormation provisions Redshift clusters and supported Redshift Serverless namespaces and workgroups, along with networking and parameter configuration.
- **[Amazon Rekognition](https://blowstack.com/tools/cloud-services-hub/amazon-rekognition)**: CloudFormation provisions Rekognition collections, projects, and stream processors, including supported video-processing and notification settings.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: CloudFormation creates Route 53 hosted zones, DNS records, health checks, and supported Route 53 Resolver resources.
- **[Amazon S3 Glacier](https://blowstack.com/tools/cloud-services-hub/amazon-s3-glacier)**: CloudFormation configures S3 bucket lifecycle rules that transition objects into S3 Glacier storage classes. Templates can define archival schedules and expiration rules alongside the bucket.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: CloudFormation provisions supported SageMaker resources, including Studio domains, notebook instances, models, endpoints, pipelines, and feature groups.
- **[Amazon SageMaker Ground Truth](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-ground-truth)**: CloudFormation provisions SageMaker workteams used by Ground Truth, including workforce membership and notification configuration.
- **[Amazon Security Lake](https://blowstack.com/tools/cloud-services-hub/amazon-security-lake)**: CloudFormation provisions Security Lake data lakes, log sources, subscribers, and subscriber notifications, including retention and encryption settings.
- **[Amazon Simple Email Service (Amazon SES)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-email-service-(amazon-ses))**: CloudFormation provisions SES identities, configuration sets, email templates, receipt rules, and other supported email resources.
- **[Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns))**: CloudFormation provisions SNS topics, subscriptions, and topic policies. It can also publish stack event notifications to an SNS topic configured for the stack.
- **[Amazon Simple Queue Service (Amazon SQS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-queue-service-(amazon-sqs))**: CloudFormation provisions SQS queues and queue policies, including FIFO settings, encryption, dead-letter queues, and redrive configuration.
- **[Amazon Timestream](https://blowstack.com/tools/cloud-services-hub/amazon-timestream)**: CloudFormation provisions Timestream databases, tables, and scheduled queries, including retention, storage, encryption, and query execution settings.
- **[Amazon Timestream for InfluxDB](https://blowstack.com/tools/cloud-services-hub/amazon-timestream-for-influxdb)**: CloudFormation provisions Timestream for InfluxDB database instances, configuring compute capacity, storage, networking, and database settings.
- **[Amazon Verified Permissions](https://blowstack.com/tools/cloud-services-hub/amazon-verified-permissions)**: CloudFormation provisions Verified Permissions policy stores and identity sources. A policy store template can include its schema and validation settings.
- **[Amazon WorkSpaces](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces)**: CloudFormation provisions supported WorkSpaces resources, including desktops and connection aliases, with bundle, directory, user, and workspace settings.
- **[Amazon WorkSpaces Applications](https://blowstack.com/tools/cloud-services-hub/amazon-appstream-2)**: CloudFormation provisions WorkSpaces Applications resources through the AWS::AppStream resource types, including fleets, stacks, image builders, and user associations.
- **[Amazon WorkSpaces Secure Browser](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces-web)**: CloudFormation provisions WorkSpaces Secure Browser portals and associated browser, network, identity provider, user, and logging settings through AWS::WorkSpacesWeb resource types.
- **[AWS Amplify](https://blowstack.com/tools/cloud-services-hub/aws-amplify)**: CloudFormation provisions Amplify applications, branches, domains, and supported backend environments. Amplify's CloudFormation-based backend workflows also use stacks to deploy backend resources.
- **[AWS App Runner](https://blowstack.com/tools/cloud-services-hub/aws-app-runner)**: CloudFormation provisions App Runner services, automatic scaling configurations, VPC connectors, and VPC ingress connections.
- **[AWS App2Container](https://blowstack.com/tools/cloud-services-hub/aws-app2container)**: App2Container generates CloudFormation templates for deploying containerized applications and their supporting infrastructure. CloudFormation creates the resources described by those deployment artifacts.
- **[AWS AppConfig](https://blowstack.com/tools/cloud-services-hub/aws-appconfig)**: CloudFormation provisions AppConfig applications, environments, configuration profiles, hosted configuration versions, deployment strategies, and deployments.
- **[AWS AppSync](https://blowstack.com/tools/cloud-services-hub/aws-appsync)**: CloudFormation provisions AppSync APIs, schemas, data sources, resolvers, functions, and authentication settings.
- **[AWS Audit Manager](https://blowstack.com/tools/cloud-services-hub/aws-audit-manager)**: CloudFormation provisions Audit Manager assessments, defining the assessment framework, scope, roles, and evidence report destination.
- **[AWS Auto Scaling](https://blowstack.com/tools/cloud-services-hub/aws-auto-scaling)**: CloudFormation provisions Application Auto Scaling scalable targets and scaling policies, as well as AWS Auto Scaling scaling plans.
- **[AWS Backup](https://blowstack.com/tools/cloud-services-hub/aws-backup)**: CloudFormation provisions Backup vaults, backup plans, resource selections, and other supported backup resources, including retention and copy settings.
- **[AWS Batch](https://blowstack.com/tools/cloud-services-hub/aws-batch)**: CloudFormation provisions Batch compute environments, job queues, job definitions, and scheduling policies.
- **[AWS Billing and Cost Management](https://blowstack.com/tools/cloud-services-hub/aws-billing-and-cost-management)**: CloudFormation provisions supported billing and cost-management resources, including cost categories and cost anomaly monitors, so financial governance settings can be managed as code.
- **[AWS Billing Conductor](https://blowstack.com/tools/cloud-services-hub/aws-billing-conductor)**: CloudFormation provisions Billing Conductor billing groups, pricing plans, pricing rules, and custom line items.
- **[AWS Budgets](https://blowstack.com/tools/cloud-services-hub/aws-budgets)**: CloudFormation creates budgets and budget actions, including spending thresholds, notifications, subscribers, and supported automated responses.
- **[AWS Certificate Manager (ACM)](https://blowstack.com/tools/cloud-services-hub/aws-certificate-manager-(acm))**: CloudFormation requests and manages ACM certificates, including domain names, validation settings, and supported certificate options. DNS validation can be automated for eligible Route 53 hosted zones.
- **[AWS Chatbot](https://blowstack.com/tools/cloud-services-hub/aws-chatbot)**: CloudFormation provisions supported Chatbot channel configurations, including notification topics, IAM roles, and guardrail policies.
- **[AWS Clean Rooms](https://blowstack.com/tools/cloud-services-hub/aws-clean-rooms)**: CloudFormation provisions Clean Rooms collaborations, memberships, configured tables, associations, and supported analysis resources.
- **[AWS Client VPN](https://blowstack.com/tools/cloud-services-hub/aws-client-vpn)**: CloudFormation provisions Client VPN endpoints, target-network associations, authorization rules, and routes through EC2 resource types.
- **[AWS Cloud Map](https://blowstack.com/tools/cloud-services-hub/aws-cloud-map)**: CloudFormation provisions Cloud Map namespaces, services, and registered instances, including DNS and health-check settings.
- **[AWS Cloud9](https://blowstack.com/tools/cloud-services-hub/aws-cloud9)**: CloudFormation provisions Cloud9 EC2 development environments, configuring their instance type, subnet, ownership, and automatic shutdown settings.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records CloudFormation API activity for auditing stack and configuration changes. CloudFormation also provisions CloudTrail trails, event data stores, and other supported logging resources.
- **[AWS CodeArtifact](https://blowstack.com/tools/cloud-services-hub/aws-codeartifact)**: CloudFormation provisions CodeArtifact domains and repositories, including permissions policies, upstream repositories, and external connections.
- **[AWS CodeBuild](https://blowstack.com/tools/cloud-services-hub/aws-codebuild)**: CloudFormation provisions CodeBuild projects, report groups, and fleets, including source, build environment, artifacts, and logging configuration.
- **[AWS CodeCommit](https://blowstack.com/tools/cloud-services-hub/aws-codecommit)**: CloudFormation provisions CodeCommit repositories and configures supported repository initialization and triggers.
- **[AWS CodeConnections](https://blowstack.com/tools/cloud-services-hub/aws-codeconnections)**: CloudFormation Git sync uses CodeConnections to access supported Git repositories and update stacks when template or deployment files change. CloudFormation also provisions supported connection resources.
- **[AWS CodePipeline](https://blowstack.com/tools/cloud-services-hub/aws-codepipeline)**: CodePipeline has CloudFormation deployment actions that create or update stacks and create or execute change sets. CloudFormation also provisions pipelines, including their stages, actions, artifacts, and permissions.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: CloudFormation provisions Config recorders, delivery channels, rules, conformance packs, and aggregators. Config can record CloudFormation stack configuration and use a managed rule to check stack drift.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: CloudFormation provisions supported Control Tower landing zones, enabled controls, and enabled baselines. Control Tower also uses CloudFormation StackSets to deploy and maintain account-governance resources.
- **[AWS Cost and Usage Report](https://blowstack.com/tools/cloud-services-hub/aws-cost-and-usage-report)**: CloudFormation provisions Cost and Usage Report definitions, specifying report contents, delivery frequency, format, and destination bucket.
- **[AWS Cost Explorer](https://blowstack.com/tools/cloud-services-hub/aws-cost-explorer)**: CloudFormation provisions Cost Explorer cost categories, anomaly monitors, and anomaly subscriptions, allowing cost allocation and anomaly alerting configuration to be version controlled.
- **[AWS Data Exchange](https://blowstack.com/tools/cloud-services-hub/aws-data-exchange)**: CloudFormation provisions supported Data Exchange datasets, revisions, and event actions, allowing data-product resources and automation to be managed in stacks.
- **[AWS Data Pipeline](https://blowstack.com/tools/cloud-services-hub/aws-data-pipeline)**: CloudFormation provisions Data Pipeline pipelines, including pipeline objects, parameters, and activation settings.
- **[AWS Database Migration Service (AWS DMS)](https://blowstack.com/tools/cloud-services-hub/aws-database-migration-service-(aws-dms))**: CloudFormation provisions DMS replication instances, endpoints, replication tasks, subnet groups, and supported serverless replication configurations.
- **[AWS DataSync](https://blowstack.com/tools/cloud-services-hub/aws-datasync)**: CloudFormation provisions DataSync agents, locations, and tasks, including transfer options, schedules, and logging settings.
- **[AWS Device Farm](https://blowstack.com/tools/cloud-services-hub/aws-device-farm)**: CloudFormation provisions supported Device Farm resources, including projects, device pools, network profiles, and test grid projects.
- **[AWS DevOps Agent](https://blowstack.com/tools/cloud-services-hub/aws-devops-agent)**: AWS DevOps Agent can use CloudFormation stack information to identify application resources and understand their relationships during operational investigations.
- **[AWS Directory Service](https://blowstack.com/tools/cloud-services-hub/aws-directory-service)**: CloudFormation provisions supported Directory Service directories, including AWS Managed Microsoft AD and Simple AD, with their networking and directory settings.
- **[AWS Elastic Beanstalk](https://blowstack.com/tools/cloud-services-hub/aws-elastic-beanstalk)**: CloudFormation provisions Elastic Beanstalk applications, application versions, environments, and configuration templates. Elastic Beanstalk also uses CloudFormation stacks to manage the AWS resources underlying its environments.
- **[AWS Entity Resolution](https://blowstack.com/tools/cloud-services-hub/aws-entity-resolution)**: CloudFormation provisions Entity Resolution schema mappings, matching workflows, and supported ID mapping resources.
- **[AWS Fargate](https://blowstack.com/tools/cloud-services-hub/aws-fargate)**: CloudFormation configures Fargate workloads through ECS task definitions and services, EKS Fargate profiles, and supported Batch compute environments.
- **[AWS Fault Injection Service](https://blowstack.com/tools/cloud-services-hub/aws-fault-injection-simulator-(aws-fis))**: CloudFormation provisions Fault Injection Service experiment templates, including experiment actions, targets, stop conditions, and logging configuration.
- **[AWS Firewall Manager](https://blowstack.com/tools/cloud-services-hub/aws-firewall-manager)**: CloudFormation provisions Firewall Manager policies and supported resource sets, defining centrally managed security policies and their scope.
- **[AWS Global Accelerator](https://blowstack.com/tools/cloud-services-hub/aws-global-accelerator)**: CloudFormation provisions Global Accelerator accelerators, listeners, and endpoint groups, including traffic routing and health-check settings.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: CloudFormation provisions Glue databases, tables, crawlers, jobs, workflows, triggers, connections, and other supported data-integration resources.
- **[AWS Glue DataBrew](https://blowstack.com/tools/cloud-services-hub/aws-glue-databrew)**: CloudFormation provisions DataBrew datasets, recipes, projects, jobs, schedules, and rulesets for repeatable data preparation.
- **[AWS IAM Identity Center (AWS Single Sign-On)](https://blowstack.com/tools/cloud-services-hub/aws-iam-identity-center-(aws-single-sign-on))**: CloudFormation provisions IAM Identity Center permission sets, account assignments, and supported application resources through AWS::SSO resource types.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: CloudFormation provisions IAM roles, policies, users, groups, instance profiles, and identity providers. CloudFormation can assume a dedicated service role to perform stack operations with controlled permissions.
- **[AWS IoT Core](https://blowstack.com/tools/cloud-services-hub/aws-iot-core)**: CloudFormation provisions IoT Core things, policies, certificates, topic rules, and other supported messaging and registry resources.
- **[AWS IoT Device Defender](https://blowstack.com/tools/cloud-services-hub/aws-iot-device-defender)**: CloudFormation provisions Device Defender security profiles, scheduled audits, account audit settings, and mitigation actions.
- **[AWS IoT Greengrass](https://blowstack.com/tools/cloud-services-hub/aws-iot-greengrass)**: CloudFormation provisions supported Greengrass resources, including Greengrass V2 component versions and deployments.
- **[AWS IoT SiteWise](https://blowstack.com/tools/cloud-services-hub/aws-iot-sitewise)**: CloudFormation provisions SiteWise asset models, assets, gateways, portals, projects, and dashboards.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: CloudFormation provisions KMS keys, aliases, and supported replica keys, including key policies and rotation settings. CloudFormation parameter types and dynamic references can also use values protected by KMS encryption through integrated services.
- **[AWS Lake Formation](https://blowstack.com/tools/cloud-services-hub/aws-lake-formation)**: CloudFormation provisions Lake Formation data lake settings, registered resources, permissions, LF-Tags, and supported tag-based access controls.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: CloudFormation provisions Lambda functions, versions, aliases, permissions, layers, and event source mappings. Lambda functions can also implement custom resources and CloudFormation registry resource providers.
- **[AWS Launch Wizard](https://blowstack.com/tools/cloud-services-hub/aws-launch-wizard)**: Launch Wizard uses CloudFormation to deploy and manage the infrastructure for supported application deployments, organizing provisioned resources into stacks.
- **[AWS License Manager](https://blowstack.com/tools/cloud-services-hub/aws-license-manager)**: CloudFormation provisions supported License Manager licenses and grants, including license entitlements and grant recipients.
- **[AWS Managed Services (AMS)](https://blowstack.com/tools/cloud-services-hub/aws-managed-services-(ams))**: AMS uses CloudFormation-based stack deployments to provision and manage supported infrastructure through its managed change workflows.
- **[AWS Marketplace](https://blowstack.com/tools/cloud-services-hub/aws-marketplace)**: CloudFormation deploys AWS Marketplace products that provide CloudFormation fulfillment templates. These templates can launch a vendor solution and its supporting AWS resources as a stack.
- **[AWS Migration Hub](https://blowstack.com/tools/cloud-services-hub/aws-migration-hub)**: CloudFormation provisions Migration Hub Refactor Spaces environments, applications, and routes, allowing application modernization routing infrastructure to be managed as code.
- **[AWS Network Firewall](https://blowstack.com/tools/cloud-services-hub/aws-network-firewall)**: CloudFormation provisions Network Firewall firewalls, firewall policies, rule groups, and logging configurations.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: CloudFormation StackSets integrates with Organizations to deploy stacks across accounts and organizational units using service-managed permissions. CloudFormation also provisions supported Organizations resources, including organizational units and policies.
- **[AWS Outposts](https://blowstack.com/tools/cloud-services-hub/aws-outposts)**: CloudFormation provisions supported Outposts-hosted resources, including EC2 resources placed on an Outpost and S3 on Outposts buckets, access points, and endpoints.
- **[AWS Private Certificate Authority](https://blowstack.com/tools/cloud-services-hub/aws-private-certificate-authority)**: CloudFormation provisions private certificate authorities, CA activation resources, certificates, and permissions, including supported revocation configuration.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: CloudFormation provisions PrivateLink endpoint services, service permissions, and VPC endpoints. PrivateLink also provides interface endpoints for private access to the CloudFormation API.
- **[AWS Resilience Hub](https://blowstack.com/tools/cloud-services-hub/aws-resilience-hub)**: CloudFormation provisions Resilience Hub applications and resiliency policies. Resilience Hub can also import resources from CloudFormation stacks to define the application it assesses.
- **[AWS Resource Access Manager (AWS RAM)](https://blowstack.com/tools/cloud-services-hub/aws-resource-access-manager-(aws-ram))**: CloudFormation provisions RAM resource shares, defining shared resources, principals, and supported sharing permissions.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: CloudFormation provisions resource groups and can define a group whose membership follows a CloudFormation stack, helping organize the stack's resources for management.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: CloudFormation provisions secrets, resource policies, rotation schedules, and target attachments. Dynamic references let stack resources use secret values without placing those values directly in templates.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: CloudFormation provisions supported Security Hub resources, including hub configuration, automation rules, configuration policies, and policy associations.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: CloudFormation uses STS to assume service roles and obtain temporary credentials for provisioning resources. Self-managed StackSets also use role assumption to operate in target accounts.
- **[AWS Serverless Application Model (AWS SAM)](https://blowstack.com/tools/cloud-services-hub/aws-serverless-application-model-(aws-sam))**: CloudFormation supports the AWS::Serverless transform, which expands SAM template resources into CloudFormation resources. This allows functions, APIs, and other serverless application components to be deployed together as a stack.
- **[AWS Serverless Application Repository](https://blowstack.com/tools/cloud-services-hub/aws-serverless-application-repository)**: Serverless Application Repository applications are packaged with CloudFormation-compatible templates and deployed as stacks. CloudFormation can include repository applications through the AWS::Serverless::Application resource.
- **[AWS Service Catalog](https://blowstack.com/tools/cloud-services-hub/aws-service-catalog)**: Service Catalog uses CloudFormation templates to define products and CloudFormation stacks to provision them. CloudFormation also provisions Service Catalog portfolios, products, constraints, and associations.
- **[AWS Shield](https://blowstack.com/tools/cloud-services-hub/aws-shield)**: CloudFormation provisions Shield Advanced protections and protection groups, including supported application-layer automatic response settings.
- **[AWS Signer](https://blowstack.com/tools/cloud-services-hub/aws-signer)**: CloudFormation provisions Signer signing profiles and profile permissions. These profiles can be referenced by Lambda code-signing configurations deployed in the same stack.
- **[AWS Site-to-Site VPN](https://blowstack.com/tools/cloud-services-hub/aws-site-to-site-vpn)**: CloudFormation provisions customer gateways, VPN gateways, VPN connections, and VPN routes, including supported tunnel configuration.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: CloudFormation provisions Step Functions state machines and activities, including workflow definitions, execution roles, logging, and tracing settings.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: CloudFormation provisions Systems Manager parameters, documents, associations, maintenance windows, and other supported management resources. Templates can resolve Parameter Store values, and Systems Manager Automation provides actions for creating and deleting CloudFormation stacks.
- **[AWS Transfer Family](https://blowstack.com/tools/cloud-services-hub/aws-transfer-family)**: CloudFormation provisions Transfer Family servers, users, workflows, connectors, agreements, and profiles, including authentication and storage access settings.
- **[AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway)**: CloudFormation provisions transit gateways, attachments, route tables, routes, associations, and propagations through EC2 resource types.
- **[AWS User Notifications](https://blowstack.com/tools/cloud-services-hub/aws-user-notifications)**: CloudFormation provisions User Notifications notification hubs, notification configurations, event rules, and channel associations.
- **[AWS Verified Access](https://blowstack.com/tools/cloud-services-hub/aws-verified-access)**: CloudFormation provisions Verified Access instances, trust providers, groups, and endpoints, including access policies and logging settings.
- **[AWS WAF](https://blowstack.com/tools/cloud-services-hub/aws-waf)**: CloudFormation provisions WAF web ACLs, rule groups, IP sets, regex pattern sets, logging configurations, and supported resource associations.
- **[AWS Well-Architected Tool](https://blowstack.com/tools/cloud-services-hub/aws-well-architected-tool)**: CloudFormation provisions Well-Architected workloads, defining their environment, review owner, architectural scope, and associated lenses.
- **[AWS X-Ray](https://blowstack.com/tools/cloud-services-hub/aws-x-ray)**: CloudFormation provisions X-Ray groups, sampling rules, and resource policies, allowing tracing controls to be deployed alongside application infrastructure.
- **[EC2 Image Builder](https://blowstack.com/tools/cloud-services-hub/ec2-image-builder)**: CloudFormation provisions Image Builder components, recipes, infrastructure configurations, distribution configurations, images, and image pipelines.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: CloudFormation provisions load balancers, target groups, listeners, listener rules, and supported certificates and attributes. Stack references connect load balancers to their networks and application targets.

## What is AWS CloudFormation

Amazon Web Services (AWS) CloudFormation is a powerful tool designed to give developers and IT professionals an easy way to create and manage a collection of related AWS resources.

At its core, CloudFormation provides a user-friendly way to automate the deployment and management of infrastructure and applications within the cloud, saving time and reducing the potential for human error. By treating infrastructure as code, CloudFormation enables users to model their entire infrastructure in text files or templates, which can be version-controlled, reused, and shared among team members.

CloudFormation templates are written in either JSON or YAML format, making them both human-readable and machine-readable. These templates describe all the AWS resources needed for a project, including their properties and relationships to one another. For instance, a template might define a network stack that includes an Amazon VPC, subnets, a security group, and an EC2 instance. Once a template is created, CloudFormation automates the provisioning and updating of the specified resources in an orderly and predictable fashion. This automation extends to managing dependencies between resources, ensuring that they are created, updated, or deleted in the correct sequence.

CloudFormation and CDK also offer express mode, which completes stack operations when resource configuration is confirmed as applied rather than waiting for extended stabilization checks such as traffic readiness, region propagation, and resource cleanup.

One of the key benefits of using AWS CloudFormation is its ability to manage the entire lifecycle of resources. With CloudFormation, users can easily update their infrastructure in a controlled and predictable way. CloudFormation offers drift-aware change sets that compare an IaC template with the actual state of infrastructure and can bring drifted resources in line with their template definitions. This approach minimizes disruptions to running applications and services. CloudFormation also supports the concept of stacks, which are collections of AWS resources that are managed as a single unit. This means that all the resources defined in a stack are treated together, allowing users to easily replicate their infrastructure for different environments such as development, testing, and production.

If an error occurs during deployment of a change set, CloudFormation automatically rolls back to the last known working state.

Furthermore, CloudFormation provides detailed status reports, which help users track the progress of operations and troubleshoot any issues that arise during the deployment or management of their resources. Another significant advantage of using CloudFormation is its integration with other AWS services and third-party tools. This integration facilitates the automation of complex deployments that involve multiple interdependent services and applications.

CloudFormation registry extensions use CREATE, UPDATE, DELETE, READ, or LIST handler operations for resource types, and CREATE, UPDATE, or DELETE handler operations for Hook types.

In addition, CloudFormation is backed by the vast ecosystem of AWS, providing users with a comprehensive set of tools and services to manage their infrastructure efficiently. In summary, AWS CloudFormation is an indispensable tool for individuals and organizations looking to automate the deployment and management of their infrastructure on AWS. Its approach to infrastructure as code, combined with powerful templating, lifecycle management, and integration capabilities, makes CloudFormation an essential component of modern cloud computing practices. By leveraging CloudFormation, users can achieve greater efficiency, reliability, and scalability in their cloud-based applications and services.

## Concepts related to AWS CloudFormation

- [Infrastructure as code (IaC)](https://blowstack.com/tools/cloud-concepts-hub/infrastructure-as-code-(iac)): Infrastructure as code (IaC) is the practice of defining and managing infrastructure through machine-readable, version-controlled configuration or code rather than manual setup.
- [Configuration Drift](https://blowstack.com/tools/cloud-concepts-hub/configuration-drift): Configuration drift is the divergence of a resource’s actual configuration from its declared or approved desired state over time.
- [Policy as Code](https://blowstack.com/tools/cloud-concepts-hub/policy-as-code): Policy as Code expresses governance and security requirements as version-controlled, machine-evaluable rules that automated workflows can test and enforce.
- [Declarative Programming](https://blowstack.com/tools/cloud-concepts-hub/declarative-programming): Declarative programming describes the desired result or structure of a system while delegating the execution steps to a runtime, framework, or provisioning engine.
- [Parameterization](https://blowstack.com/tools/cloud-concepts-hub/parameterization): Parameterization separates environment-specific values from reusable infrastructure definitions by supplying those values through explicit inputs.
- [Deployment Rollback](https://blowstack.com/tools/cloud-concepts-hub/deployment-rollback): Deployment rollback restores a previously validated application, infrastructure, or model release when a new deployment fails or causes unacceptable behavior.
- [Pilot Light](https://blowstack.com/tools/cloud-concepts-hub/pilot-light): Pilot light is a disaster recovery strategy that keeps essential components and replicated data ready in a recovery environment while leaving most application capacity inactive until needed.
- [Static Analysis](https://blowstack.com/tools/cloud-concepts-hub/static-analysis): Static analysis examines code, configuration, or infrastructure definitions for defects and policy violations without executing the workload or deploying the resources being analyzed.
- [CI/CD](https://blowstack.com/tools/cloud-concepts-hub/cicd): CI/CD is a software engineering approach that continuously integrates code changes and automates their validation and delivery or deployment.
- [APIs](https://blowstack.com/tools/cloud-concepts-hub/apis): APIs are defined interfaces that let software request data or actions from another system without depending on its internal implementation.
- [Benefits of migrating to the AWS Cloud](https://blowstack.com/tools/cloud-concepts-hub/benefits-of-migrating-to-the-aws-cloud): Benefits of migrating to the AWS Cloud are the operational, financial, and business advantages of using on-demand cloud resources instead of owning and managing all underlying infrastructure.
- [Configuration Management](https://blowstack.com/tools/cloud-concepts-hub/configuration-management): Configuration management is the practice of defining, tracking, and controlling system settings and components so that environments remain consistent with an approved state.
- [Imperative Programming](https://blowstack.com/tools/cloud-concepts-hub/imperative-programming): Imperative programming expresses computation as explicit instructions that control execution and change program or system state.
- [Warm Standby](https://blowstack.com/tools/cloud-concepts-hub/warm-standby): Warm standby is a disaster recovery strategy that keeps a scaled-down, functional copy of a production environment running in a separate recovery location.
- [Acceptance Testing](https://blowstack.com/tools/cloud-concepts-hub/acceptance-testing): Acceptance testing verifies that a system satisfies agreed acceptance criteria and is suitable for its intended business use.
- [Agile Development](https://blowstack.com/tools/cloud-concepts-hub/agile-development): Agile development is an iterative, incremental approach to software delivery that adapts plans through frequent feedback, collaboration, and working software.
- [AWS Prescriptive Guidance](https://blowstack.com/tools/cloud-concepts-hub/aws-prescriptive-guidance): AWS Prescriptive Guidance is an official AWS library of strategies, guides, and implementation patterns for planning and carrying out cloud migrations, modernization, and other technical initiatives.
- [AWS SDKs](https://blowstack.com/tools/cloud-concepts-hub/aws-sdks): AWS SDKs are language-specific software development kits that let applications interact with AWS service APIs through familiar programming interfaces.
- [Environment Isolation](https://blowstack.com/tools/cloud-concepts-hub/environment-isolation): Environment isolation separates development, testing, staging, and production resources so that activity in one environment does not unintentionally affect another.
- [Growth Mindset](https://blowstack.com/tools/cloud-concepts-hub/growth-mindset): A growth mindset is the belief that abilities can develop through effective practice, feedback, learning, and support rather than remaining fixed.
- [Integration Testing](https://blowstack.com/tools/cloud-concepts-hub/integration-testing): Integration testing verifies that connected software components exchange data and work together correctly across their interfaces.
- [Performance Benchmarking](https://blowstack.com/tools/cloud-concepts-hub/performance-benchmarking): Performance benchmarking is the repeatable measurement of a system under defined workloads to compare its behavior against a baseline, alternative configuration, or performance target.
- [Rollback](https://blowstack.com/tools/cloud-concepts-hub/rollback): Rollback is the reversal of a change to return a system to a previously known-good operational state.
- [Test Pyramid](https://blowstack.com/tools/cloud-concepts-hub/test-pyramid): The Test Pyramid is a testing strategy that favors many fast, focused tests, fewer integration tests, and a small set of broad end-to-end tests.
- [Waterfall Model](https://blowstack.com/tools/cloud-concepts-hub/waterfall-model): The Waterfall Model is a software development lifecycle approach that organizes work into sequential phases, typically completing and approving each phase before the next begins.

## AWS CloudFormation exam questions

Real practice exam questions on AWS CloudFormation, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A company maintains separate resource configuration files for its development and production environments. Both environments require the same network and security design, but production needs larger compute and database resources. Engineers spend time applying each design change to both files, and the files sometimes become inconsistent. Which approach would reduce this maintenance effort while preserving the required capacity differences?

**Correct answer:** Maintain one AWS CloudFormation template and supply environment-specific parameters for compute and database sizes during deployment.

**Explanation:** A parameterized template provides one reusable infrastructure design while allowing each environment to use appropriate resource sizes. This reduces duplicate maintenance and the risk of inconsistent changes.

### Question 2 (MLA-C02)

**Question:**

A company separates its ML approval application and compute provisioning platform into two AWS accounts. The approval application publishes custom events to an Amazon EventBridge custom event bus in the application account. Each event includes an approval status, an environment, and a workload ID.

The architecture requires these events to be forwarded to a custom event bus in the platform account so that multiple independent consumers can use them. Only events with approvalStatus equal to APPROVED and environment equal to production must start an existing AWS Step Functions workflow that provisions GPU resources through AWS CloudFormation. Both accounts are in the same AWS Region, and no cross-account permissions are currently configured.

Which solution meets these requirements?

**Correct answer:** Forward the application events to the platform custom event bus by using a rule with an IAM role that allows events:PutEvents on that bus. Add a resource policy to the platform bus allowing the application account to send events. On the platform bus, create a rule that matches the required approval status and environment and targets the workflow by using a role that allows states:StartExecution.

**Explanation:** Cross-account forwarding requires permission to send events and authorization on the receiving event bus. A rule on the receiving custom bus can filter the event detail fields and start the local workflow by using a target execution role with states:StartExecution permission.

### Question 3 (SAP-C03)

**Question:**

A company uses an AWS CloudFormation StackSet with self-managed permissions to deploy a security baseline from a tooling account in us-east-1 to 30 application accounts. Deployments to us-east-1 and eu-west-1 succeed. The company must extend the same StackSet to ap-east-1, a Region that is disabled by default.

The company has enabled ap-east-1 in all participating accounts and verified that account activation and IAM propagation are complete. The StackSet administration role trusts only cloudformation.amazonaws.com and permits sts:AssumeRole on the designated execution roles. Each target execution role trusts the administration role and has all permissions required by the template. The pipeline has the required CloudFormation and iam:PassRole permissions. No SCPs, permissions boundaries, or explicit denies restrict the deployment.

The company must retain self-managed permissions and continue deploying to the existing Regions. Which change is required before deploying stack instances to ap-east-1?

**Correct answer:** Add cloudformation.ap-east-1.amazonaws.com to the administration role's trust policy alongside cloudformation.amazonaws.com, allowing sts:AssumeRole.

**Explanation:** Self-managed StackSet deployments into a Region that is disabled by default require the administration role to trust that Region's regional CloudFormation service principal. Adding cloudformation.ap-east-1.amazonaws.com enables the required assumption while retaining the existing principal for deployments to the other Regions.

### Question 4 (SOA-C03)

**Question:**

A company uses AWS Organizations with all features enabled. A service-managed AWS CloudFormation StackSet deploys a monitoring baseline to member accounts in us-east-1. The company must extend the baseline to ap-east-1, an opt-in AWS Region, in the same accounts.

The management account has enabled ap-east-1, but the target member accounts show that Region as DISABLED. StackSet deployments to ap-east-1 fail. Trusted access is configured, the template supports ap-east-1, and no IAM policies or service control policies (SCPs) restrict the required operations.

Which solution will allow the engineer to deploy the baseline to ap-east-1 while retaining AWS-managed cross-account deployment permissions?

**Correct answer:** Enable ap-east-1 in each target member account, wait until the Region status is ENABLED in those accounts, and then retry the StackSet deployments.

**Explanation:** Opt-in Regions must be enabled separately for each target account. Enabling the Region only in the management account does not enable it in member accounts. After Region enablement completes, the existing service-managed StackSet can deploy there while retaining AWS-managed cross-account permissions.

### Question 5 (AIP-C01)

**Question:**

An enterprise runs Amazon Bedrock applications in AWS accounts that belong to a dedicated AWS Organizations organizational unit (OU). A platform team has created a parameterized baseline for application execution roles, encrypted storage, and operational alarms. The baseline must be deployed into two approved AWS Regions in every account in the OU, including accounts added later.

The enterprise requires centrally reviewed infrastructure updates and automatic provisioning when an account joins the OU. The platform team must not maintain deployment execution roles separately in each member account. Development and production accounts must use the same infrastructure definition with approved parameter differences. AWS Organizations has all features enabled.

Which implementation meets these requirements?

**Correct answer:** Activate trusted access between CloudFormation StackSets and AWS Organizations. Create a service-managed StackSet targeting the OU and both approved Regions, enable automatic deployment, and manage the template and approved parameter overrides through a reviewed deployment pipeline.

**Explanation:** Service-managed StackSets use AWS Organizations integration to manage deployment permissions without separately maintained execution roles in each account. OU targeting with automatic deployment provisions stack instances when new accounts join the OU. A shared template, approved parameter overrides, and reviewed updates provide repeatable infrastructure with controlled environment differences.

### Question 6 (DEA-C01)

**Question:**

A company deploys a data validation application and its Amazon CloudWatch Logs log group into new environments by using a version-controlled AWS CloudFormation template. Application log messages contain email addresses in formats supported by CloudWatch Logs sensitive data detection.

The company requires email addresses in newly ingested events to be masked when operations engineers view or query the log group. The remaining message content must remain readable. Authorized security investigators must be able to retrieve the original values. The configuration must be deployed automatically in every new environment before the application starts writing logs, without changing application code or creating a separate sanitized log group.

Which change should the data engineer make to the deployment?

**Correct answer:** Add a DataProtectionPolicy to the AWS::Logs::LogGroup resource with Audit and Deidentify operations for the managed EmailAddress data identifier. Ensure application startup depends on creation of the configured log group.

**Explanation:** A CloudWatch Logs data protection policy can detect and mask supported email addresses while preserving the original data for investigators with logs:Unmask permission. Declaring the policy on the log group makes the configuration repeatable through CloudFormation. Creating the configured group before logging begins is important because masking applies to events ingested after the policy is established.

### Question 7 (SCS-C03)

**Question:**

A company uses an AWS Control Tower landing zone to govern its AWS accounts. The security team has developed a CloudFormation template that deploys a company-specific AWS Config rule and its supporting resources without modifying Control Tower-managed resources.

Platform operators must be able to select this approved security customization and its version when creating workload accounts through the Control Tower console. The customization must be deployed as part of the account provisioning workflow. The company does not want to modify the Control Tower-managed Account Factory product or maintain a separate post-provisioning automation pipeline.

Which solution meets these requirements?

**Correct answer:** Publish the template as a versioned AWS Service Catalog product in a blueprint hub account. Configure Account Factory Customization and select the product's blueprint and version when provisioning each workload account.

**Explanation:** Account Factory Customization integrates Service Catalog blueprint products into Control Tower account provisioning. A blueprint can deploy custom security resources from a CloudFormation template. Operators can select the approved blueprint and version during account creation without modifying the Control Tower-managed Account Factory product or maintaining a separate deployment pipeline.

### Question 8 (DVA-C02)

**Question:**

A developer updates an existing AWS CloudFormation staging stack that contains a Lambda-backed API. Each release uses an immutable, versioned code artifact. The update changes only function code and environment variables; it does not change stored data. Resource updates can succeed even when the new release produces incorrect API responses.

An existing Amazon CloudWatch alarm outside the stack enters ALARM when synthetic API tests detect incorrect responses. The alarm is currently OK. The developer must automatically restore the stack's previous code and configuration if this alarm enters ALARM during the update or within 10 minutes after resource provisioning finishes, without implementing custom recovery automation.

How should the developer configure the stack update?

**Correct answer:** Add the CloudWatch alarm ARN to the update's RollbackConfiguration and set MonitoringTimeInMinutes to 10.

**Explanation:** CloudFormation rollback triggers monitor specified CloudWatch alarms during the update and for the configured period after resource provisioning finishes. If the alarm enters ALARM during that interval, CloudFormation rolls back the update, restoring the previous stack configuration and its referenced code artifact.

### Question 9 (DOP-C02)

**Question:**

A company distributes reusable network patterns through a centrally maintained AWS CloudFormation macro. Application templates invoke the macro, which generates security groups and ingress rules based on application parameters. Application teams can also declare security group resources directly.

A deployment pipeline currently evaluates the submitted templates against version-controlled security rules. An audit finds that a template passed these checks even though the macro generated an ingress rule allowing TCP port 22 from 0.0.0.0/0.

The company must automatically reject deployments containing prohibited ingress rules before provisioning any resources, whether the rules are declared directly or generated by the macro. The relevant properties in the transformed templates use literal values. Only the pipeline can deploy stacks, and the company wants to retain the macro-based patterns.

Which pipeline change meets these requirements?

**Correct answer:** Create a CloudFormation change set and wait for its creation to complete. Retrieve its template with GetTemplate and TemplateStage set to Processed. Evaluate that template with CloudFormation Guard rules covering security groups and ingress resources. Execute that same change set only if the evaluation succeeds.

**Explanation:** The processed template includes resources produced by the macro as well as resources declared directly. Creating a change set processes transforms without provisioning stack resources. Evaluating the processed template with explicit Guard rules and blocking execution on failure enforces the standard before provisioning. Executing the same change set preserves the connection between the evaluated definitions and the deployment.

### Question 10 (SAA-C03)

**Question:**

A company runs a customer-facing application across two Availability Zones. A recent infrastructure update unexpectedly replaced a production resource and caused an outage. Infrastructure changes are currently applied by scripts that issue individual AWS API calls.

The company wants to maintain a version-controlled definition of the complete application infrastructure. Before each production deployment, an engineer must review the proposed resource additions, modifications, and deletions, including whether an update might replace a resource. No production changes may occur until the engineer approves the proposal. The company wants to minimize custom deployment logic.

Which solution meets these requirements?

**Correct answer:** Define the infrastructure in version-controlled AWS CloudFormation templates. Create a change set for each proposed production revision, require an engineer to review and approve it, and execute the change set only after approval.

**Explanation:** CloudFormation manages infrastructure from reusable, version-controlled definitions. Change sets preview proposed additions, modifications, deletions, and potential resource replacements without applying them. Separating change set creation from execution provides the required approval gate with little custom deployment logic.

### Question 11 (ANS-C01)

**Question:**

A company uses AWS CloudFormation to provision a new VPC and routing resources for each hybrid application segment. An on-premises configuration host is registered as an AWS Systems Manager managed node. Scripts on this host can stage network-device configuration, test connectivity, activate the segment, and remove the staged configuration.

Each deployment must wait for the CloudFormation stack to finish creating before staging the on-premises configuration. Connectivity tests can take 45 minutes. Only after the tests succeed may the deployment request approval from a network operator, who can take up to 8 hours to respond. Activation must occur only after approval. If testing fails or approval is rejected or times out, automation must remove the staged on-premises configuration before deleting the newly created stack. Existing production segments must remain unchanged.

Which implementation meets these requirements?

**Correct answer:** Use a Systems Manager Automation runbook that waits for stack creation to complete, runs staging and testing through aws:runCommand with appropriate timeouts, and uses aws:approve before activation. Route test failures and approval rejection or timeout to cleanup steps that remove staged configuration, verify its removal, and then delete the new stack.

**Explanation:** The runbook maintains execution state across provisioning, long-running commands, and approval. Waiting for stack completion and command success enforces the required order. Explicit failure paths provide compensating actions for on-premises changes, which CloudFormation does not manage, and ensure cleanup occurs before stack deletion. The steps can target only the newly created segment.

## Practice AWS CloudFormation in a full exam

Questions on AWS CloudFormation in each practice exam, with every answer option and an explanation for each:

- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 68 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 66 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 30 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 26 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 20 questions
- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 16 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 12 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 11 questions
- [MLA-C02](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 7 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 5 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 5 questions

## Learn AWS CloudFormation in lessons

28 short lessons on AWS CloudFormation in 9 certification courses.

- CLF-C02: AWS CloudFormation: templates and stacks (Premium), https://app.blowstack.com/lessons/aws-cloudformation-templates-and-stacks-clf-c02
- MLA-C02: AWS CloudFormation: connecting infrastructure stacks (Premium), https://app.blowstack.com/lessons/aws-cloudformation-connecting-infrastructure-stacks-mla-c02
- SAP-C03: AWS Cloud Development Kit (AWS CDK) vs AWS CloudFormation (Premium), https://app.blowstack.com/lessons/aws-cloud-development-kit-aws-cdk-vs-aws-cloudformation-sap-c03
- SOA-C03: AWS CDK and AWS CloudFormation: authoring versus provisioning (Premium), https://app.blowstack.com/lessons/aws-cdk-and-aws-cloudformation-authoring-versus-provisioning-soa-c03
- AIP-C01: AWS CDK and AWS CloudFormation: abstraction versus deployment (Premium), https://app.blowstack.com/lessons/aws-cdk-and-aws-cloudformation-abstraction-versus-deployment-aip-c01
- DEA-C01: AWS CDK and AWS CloudFormation: authoring and provisioning (Premium), https://app.blowstack.com/lessons/aws-cdk-and-aws-cloudformation-authoring-and-provisioning-dea-c01
