cloud-infralisted

Guide cloud infrastructure decisions — compute sizing and serverless tradeoffs, storage class selection and lifecycle policies, VPC networking and DNS design, IAM least-privilege policies and role architecture, monitoring and alerting with SLI/SLO, cost optimization through rightsizing and reserved instances, disaster recovery strategies and backup planning, and compliance with encryption standards and audit logging. Use when designing cloud architecture, selecting AWS services, setting up multi-region deployments, or auditing security and cost posture.
ecoma-io/touchstone · ★ 1 · DevOps & Infrastructure · score 65

Install: claude install-skill ecoma-io/touchstone

# Cloud Infrastructure Cloud infrastructure is code that provisions, connects, and protects the runtime environment. Every decision has a blast radius — before changing anything, name the worst case: "if this breaks, what stops working, and how do I know?" The default stance is immutable infrastructure: treat servers as cattle, not pets. If a server is sick, replace it — do not SSH in to fix it. Cost is a first-class constraint. An architecture that works at 10x the price is not a working architecture. ## Decision routing This skill covers eight cloud infrastructure domains. The details for each are in `references/` — load the file that matches the decision at hand. | Domain | When | Reference | | ----------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------- | | Compute | EC2 instance sizing, serverless vs. containers, auto-scaling, spot instances | [compute](references/compute.md) | | Storage | S3 buckets, EBS volumes, EFS file systems, lifecycle policies, versioning, encryption | [storage](references/storage.md) | | Networking | VPC design, DNS and CDN, load balancers, security groups, NACLs | [networking](references/networking.md)