1---2name: infrastructure-review3description: Review infrastructure configurations for reliability, security, cost efficiency, and operational best practices across cloud and on-prem environments. TRIGGER when: user says /infrastructure-review, "review our infrastructure", "audit cloud setup", "infra review", or "check our AWS/GCP/Azure config".4---56# Infrastructure Review78You are a senior infrastructure engineer performing a comprehensive review. Evaluate against reliability, security, cost, and operational excellence pillars.910## Process1112### Step 1: Understand the Environment1314| Parameter | Description |15|-----------|-------------|16| Cloud provider(s) | AWS, GCP, Azure, on-prem, hybrid |17| IaC tool | Terraform, CloudFormation, Pulumi, CDK, Ansible |18| Architecture pattern | Microservices, monolith, serverless, event-driven |19| Scale | Traffic volume, data size, team size |20| Compliance requirements | SOC2, HIPAA, PCI-DSS, GDPR |2122### Step 2: Review Checklist2324#### Reliability2526| Check | What to Look For |27|-------|-----------------|28| High availability | Multi-AZ / multi-region, no single points of failure |29| Auto-scaling | Scaling policies configured, min/max instances appropriate |30| Backup & recovery | Automated backups, tested restore, RPO/RTO defined |31| Health checks | LB health checks, container liveness/readiness probes |32| Circuit breakers | Retry policies, timeout configs, fallback mechanisms |3334#### Security3536| Check | What to Look For |37|-------|-----------------|38| Network segmentation | VPC design, subnet isolation, security groups |39| IAM | Least-privilege roles, no wildcard permissions, MFA enforced |40| Encryption | At-rest (KMS), in-transit (TLS 1.2+), key rotation |41| Secrets management | No hardcoded secrets, using vault/SSM/secrets manager |42| Logging & audit | CloudTrail / audit logs enabled, tamper-proof storage |4344#### Cost Efficiency4546| Check | What to Look For |47|-------|-----------------|48| Right-sizing | Instances matched to actual utilization |49| Reserved/committed use | Savings plans for predictable workloads |50| Idle resources | Unused volumes, unattached IPs, stopped instances |51| Storage tiering | Lifecycle policies, archive old data |5253#### Operational Excellence5455| Check | What to Look For |56|-------|-----------------|57| IaC coverage | All resources managed by code, no manual changes |58| Tagging | Consistent tags for cost allocation, ownership, environment |59| Monitoring | Metrics, logs, traces for all critical services |60| Deployment pipeline | CI/CD for infrastructure changes |6162## Output Format6364```markdown65## Infrastructure Review: [Environment]6667### Summary68- Overall health: [Good / Needs Attention / Critical]69- Findings: N critical, N high, N medium, N low7071### Findings72#### [SEVERITY]: [Title]73**Resource:** [specific resource or config]74**Pillar:** Reliability | Security | Cost | Operations75**Issue:** [What is wrong]76**Risk:** [What could happen]77**Recommendation:** [What to do]78**Effort:** Low / Medium / High7980### Cost Optimization Opportunities81| Opportunity | Estimated Savings | Effort |8283### Action Plan84| Priority | Action | Owner | Effort | Impact |85```8687## Quality Checklist8889- [ ] All four pillars reviewed (reliability, security, cost, operations)90- [ ] Findings reference specific resources or configurations91- [ ] Recommendations are actionable with effort estimates92- [ ] Cost savings are quantified where possible93- [ ] Security findings flagged with appropriate urgency9495## Edge Cases9697- **Multi-cloud**: Review each provider independently, then assess cross-cloud networking98- **Legacy infrastructure**: Focus on migration path and risk reduction99- **Startup / early stage**: Prioritize security and reliability basics over optimization100- **Regulated industry**: Lead with compliance requirements, map controls to infrastructure
ashutoshsrivastava17