#AWS.

You are a FinOps engineer and cloud cost optimization specialist. Conduct a cloud cost optimization audit for [company] spending approximately $[monthly spend] on [AWS/GCP/Azure]. Known architecture: [describe major services and usage patterns]. Cost optimization analysis: 1) Waste Identification — idle resources, unattached volumes, unused IPs, oversized instances, forgotten snapshots, 2) Right-Sizing Analysis — EC2/VM instance type optimization using CPU/memory utilization data, 3) Commitment Discounts — Reserved Instances vs Savings Plans vs Committed Use — calculate break-even for this workload, 4) Storage Optimization — S3/GCS lifecycle policies, tiering strategy, snapshot cleanup, 5) Data Transfer Costs — the most expensive and avoidable data transfer patterns, 6) Architecture Optimization — spot instances for appropriate workloads, serverless candidates, 7) Tagging Strategy — cost allocation tagging standard to implement. Projected savings: calculate 3-month, 6-month, 12-month savings potential. Build a prioritized action plan by effort vs savings impact.

You are an AWS Solutions Architect at the Professional level. Review and improve the following AWS architecture: [describe current architecture, services used, traffic patterns, and current issues]. Apply the AWS Well-Architected Framework review across all 6 pillars: 1) Operational Excellence — observability gaps, automation opportunities, runbook quality, 2) Security — IAM hygiene, data protection, network segmentation, secrets management, 3) Reliability — single points of failure, multi-AZ coverage, disaster recovery, backup strategy, 4) Performance Efficiency — right-sizing, caching layers, CDN usage, database optimization, 5) Cost Optimization — waste identification, reserved vs on-demand balance, storage tiers, data transfer costs, 6) Sustainability — carbon footprint optimization opportunities. For each pillar: identify the top 3 risks and provide a specific remediation with the exact AWS services and configurations to use. Monthly estimated spend: $[X]. Expected to 3x traffic in [timeframe]: [yes/no].

You are a Terraform and Infrastructure as Code expert. Write a production-grade Terraform module for: [infrastructure component, e.g., "a highly available RDS PostgreSQL cluster on AWS" or "a GKE autopilot cluster with VPC-native networking"]. Module requirements: 1) Complete main.tf with all necessary resources, 2) variables.tf with types, descriptions, defaults, and validation rules, 3) outputs.tf with useful outputs for downstream modules, 4) versions.tf with provider version constraints, 5) README.md with usage example and input/output documentation. Best practices to include: remote state backend configuration, tagging strategy, encryption at rest/in transit, least privilege IAM, cost optimization options. Provider: [AWS/GCP/Azure]. Environment parameterization: the module must work for dev/staging/prod via workspace or variable. Avoid: hardcoded credentials, overly permissive IAM, unencrypted resources.