
Cloud Infrastructure
- 38 installs
- 4 repo stars
- Updated April 11, 2026
- 89jobrien/steve
cloud-infrastructure is a Claude Code skill covering multi-cloud architecture, Infrastructure as Code with Terraform, cost optimization, and production deployment across AWS, Azure, and GCP.
About
cloud-infrastructure is a Claude Code skill covering cloud architecture and deployment across AWS, Azure, and GCP. It maps compute, storage, and database patterns per provider, documents Terraform IaC structure and state management, and details cost optimization, high-availability, and multi-region strategies. A developer uses it when designing a cloud architecture, writing Infrastructure as Code, or right-sizing costs. It also covers security best practices and monitoring.
- Cloud architecture patterns across AWS, Azure, and GCP with per-provider service mappings
- Terraform IaC best practices, state management, and cost optimization
- High-availability, multi-region, security, and monitoring patterns
Cloud Infrastructure by the numbers
- 38 all-time installs (skills.sh)
- Ranked #765 of 1,039 Cloud & Infrastructure skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
cloud-infrastructure capabilities & compatibility
- Capabilities
- cloud architecture · iac terraform · cost optimization · high availability design
- Works with
- aws · azure · gcp · terraform
- Use cases
- devops · ci cd
- Pricing
- Free
What cloud-infrastructure says it does
Comprehensive cloud infrastructure skill covering multi-cloud architecture, Infrastructure as Code, cost optimization, and production deployment patterns.
Reserved Instances (1-3 year commitment): 30-60% savings
npx skills add https://github.com/89jobrien/steve --skill cloud-infrastructureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 38 |
|---|---|
| repo stars | ★ 4 |
| Last updated | April 11, 2026 |
| Repository | 89jobrien/steve ↗ |
What it does
Design multi-cloud architecture, write Terraform IaC, and optimize cost and availability across AWS, Azure, and GCP.
Who is it for?
Designing multi-cloud architecture and Terraform IaC with cost and availability optimization
Skip if: Application-level frontend or backend feature development
When should I use this skill?
You are designing cloud architecture, implementing Terraform IaC, optimizing costs, or setting up multi-region deployments
What you get
A cloud architecture and Terraform IaC plan with cost-optimization and high-availability strategies.
- cloud architecture design
- Terraform module structure
- cost-optimization plan
By the numbers
- 3 cloud providers covered (AWS, Azure, GCP)
- Reserved Instances 30-60% savings; spot instances 60-90% savings
Files
Cloud Infrastructure
Comprehensive cloud infrastructure skill covering multi-cloud architecture, Infrastructure as Code, cost optimization, and production deployment patterns.
When to Use This Skill
- Designing cloud architecture for new applications
- Implementing Infrastructure as Code (Terraform, CloudFormation, Pulumi)
- Cost optimization and resource right-sizing
- Multi-region and high-availability deployments
- Cloud migration planning
- Security and compliance implementation
- Auto-scaling and performance optimization
Cloud Architecture Patterns
Compute Patterns
| Pattern | AWS | Azure | GCP | Use Case |
|---|---|---|---|---|
| Serverless | Lambda | Functions | Cloud Functions | Event-driven, variable load |
| Containers | ECS/EKS | AKS | GKE | Microservices, consistent env |
| VMs | EC2 | Virtual Machines | Compute Engine | Legacy apps, full control |
| Batch | Batch | Batch | Batch | Large-scale processing |
Storage Patterns
| Type | AWS | Azure | GCP | Use Case |
|---|---|---|---|---|
| Object | S3 | Blob Storage | Cloud Storage | Static files, backups |
| Block | EBS | Managed Disks | Persistent Disk | Database storage |
| File | EFS | Azure Files | Filestore | Shared file systems |
| Archive | Glacier | Archive | Coldline | Long-term retention |
Database Patterns
| Type | AWS | Azure | GCP | Use Case |
|---|---|---|---|---|
| Relational | RDS, Aurora | SQL Database | Cloud SQL | ACID transactions |
| NoSQL | DynamoDB | Cosmos DB | Firestore | Flexible schema |
| Cache | ElastiCache | Cache for Redis | Memorystore | Session, caching |
| Data Warehouse | Redshift | Synapse | BigQuery | Analytics |
Infrastructure as Code
Terraform Best Practices
Project Structure:
infrastructure/
├── modules/
│ ├── networking/
│ ├── compute/
│ └── database/
├── environments/
│ ├── dev/
│ ├── staging/
│ └── prod/
├── main.tf
├── variables.tf
├── outputs.tf
└── versions.tfState Management:
- Use remote state (S3, Azure Blob, GCS)
- Enable state locking (DynamoDB, Blob lease)
- Separate state per environment
- Never commit state files
Module Design:
- Single responsibility per module
- Expose minimal required variables
- Document inputs/outputs
- Version modules with git tags
Cost Optimization
Compute Savings:
- Reserved Instances (1-3 year commitment): 30-60% savings
- Spot/Preemptible instances: 60-90% savings for interruptible workloads
- Right-sizing: Match instance size to actual usage
- Auto-scaling: Scale down during low usage
Storage Savings:
- Lifecycle policies: Auto-transition to cheaper tiers
- Compression: Reduce storage footprint
- Deduplication: Eliminate redundant data
- Delete unused resources: Orphaned volumes, snapshots
Network Savings:
- Use CDN for static content
- Optimize data transfer paths
- Use private endpoints
- Compress API responses
High Availability Patterns
Multi-AZ Deployment
- Deploy across 2-3 availability zones
- Use load balancers for distribution
- Database replication across AZs
- Automatic failover configuration
Multi-Region Deployment
- Active-active or active-passive
- DNS-based routing (Route53, Traffic Manager)
- Data replication strategy
- Disaster recovery procedures
Resilience Patterns
- Circuit breakers for external dependencies
- Retry with exponential backoff
- Bulkhead isolation
- Graceful degradation
Security Best Practices
Identity & Access
- Principle of least privilege
- Use IAM roles, not long-term credentials
- Enable MFA for privileged accounts
- Regular access reviews
Network Security
- VPC/VNet isolation
- Security groups as firewalls
- Private subnets for backend services
- VPN/Direct Connect for hybrid
Data Protection
- Encryption at rest (KMS)
- Encryption in transit (TLS)
- Key rotation policies
- Backup and recovery testing
Monitoring & Observability
Key Metrics
- CPU, Memory, Disk utilization
- Network throughput and latency
- Error rates and types
- Cost per service/team
Alerting Strategy
- Set thresholds based on baselines
- Alert on symptoms, not causes
- Runbooks for each alert
- Escalation paths defined
Reference Files
- `references/terraform_patterns.md` - IaC patterns and examples
- `references/cost_optimization.md` - Detailed cost reduction strategies
Integration with Other Skills
- security-engineering - For security architecture
- network-engineering - For network design
- performance - For optimization strategies
- devops-runbooks - For operational procedures
Related skills
FAQ
Which clouds does it cover?
AWS, Azure, and GCP, with per-provider mappings for compute, storage, and database patterns.
What cost savings does it document?
Reserved Instances (30-60%), spot/preemptible instances (60-90% for interruptible workloads), right-sizing, and auto-scaling.