← LeaderboardThe Skill Leaderboard

cloudformation-best-practices

CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates.

Published by sickn33 ↗sickn33/agentic-awesome-skills

Try your first task

Start a fresh conversation. Replace the highlighted placeholders.

Use cloudformation-best-practices to review [CloudFormation template] and return production-ready YAML improvements for parameterization, stateful-resource retention, and stack structure; do not deploy it.

Required inputs

[CloudFormation template]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: cloudformation-best-practicesdescription: "CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates."risk: criticalsource: communitydate_added: "2026-02-27"

You are an expert in AWS CloudFormation specializing in template optimization, stack architecture, and production-grade infrastructure deployment.

Use this skill when

Writing or reviewing CloudFormation templates (YAML/JSON)
Optimizing existing templates for maintainability and cost
Designing nested or cross-stack architectures
Troubleshooting stack creation/update failures and drift

Do not use this skill when

The user prefers CDK or Terraform over raw CloudFormation
The task is application code, not infrastructure

Instructions

Use YAML over JSON for readability.
Parameterize environment-specific values; use Mappings for static lookups.
Apply DeletionPolicy: Retain on stateful resources (RDS, S3, DynamoDB).
Use Conditions to support multi-environment templates.
Validate templates with aws cloudformation validate-template before deployment.
Prefer !Sub over !Join for string interpolation.

Examples

Example 1: Parameterized VPC Template

AWSTemplateFormatVersion: "2010-09-09"
Description: Minimal VPC skeleton; subnet/routing/security resources are not included

Parameters:
  Environment:
    Type: String
    AllowedValues: [dev, staging, prod]
  VpcCidr:
    Type: String
    Default: "10.0.0.0/16"

Conditions:
  IsProd: !Equals [!Ref Environment, prod]

Resources:
  VPC:
    Type: AWS::EC2::VPC
    Properties:
      CidrBlock: !Ref VpcCidr
      EnableDnsSupport: true
      EnableDnsHostnames: true
      Tags:
        - Key: Name
          Value: !Sub "${Environment}-vpc"

Outputs:
  VpcId:
    Value: !Ref VPC
    Export:
      Name: !Sub "${Environment}-VpcId"

Best Practices

✅ Do: Use Outputs with Export for cross-stack references
✅ Do: Add DeletionPolicy and UpdateReplacePolicy on stateful resources
✅ Do: Use cfn-lint and cfn-nag in CI pipelines
❌ Don't: Hardcode ARNs or account IDs — use !Sub with pseudo parameters
❌ Don't: Put all resources in a single monolithic template

Troubleshooting

Problem: Stack stuck in UPDATE_ROLLBACK_FAILED Solution: Inspect the exact stack events and failed-resource state first. Skipping resources is a last-resort recovery action requiring approval; skipped resources can remain inconsistent with the template and must be reconciled before another update.

Limitations

validate-template checks template form, not deployability, cost, policy or safe replacements. Review an explicit change set in the authorized account/region, especially deletes/replacements and IAM capabilities. DeletionPolicy alone does not protect replacement; evaluate UpdateReplacePolicy and backups.
Never execute a deploy/recovery or change a stack merely to validate these examples. The VPC skeleton does not provide production networking or public/private subnet isolation.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.