During an incident, nobody searches by architecture diagram. They search by name. A gateway called gw-prod-2 in one cloud, a route table called main in another, and a firewall policy copied from a tutorial in a third will each make sense to the person who created them and to nobody else on the call. By the time the team has opened three consoles and translated three local naming habits, the outage has had a head start.
Naming feels like housekeeping until the estate spans AWS, Azure, Google Cloud, and Oracle at once. Then it becomes part of the incident response system itself. A good scheme lets any engineer, in any cloud, answer three questions from a name alone: what is this, where does it live, and what depends on it.
Why local naming habits break across clouds
Each cloud encourages a different default. Resource groups imply one grouping in Azure, projects imply another in Google Cloud, and accounts and VPCs carve AWS differently again.…