Controlling spend.
WHAT DRIVES COST
Compute running continuously Data processed by analytical queries Egress, or data leaving the platform Storage in the wrong class Resources left running
WHAT THAT LAST ONE IS
The largest avoidable waste, consistently.
WHAT TO SET UP IMMEDIATELY
A budget with alerts Labels on every resource Cost reporting by label and project
WHY LABELS
Without them, nobody can attribute cost to a project or team.
WHAT SAVES SUBSTANTIALLY
Committed use discounts for predictable workloads Scaling to zero where the service supports it Stopping non-production resources outside working hours Appropriate storage classes Deleting what is unused
WHAT TO AUTOMATE
Shutting down development environments.
WHAT TO WATCH SPECIFICALLY
Analytical query cost, which can be very large from a single query Egress charges Services billed per operation at volume
WHAT TO SET AS A SAFEGUARD
Maximum instances on scaling services Maximum bytes billed on queries
WHAT TO REVIEW MONTHLY
The largest items, and anything growing unexpectedly.
WHAT TO ESTABLISH
Who may create expensive resources.
