Session
Setting Hard Caps to Limit Your Google Cloud Spend
For years, Google Cloud budget alerts were purely informational. They sent an email while your project quietly burned through your savings. But recently, Google has introduced native Cloud Spend Caps (currently in Public Preview). You can now hard-cap spend per service so an unexpected API leak or runaway script hits a 403 Permission Denied wall instead of creating a $10,000 bill.
Here I'll demonstrate how to configure it and protect your own projects from runaway spend.
Darren "Dazbo" Lester
Cloud architect, leader, Google Cloud & AI evangelist, and technology blogger. Known to the community as Dazbo.
London, United Kingdom
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top