Money Left on the Table: 10 GCP Settings Your Team Forgot to Turn On
Photo: engineer analyzing cloud cost dashboard on laptop screen, via static.wixstatic.com
Every month, somewhere in America, an engineering manager opens a GCP invoice, sighs, and mutters something about 'the cost of doing business.' Meanwhile, engineers in our Pune community treat that same invoice like a puzzle with ten obvious pieces missing.
This isn't about exotic optimizations or heroics. It's about features Google already built — sitting there, off by default — that our study group members configure in their first week on any new project. Here's the checklist, with the how-to for each.
1. Committed Use Discounts (The Boring One That Pays Most)
If you're running steady-state workloads on Compute Engine and paying on-demand rates, you're donating roughly 37–57% to Google. A one-year commitment on a predictable VM fleet is the closest thing to free money in cloud computing.
Do it this week: In the console, go to Billing → Committed use discounts → Purchase commitment. Start with your longest-running instance types. Even a 50% coverage commitment beats 0%.
2. Spot VMs for Anything Interruptible
Batch jobs, CI runners, render pipelines — none of these care if they get evicted with 30 seconds' notice. Spot VMs run up to 91% cheaper than standard instances.
How: Set scheduling.preemptible: true (or select Spot in the console) on worker node pools. Add retry logic. Done.
3. Autoclass on Cloud Storage
Most buckets hold access logs from 2022 that nobody has opened since. Storage Autoclass automatically moves objects between Standard, Nearline, and Coldline based on actual access patterns.
How: Enable Autoclass on existing buckets via Storage → Bucket → Edit. New buckets: just check the box at creation. No lifecycle rules to babysit.
4. Logging Exclusions Before You Drown
Cloud Logging bills ingestion beyond the free 50 GiB/month. Verbose debug logs from a chatty microservice can blow through that in days.
How: Logging → Log Router → Create exclusion. Exclude health checks, debug-level entries, and load balancer noise. Keep an emergency sink for security-relevant logs.
5. Log Bucket Retention Tuning
Default retention is 30 days — but teams routinely pay for custom 365-day retention on everything. Tier it: 30 days hot, 365 days only for audit logs.
How: Logging → Storage → Edit bucket, set view-level retention policies per log view.
6. Budget Alerts That Actually Fire Early
A budget alert at 100% isn't a budget, it's a postmortem. Set thresholds at 50%, 80%, and 90% with Pub/Sub notifications wired to Slack.
How: Billing → Budgets & alerts. Create per-project budgets, not one giant one.
7. Cloud SQL Idle Instance Detection
Dev and staging databases running 24/7 are a classic leak. Our community members schedule stop/start via Cloud Scheduler — a 15-line Cloud Function that saves hundreds monthly.
How: Enable the Cloud SQL Admin API, deploy a scheduled function calling instances:patch with activation policy ALWAYS/NEVER on a cron.
8. Network Egress Tiering
Premium tier networking is great — for user-facing traffic. Internal batch replication between regions often doesn't need it.
How: Evaluate Standard tier for non-latency-sensitive egress in Network Services → Hybrid Connectivity. Test before you commit.
9. Cloud Armor Preconfigured Rules
DDoS and common exploit traffic burns both compute and egress. Preconfigured WAF rules block the worst of it cheaply.
How: Attach a Cloud Armor security policy to your load balancer with the preconfigured rule sets (SQLi, XSS) in preview mode first, then enforce.
10. Recommender-Driven Rightsizing
GCP literally tells you which VMs are oversized. Most teams never open the email.
How: Compute Engine → Recommender (or Active Assist). Review monthly. Apply the machine type changes during your next deploy window.
The Pattern Behind All Ten
Notice something? None of this requires new architecture, a migration, or a consultant. It's configuration hygiene — the kind our Pune study circles drill into members because most of us learned cloud on constrained budgets, where every rupee of credit had to count.
Pick three items off this list. Enable them Friday afternoon. Then check next month's invoice. The sigh might turn into something closer to a smile.
