cloudformation-generator

AWS CloudFormation cross-stack references are defined using outputs with unique export names, then referenced in other stacks via Fn::ImportValue. This approach supports repeatable deployments and common intrinsic functions across separate stacks.

Generating AWS CloudFormation YAML templates requires defining infrastructure requirements including resources, parameters, environments, and cross-stack dependencies. The skill enforces correct AWSTemplateFormatVersion, section ordering, safe string handling, and AWS-specific parameter types for repeatable deployments.

AWS CloudFormation cross-stack references are defined using outputs with unique export names, then referenced in other stacks via Fn::ImportValue. This approach supports repeatable deployments and common intrinsic functions across separate stacks.

The best way to validate AWS CloudFormation templates is using cloudformation-validator or cfn-lint. The skill enforces safe naming, portability, AWS-specific parameter types, and correct YAML section ordering to ensure production-ready infrastructure-as-code.

Yes, you can translate manual AWS console configurations into infrastructure-as-code by defining the resources and parameters. The skill guides you through specifying environments, subnet IDs, cross-stack dependencies, and deletion behavior for parameterized YAML templates.

Limitations include ensuring you provide correct AWSTemplateFormatVersion, Description, and section ordering. You must manage safe string handling, unique export names for cross-stack references, and AWS-specific parameter types to maintain portability and pass validation.