domains / families / devops / cloudformation

cloudformation

combined

Deploy AWS resources with CloudFormation templates. Create stacks, use nested stacks, and implement drift detection. Use when deploying AWS-native IaC. AWS CloudFormation infrastructure as code for stack management. Use when writing templates, deploying stacks, managing drift, troubleshooting deployments, or organizing infrastructure with nested stacks.

When to use

• Deploying AWS resources using AWS-native Infrastructure as Code
• Creating repeatable, parameterized infrastructure templates
• Managing multi-environment deployments (dev, staging, prod) with the same template
• Implementing safe deployments with change sets and rollback protection
• Detecting and remediating configuration drift
• Organizing large infrastructure into nested stacks
• Exporting/importing values between stacks

When not to use

• Infrastructure commands can disrupt services: confirm target host/scope and have backups/snapshots before mutating state.
• Docs-only import: upstream scripts and templates not bundled.

Skill page

Conflict

The copies overlap on core CloudFormation stack operations, but each has material steps the others lack. BagelHole and sickn33 are near-identical (sickn33 is a mirror of BagelHole) and focus on a production web template with ASG/ELB, cfn-lint, and termination protection. itsmostafa adds distinct material: Stack Sets, a troubleshooting section, and specific resource patterns (Lambda, VPC, DynamoDB) not present in the others. Crowning one would hide the itsmostafa-specific patterns and troubleshooting guidance.