AWS Cloud Architecture & Infrastructure Skills
Overview
Practical patterns and tooling for AWS development focused on infrastructure automation and cloud architecture. Covers provisioning, CI/CD, security, and cost-aware design using common IaC and AWS services. Aimed at developers and architects who need repeatable, production-ready approaches for AWS workloads.
How This Skill Works
Inspects your architecture goals and recommends infrastructure-as-code patterns, service choices, and deployment workflows. Suggests templates, module boundaries, and automation steps for Terraform, CloudFormation, CDK, and CI pipelines. Highlights security controls, networking topologies, and cost optimization measures tailored to the chosen services.
When to Use
- Designing or refactoring cloud-native applications on AWS
- Automating environment provisioning with Terraform, CDK, or CloudFormation
- Setting up secure CI/CD pipelines for infrastructure and application code
- Evaluating service choices for cost, scalability, and fault tolerance
- Preparing production runbooks, observability, and incident response
Best Practices
- Model infrastructure as modular IaC components with clear ownership
- Enforce least-privilege IAM policies and use short-lived credentials
- Automate tests and policy checks in CI for IaC changes
- Design multi-AZ and graceful-failover patterns for critical workloads
- Monitor cost and performance with tagging, budgets, and observability
Example Use Cases
- VPC with Transit Gateway - Create segmented subnets for multi-tier apps
- Blue/Green Deployments - Implement canary deployments for ECS, EKS, or Lambda workloads
- Infrastructure Pipelines - Build automated pipelines that run plan/apply with approvals
- Account Hardening - Harden with SCPs, IAM roles, and centralized logging/monitoring
- Migration - Migrate monolithic services to serverless or container platforms with staged rollout
IaC Tool Selection Guide
| Tool |
Best For |
Strengths |
| Terraform |
Cross-cloud consistency |
Large module ecosystem, HCL declarative syntax |
| CDK |
Complex logic, familiar languages |
TypeScript/Python/Java constructs, L2/L3 abstractions |
| CloudFormation |
Native AWS support |
No external tooling, deep AWS integration |
Environment Consistency
To keep environments consistent across dev, staging, and prod:
- Use the same IaC modules with parameterized inputs
- Enforce policy-as-code checks in CI
- Apply automated promotion gates so the same templates and tests run across environments
Architecture Patterns
Multi-AZ High Availability
- Deploy across at least 2 AZs
- Use ALB/NLB for traffic distribution
- Configure auto-scaling groups with health checks
- Implement database read replicas across AZs
Cost Optimization
- Right-size instances using AWS Compute Optimizer
- Use Savings Plans or Reserved Instances for steady-state workloads
- Implement auto-scaling for variable workloads
- Tag all resources for cost allocation and tracking
- Set up AWS Budgets with alerts
Security Baseline
- Enable AWS CloudTrail in all regions
- Configure AWS Config rules for compliance
- Use AWS GuardDuty for threat detection
- Implement VPC Flow Logs
- Enable AWS Security Hub for centralized findings
1---2name: aws-skills3description: Guides AWS development with infrastructure automation and cloud architecture patterns. Use when designing or refactoring cloud-native applications on AWS, automating environment provisioning with Terraform/CDK/CloudFormation, setting up secure CI/CD pipelines, evaluating service choices for cost/scalability/fault tolerance, or preparing production runbooks and observability.4---56# AWS Cloud Architecture & Infrastructure Skills78## Overview910Practical patterns and tooling for AWS development focused on infrastructure automation and cloud architecture. Covers provisioning, CI/CD, security, and cost-aware design using common IaC and AWS services. Aimed at developers and architects who need repeatable, production-ready approaches for AWS workloads.1112## How This Skill Works1314Inspects your architecture goals and recommends infrastructure-as-code patterns, service choices, and deployment workflows. Suggests templates, module boundaries, and automation steps for Terraform, CloudFormation, CDK, and CI pipelines. Highlights security controls, networking topologies, and cost optimization measures tailored to the chosen services.1516## When to Use1718- Designing or refactoring cloud-native applications on AWS19- Automating environment provisioning with Terraform, CDK, or CloudFormation20- Setting up secure CI/CD pipelines for infrastructure and application code21- Evaluating service choices for cost, scalability, and fault tolerance22- Preparing production runbooks, observability, and incident response2324## Best Practices2526- Model infrastructure as modular IaC components with clear ownership27- Enforce least-privilege IAM policies and use short-lived credentials28- Automate tests and policy checks in CI for IaC changes29- Design multi-AZ and graceful-failover patterns for critical workloads30- Monitor cost and performance with tagging, budgets, and observability3132## Example Use Cases33341. **VPC with Transit Gateway** - Create segmented subnets for multi-tier apps352. **Blue/Green Deployments** - Implement canary deployments for ECS, EKS, or Lambda workloads363. **Infrastructure Pipelines** - Build automated pipelines that run plan/apply with approvals374. **Account Hardening** - Harden with SCPs, IAM roles, and centralized logging/monitoring385. **Migration** - Migrate monolithic services to serverless or container platforms with staged rollout3940## IaC Tool Selection Guide4142| Tool | Best For | Strengths |43|------|----------|-----------|44| **Terraform** | Cross-cloud consistency | Large module ecosystem, HCL declarative syntax |45| **CDK** | Complex logic, familiar languages | TypeScript/Python/Java constructs, L2/L3 abstractions |46| **CloudFormation** | Native AWS support | No external tooling, deep AWS integration |4748## Environment Consistency4950To keep environments consistent across dev, staging, and prod:51- Use the same IaC modules with parameterized inputs52- Enforce policy-as-code checks in CI53- Apply automated promotion gates so the same templates and tests run across environments5455## Architecture Patterns5657### Multi-AZ High Availability58- Deploy across at least 2 AZs59- Use ALB/NLB for traffic distribution60- Configure auto-scaling groups with health checks61- Implement database read replicas across AZs6263### Cost Optimization64- Right-size instances using AWS Compute Optimizer65- Use Savings Plans or Reserved Instances for steady-state workloads66- Implement auto-scaling for variable workloads67- Tag all resources for cost allocation and tracking68- Set up AWS Budgets with alerts6970### Security Baseline71- Enable AWS CloudTrail in all regions72- Configure AWS Config rules for compliance73- Use AWS GuardDuty for threat detection74- Implement VPC Flow Logs75- Enable AWS Security Hub for centralized findings
aws-samples