GCP · Free CLI guide · kloudaudit.eu

How to Find Idle GCP VM Instances Using gcloud CLI

⚡ Quick answer — copy and run

gcloud compute instances list --format=table
1

Make sure you have the AWS CLI configured: aws configure

2

Run the command above. Review the output for resources to clean up.

3

Delete or stop resources that are confirmed idle or unused.

🔍

Don't want to script this manually?

KloudAudit finds this — and 17 other cost leaks — in 15 minutes. No credentials. No agents. Just your answers.

✓18 structured checks across compute, storage, network, database, governance
✓Waste Score + savings estimate for your exact bill size
✓AI Blueprint with exact CLI commands — $79, delivered in 2 minutes
Run Free Audit →

Why this matters

GCP charges for VM instances even when they are sitting idle. Sustained use discounts only apply to running instances — stopped instances still charge for attached persistent disks.

⚠ Always verify resources are genuinely unused before deleting. Check with your team — a "stopped" instance may be intentional.

Find all 18 cost leaks at once

Teams typically find $500–$4,000+/month. Free. No credentials.

kloudaudit.eu →
KloudAudit · kloudaudit.eu · Built by Samuel Ayodele Adomeh · Senior DevOps Engineer · Wrocław, Poland
Savings estimates are based on typical findings across cloud environments and not a guarantee.