Anatomy of a multi-cloud deploy that failsFriday, 6:10pm. The terraform plan says "12 to add, 3 to change, 1 to destroy". You read it, nothing looks odd. Apply. Green bar. You get up for a coffee and when you come back the alerts channel has 13h ago · 5 min readcontrolcloud.hashnode.dev
BYO credentials: why your control plane should never ask for master keysYou sign up for a new tool to see your infrastructure in one place. First onboarding step: "Connect your cloud". And the form asks for the tenancy's admin API key. The master one. The one that can cre13h ago · 4 min readcontrolcloud.hashnode.dev
Operating windows in non-prod: governance with an audit log vs scattered cron scriptsThe arithmetic is easy: a QA environment that runs 24/7 but is only used from 9 to 7, Monday to Friday, is powered on three times longer than it needs to be. Shutting it down outside those hours can c13h ago · 4 min readcontrolcloud.hashnode.dev
Generated vs hand-written Terraform: when to choose eachYou inherited an account with 300 resources created by hand over three years, and you were asked to "put it in Terraform". You have two paths: generate the code automatically from the infrastructure t13h ago · 3 min readcontrolcloud.hashnode.dev
Unused public IPs: what AWS and GCP charge and how to find themA public IP looks free because it has no CPU and no disk. It is not. Since February 1, 2024, AWS bills USD 0.005 per hour for every public IPv4 address, whether it is attached to a resource or not. Th16h ago · 5 min readcontrolcloud.hashnode.dev
