Operations Management

Practicing Infrastructure as Code with AWS CloudFormation - Template Design and Stack Management

Define infrastructure with templates and preview impact with change sets before deployment. Detect configuration drift with drift detection and deploy across your entire organization with StackSets.

About 7 min read

Overview of CloudFormation

CloudFormation is an IaC service that declaratively defines AWS resources in YAML or JSON templates and provisions them as stacks. Compared to manual resource creation, it delivers environment reproducibility, version control, and automation. Templates can be managed in Git and integrated into code reviews and CI/CD pipelines, applying the same quality control processes used in software development to infrastructure changes. SAM is an extension of CloudFormation that simplifies the definition of serverless applications. Through the CloudFormation Registry, you can manage third-party and custom resource types in addition to AWS-native types.

Template Design and Stack Management

Templates define Parameters (up to 200) for deployment-time input values, Mappings for environment-specific settings, and Conditions for conditional logic. A single stack can manage up to 500 resources, and the template body size limit is 1 MB when uploaded via S3. When this limit is exceeded, nested stacks are used for partitioning, referencing child template URLs via AWS::CloudFormation::Stack resources. Change sets are created before stack updates to preview which resources will be added, modified, or deleted. Resources that trigger replacement cause temporary service interruption, making change set review critical. The Outputs section combined with Export/ImportValue enables sharing resource ARNs and IDs across stacks, facilitating team-based separation of concerns with a micro-stack architecture. The DeletionPolicy attribute lets you specify Delete (default), Retain (preserve resource after stack deletion), or Snapshot (take a snapshot before deletion), systematically protecting critical data.

Drift Detection and StackSets

Drift detection identifies whether stack resources have deviated from their template definitions. Manual console operations or script-based changes are detected as drift, and you can review the differences from the template. Automate periodic drift detection with EventBridge schedules to catch configuration deviations early. Note that drift detection does not support all resource types, so you should check the supported resources list in the documentation. StackSets deploy the same template across multiple accounts and regions in a single operation. With Organizations integration, deployments are automated at the OU level. When a new account is added to an OU, the StackSet is automatically deployed, preventing gaps in guardrail coverage. Configure MaxConcurrentCount and FailureToleranceCount appropriately to control risk during large-scale rollouts. For a systematic study of IaC, related books on Amazon can also be a useful reference.

Design Best Practices and Pitfalls

In template design, be cautious about changing logical names (LogicalId). Changing a LogicalId triggers resource replacement, which can lead to data loss for stateful resources such as RDS instances or EBS volumes. Use stack policies to prevent updates or deletions of important resources, and set UpdateReplacePolicy: Retain on critical resources. Circular dependencies are a common error that causes template deployment failures, often occurring in mutual security group references; resolve them by using separate AWS::EC2::SecurityGroupIngress/Egress resources. When a rollback failure (UPDATE_ROLLBACK_FAILED) occurs, use the ContinueUpdateRollback API to specify resources to skip and recover the stack. For large templates, combine cfn-lint with TaskCat for multi-region simultaneous testing and cfn-guard for automated policy compliance validation.

Choosing Between Terraform and CDK

CloudFormation excels in AWS-only environments that don't require multi-cloud support, especially when leveraging native features like StackSets and Organizations integration. State is automatically managed by AWS, eliminating the need to provision S3 buckets or lock tables. Terraform offers multi-cloud support and a broad provider ecosystem, allowing management of non-AWS resources in the same workflow, though state file management (S3 + DynamoDB locking) adds operational overhead. CDK defines infrastructure in general-purpose programming languages like TypeScript or Python, leveraging language features such as loops, conditionals, and abstraction classes to express complex infrastructure concisely. Since CDK ultimately generates CloudFormation templates, you retain access to CloudFormation features like limits and drift detection. As a selection guide: StackSets for organizational guardrail deployment, CDK for programmable abstractions, and Terraform for multi-cloud scenarios.

Pricing and Limit Considerations

CloudFormation itself incurs no additional charges. Costs are limited to the usage fees of the provisioned AWS resources. Third-party resources (extension types via CloudFormation Registry) incur per-handler-operation charges (CREATE/UPDATE/DELETE/READ/LIST operations). Key limits include a default of 2,000 stacks per account (can be raised), 200 Outputs per template, and 200 Mappings per template. To improve template development efficiency, use cfn-lint to catch syntax errors early, and review change sets to confirm impact before deployment. Reuse common resources (VPCs, security groups) with nested stacks to eliminate template duplication. The Rain CLI can streamline template formatting and deployment.

