aws-cloudformation-vpc_skill
- Python
99
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill giuseppe-trisciuoglio/developer-kit --skill aws-cloudformation-vpc- SKILL.md33.3 KB
Overview
This skill provides AWS CloudFormation patterns and ready-made templates for building VPC infrastructure. It focuses on production-ready VPCs with public and private subnets, route tables, NAT and Internet gateways, endpoints, and cross-stack outputs. Use it to standardize template structure, parameters, mappings, and conditions for reusable infrastructure as code.
How this skill works
The skill supplies example CloudFormation YAML snippets and recommended template sections to define VPC resources and networking constructs. It outlines parameter types and constraints, mapping and condition patterns, and exportable Outputs for cross-stack references so you can compose modular stacks. Examples include single-AZ and multi-AZ VPCs with NAT Gateway routing and Internet Gateway routing for public subnets.
When to use it
- Creating a new VPC with public and private subnets for web and backend tiers
- Configuring route tables for internet-facing and NAT-based outbound access
- Implementing Parameters and AWS-specific parameter types for safer input
- Exporting VPC and subnet IDs for use in other stacks or services
- Organizing templates with Mappings, Conditions, and Metadata for reuse
Best practices
- Use AWS-specific parameter types (e.g., AWS::EC2::Subnet::Id) to validate inputs and improve console UX
- Distribute subnets across AZs and create one NAT Gateway per AZ for high availability
- Tag resources consistently and export only stable IDs needed by other stacks
- Use Conditions to toggle optional resources (like NAT Gateways) to control cost
- Keep Resources section minimal and push environment-specific values into Parameters or Mappings
Example use cases
- Quick-start template to provision a simple VPC with a single public subnet and Internet Gateway
- Production template to deploy multi-AZ public and private subnets with NAT Gateways and route tables
- Reusable network module that exports VPC and subnet IDs for application stacks
- Templates using Conditions to deploy optional VPC endpoints or NAT Gateways based on environment
- Mapping-driven AMI selection and instance sizing per region and environment
FAQ
Yes. Export the VPC and subnet IDs from the network stack and import them in consumer stacks using Fn::ImportValue for safe cross-stack references.
How do I avoid single-point-of-failure NAT architecture?
Create a NAT Gateway in each AZ where you have private subnets and route private subnet traffic to the NAT Gateway in the same AZ for fault isolation.
