One of the best pieces of news for beginners: even if you choose AWS, you’re not just learning AWS. Most of what you learn are universal concepts that exist, under different names, in Azure, Google Cloud, and any other cloud. This subchapter gives you that “translation map” so your knowledge is portable.

Clouds solve the same problems, so they offer the same types of services. What changes is the brand name and some details. If you understand the concept, the name doesn’t matter.

Analogy: “Cola soft drink” is a concept. Coca-Cola and Pepsi are different brands of the same concept. Learning what a cola soft drink is helps you recognize both brands.

This table translates the most important services among the big three. It will be useful throughout this book and your entire career:

You don’t need to memorize it now. Come back to it when you need it.

Beyond the names, there are fundamental ideas that are identical in all clouds. These are what really matter to understand:

All clouds divide the world into geographic regions, and each region into independent zones to tolerate failures. We’ll see this in Chapter 3. AWS calls them Regions and Availability Zones; Azure and GCP use almost identical names.

In all clouds, the provider protects the infrastructure and you protect what you put on top (your data, your configurations, your permissions). We’ll cover this in depth in Chapter 7 and Part VI. This division of responsibilities is identical across all providers.

All use the principle of giving only the necessary permissions to each user or service. The service has a different name (IAM, Entra ID, Cloud IAM) but the philosophy is the same.

The five NIST pillars from Chapter 1 apply equally to all clouds.

You can define your infrastructure in text files in any cloud. And here Terraform shines: with a single language you manage AWS, Azure, or GCP. This is what makes your Terraform learning (Part III) fully portable between providers.

• Your learning doesn’t expire: if you change jobs tomorrow and they use Azure, you already know 80% of the concepts. You’ll just have to learn the new names.
• You understand the “why,” not just the “how”: memorizing clicks is forgettable; understanding concepts sticks.
• You make better decisions: you recognize common patterns and know what to look for in any provider.

Real example: An engineer learns AWS in depth. She moves to a company that uses GCP. In her first week she’s already productive, because “Compute Engine is like EC2,” “Cloud Storage is like S3,” and “Cloud IAM is like IAM.” She just had to adjust names and details, not relearn from scratch.

• Clouds offer the same concepts with different names; the equivalency table is your cheat sheet.
• What really matters are the universal concepts: regions and zones, shared responsibility, identity and least privilege, pay-as-you-go and elasticity, and Infrastructure as Code.
• Learning AWS in depth gives you a foundation that transfers to any other cloud.
• Terraform takes this portability to the max: one language to manage any provider.

With this, we close Chapter 2. In Chapter 3 we’ll dive into one of those key universal concepts: regions, availability zones, and edge locations, the foundation of global availability and resilience.