How widdix/aws-cf-templates works
Main Component Categories
a. Infrastructure Components:
• VPC (Network Layer)
• EC2 (Compute Layer)
• ECS (Container Layer)
• Fargate (Serverless Container Layer)
• State (Data Layer)
• Security
• Operations
Hierarchical Structure
Level 1 (Top Level):
Level 2 (Template Groups):
• Within each category, show the available template variations
• For example, under VPC:
• 2-AZ configuration
• 3-AZ configuration
• 4-AZ configuration
• VPC endpoints
• Flow logs
Specific Elements
Core Infrastructure:
[VPC Templates] → [Compute Layer (EC2/ECS/Fargate)] → [State Layer]
• ↑ ↑ ↑
[Security Layer] -------- [Operations Layer] ------- [Monitoring/Logs]
Service-Specific Implementations:
• WordPress HA setup
• Jenkins deployment
• Static website hosting
Additional Details
Metadata Section:
• Template version compatibility
• AWS region support
• Required permissions
• Dependencies between templates
Integration Points:
• Where custom parameters can be injected
• Integration with external services (e.g., GitHub for auth)
• Points where monitoring and logging are implemented