Summary

CloudFormation is a template-based IaC service that delivers infrastructure reproducibility and automation. Change sets let you preview impact before deployment, and drift detection catches configuration deviations. StackSets deploy templates across your entire organization, automating multi-account, multi-region infrastructure management. Protect stateful resources with DeletionPolicy and stack policies, and combine with CDK or Terraform to build an IaC strategy optimized for your project requirements.

Related Services

AWS CloudFormationAn IaC service that defines and provisions AWS resources as code using templatesAmazon S3A scalable object storage serviceAWS LambdaA serverless compute service that runs code without server management

Related Articles

Visually Design Serverless Applications with AWS Application Composer - Automatic IaC Template GenerationLearn about visual design of serverless architectures with Application Composer, automatic SAM template generation, and VS Code integration.IaC with Programming Languages Using AWS CDK - Designing Constructs and StacksLearn about defining infrastructure with TypeScript/Python using CDK, choosing between L1/L2/L3 constructs, and testing techniques.Platform Engineering with AWS Proton - Self-Service Infrastructure Template DeliveryLearn about Proton's infrastructure template management, separation of environments and services, and developer self-service design.

More on This Topic

How AWS Keeps Time Internally - Amazon Time Sync Service and Leap Second Smearing DesignLearn how Amazon Time Sync Service works, how GPS and atomic clocks provide high-precision time sources, the design decision to absorb leap seconds through smearing, and why time synchronization matters in distributed systems.Centralizing SaaS Audit Logs with AWS AppFabric - OCSF Standardization and Security Lake IntegrationLearn how AppFabric collects audit logs from SaaS applications, standardizes them to OCSF format, and builds analysis pipelines.Implementing Feature Flags with AWS AppConfig - Safe Configuration Deployment and RollbackRoll out configuration changes independently from code deployments using Linear and Exponential strategies. Ensure safety with automatic rollback triggered by CloudWatch alarms.Architecture Review - Systematically Evaluate Workloads with the AWS Well-Architected ToolLearn about architecture reviews using the AWS Well-Architected Tool. Covers evaluation based on the six pillars, improvement planning, and custom lens usage.Audit Log Design and Operations - Complete API Activity Recording with CloudTrailLearn how to design audit logs using AWS CloudTrail, including recording API activity, long-term storage in S3, and compliance automation through integration with AWS Config.Lessons from AWS Incident Reports (COE) - How Past Major Outages Shaped Design PrinciplesAnalyze the root causes of past major incidents including the S3 outage, us-east-1 DNS failure, and Kinesis outage from AWS's published Correction of Errors (COE) and incident reports, and explain how they changed AWS's design principles.Tag Design Determines Operations - Trivia and Practical Naming Conventions for AWS Resource Tagging StrategyWe explain why AWS resource tags are not just labels but the foundation for cost allocation, access control, and automation, covering tag key naming conventions, how to use the 50-tag limit, and governance through tag policies.Why AWS Service Quotas Exist - Multi-Tenant Design That Protects Shared InfrastructureExplain how AWS service quotas (formerly service limits) are not mere restrictions but a design to protect other customers in a multi-tenant environment, covering the noisy neighbor problem, soft vs hard limits, and what happens behind quota increase requests.

Similar Articles and Services

AWS CloudFormationAn Infrastructure as Code service that lets you define and manage AWS infrastructure using JSON or YAML templates, handling the entire lifecycle of resources as a single stackHow Far Does CloudFormation Drift Detection See - How It Tracks Manual Changes and Its LimitationsLearn how CloudFormation drift detection internally compares the current state of resources with the expected state defined in templates, the boundary between detectable and undetectable changes, and strategies for drift remediation.What Happens During a CloudFormation Stack Update - Behind Change Sets, Rollbacks, and ReplacementsLearn about the internal processing flow when CloudFormation updates a stack, including how change sets detect differences, the logic behind resource update, replacement, and deletion decisions, and how rollbacks work.AWS IaC Maturity - The Advantage of Declarative Infrastructure Management with CloudFormation, CDK, and SAMExamine the maturity of AWS's Infrastructure as Code ecosystem centered on CloudFormation, CDK, and SAM, compared with Azure ARM/Bicep and GCP Deployment Manager, and how CDK's multi-language support transforms the developer experience.