Help me audit our cloud bill and find real savings — not 'just turn off things you don't need.'
CLOUD PROVIDER: {AWS / GCP / Azure / multi}
MONTHLY BILL (approx): {amount}
TOP 3 SERVICES BY SPEND: {service_and_spend}
INFRA TYPE: {ECS / EKS / VMs / serverless / mixed}
TEAM SIZE managing infra: {count}
GROWTH PHASE: {steady / 2x_growth / paused}
KNOWN WASTE areas you suspect: {list_or_'unknown'}
CONSTRAINTS: {can't_take_down_X / compliance_requires_Y}
WHAT YOU'VE ALREADY DONE: {RIs / savings_plans / autoscaling_already / etc.}
DESIGN a 3-pass audit:
**Pass 1 — The obvious wins (1 hour):**
- Unattached EBS volumes / disks
- Idle elastic IPs
- Snapshots of deleted resources
- Over-provisioned reserved capacity
- Forgotten dev/staging resources running 24/7
**Pass 2 — Right-sizing (4-6 hours):**
- EC2 / VM instance type vs actual CPU/mem utilization (look at 30 days p95)
- RDS instance sizing
- EKS node groups / cluster autoscaler tuning
- Lambda memory settings
- Storage class tiering (S3 IA vs Standard)
**Pass 3 — Architecture savings (1-3 days):**
- Multi-AZ vs single-AZ for non-critical workloads
- NAT Gateway egress (often the silent killer)
- Cross-region data transfer
- Caching layer to reduce DB load
- Spot/preemptible instances for batch
FOR EACH PASS:
- 3-5 specific things to check
- How to find the data (which dashboard, query, or CLI)
- Realistic % savings range
- Risk level (low / medium / high)
End with: realistic total annual savings range from a typical audit on this size of bill.0 copies·0 saves·1 views
251 words·1,523 chars
Sample output
Provider: AWS · Monthly: $42K · Top 3: EC2 ($18K), RDS ($7K), Data Transfer ($5K) · Infra: ECS Fargate + RDS Postgres + S3 · Team: 1 part-time SRE · Growth: steady · Suspect waste: dev environments + over-provisioned RDS · Constraints: prod must stay multi-AZ · Already done: 1-yr Compute Savings Plan covering 40% of compute.
Pass 1 — Obvious wins (1 hour). Expected savings: 5-15% off the monthly bill.
Unattached EBS volumes:
aws ec2 describe-volumes --filters Name=status,Values=available --query 'Volumes[*].[VolumeId,Size,VolumeType,CreateTime]' --output tableParameters
Text generation parameters
FAQ
Tag everything before you optimize. 'I think this is dev' is the most expensive sentence in cloud auditing. A 1-hour tagging exercise unlocks every 'group by environment' analysis after. The prompt targets ChatGPT (GPT-4) and lives in the Coding & Development category on mycopyprompt.
This prompt is written for ChatGPT (GPT-4). It's a text/chat prompt — paste it into ChatGPT (GPT-4) (or compatible LLMs like Claude or GPT-4) to get the expected output.
1. Click the Copy button on this page to copy the full prompt. 2. Open ChatGPT (GPT-4). 3. Paste the prompt into a new conversation. 4. Replace any {placeholders} with your specifics, then send. Most prompts produce the right output on the first try; complex ones may need 1-2 iterations.
Yes — every prompt on mycopyprompt is free forever. No paywall, no signup wall for browsing or copying. You can use it for personal or commercial work, just don't redistribute the entire mycopyprompt library.
Absolutely — most prompts are templates. Look for {placeholders} (curly braces) and swap them with your own values. You can also reword sections, add constraints, or chain it with other prompts.
See the "Sample output" panel above — that's a real example of what ChatGPT (GPT-4) returns when this prompt runs. Your output will vary in wording but should follow the same structure and depth.
Similar prompts
Matched against every prompt in the catalog by title.
Idle elastic IPs:
aws ec2 describe-addresses --query 'Addresses[?AssociationId==null]'Orphaned snapshots:
aws ec2 describe-snapshots --owner-ids self --query 'Snapshots[*].[SnapshotId,VolumeId,VolumeSize,StartTime]' then cross-ref with existing volumes.Forgotten dev/staging resources running 24/7:
Environment={prod,staging,dev}. Schedule dev/staging to stop at 8pm and start at 8am weekdays. AWS Lambda + EventBridge, or 'Instance Scheduler' solution.Compute Savings Plan utilization:
Pass 1 estimated savings: $4,000-12,000/month ($48K-144K/yr).
Pass 2 — Right-sizing (4-6 hours). Expected savings: 10-30% more off.
ECS Fargate task sizing:
RDS instance sizing:
db.r6i.2xlarge → db.r6i.xlarge.)RDS storage IOPS:
Lambda memory settings:
S3 storage class tiering:
Pass 2 estimated savings: $2,000-8,000/month additional.
Pass 3 — Architecture savings (1-3 days). Expected savings: 5-20% more, but bigger investment.
NAT Gateway egress:
Cross-AZ data transfer:
Multi-AZ for dev/staging:
Caching to reduce DB load:
Spot for batch / async workloads:
Pass 3 estimated savings: $1,500-6,000/month additional.
Total typical realistic savings on a $42K/month bill:
This level of cost reduction is achievable on most cloud bills that have grown organically without a dedicated FinOps pass.
Don't try to do all three passes in one week. Pass 1 in a single sitting → bank the wins. Pass 2 over 2 weeks. Pass 3 over a month with proper changes / staging tests.