~$ man cloud-rosetta
cloud-rosetta — translate managed-service names between AWS, Azure, and Google Cloud
Every cloud sells roughly the same forty things. None of them call any of those things the same name. You say Lambda, your Azure colleague hears Functions, and your GCP colleague hears whatever Google is calling it this quarter.
This page is the translation layer. Type a service name below — in any cloud's dialect, including retired names like Stackdriver or Azure AD — and find out what everyone else calls it. Because most of us live in one vertical, and the meeting invite says "multi-cloud".
Names services like a warehouse inventory: literal acronyms (EC2, S3), honest labels (Simple Queue Service), and the occasional word that means nothing (Fargate). There's an official rule for when it's "Amazon X" vs "AWS X". Nobody can recite it.
Puts "Azure" in front of a noun and ships it. Clear and searchable — until the noun itself gets rebranded (Active Directory → Entra ID, Stack HCI → Local). Bonus level: some products are now "Microsoft X" instead, and no one will tell you which.
The cleanest names in the business: Compute Engine, Cloud Storage, BigQuery. Read the docs quickly though — every name is one product-strategy review away from a rename (Stackdriver → Cloud Monitoring, Cloud Functions → Cloud Run functions).
Mappings are "closest everyday equivalent", not a feature-for-feature guarantee — the services differ in real ways once you're past the name. Names were verified against vendor docs in July 2026. Clouds rename things for sport; when money is involved, check the official documentation.
By the time you read this, at least one of these products has probably been renamed, "unified", or folded into a Copilot. This is not a bug in the page. It is a bug in the industry.
vibes(7) — back to the index of experiments · akhan.me(1) — back to home