AWS, GCP, and Azure: Service-by-Service Mapping for Architects

Once you understand why each hyperscaler exists, you still need a Rosetta stone for what to provision. This reference maps core categories—compute through AI—to their AWS, Google Cloud, and Azure equivalents, with notes on when the match is close versus approximate.

In short

Most building blocks have a parallel on all three clouds; names and defaults differ. Prefer portable patterns (Kubernetes, Postgres, S3-compatible APIs) where exit matters; embrace managed proprietary services where they buy clear operational wins.

Read Part 1: depth comparison for philosophy, enterprise fit, and selection criteria. Tables use current product names—verify in official docs before exams or procurement.

Compute

CapabilityAWSGCPAzure
Virtual machinesEC2Compute EngineVirtual Machines
Auto scaling groupsAuto Scaling + EC2MIG (Managed Instance Groups)VM Scale Sets
Spot / preemptibleEC2 SpotSpot VMs / PreemptibleSpot VMs
Serverless functionsLambdaCloud FunctionsAzure Functions
Container platform (managed)ECS, FargateCloud RunContainer Apps
KubernetesEKSGKEAKS
PaaS (code deploy)Elastic Beanstalk, App RunnerApp EngineApp Service
Batch / HPCAWS BatchBatchAzure Batch

Notes: GKE is often cited as the most integrated Kubernetes experience; AKS simplifies Windows node pools; EKS has the largest third-party add-on ecosystem. Fargate and Cloud Run both abstract nodes but differ in pricing and networking models.

Networking

CapabilityAWSGCPAzure
Virtual networkVPCVPCVirtual Network (VNet)
SubnetsSubnet (per AZ)Subnet (regional)Subnet
Load balancer (L4/L7)ELB (ALB/NLB/CLB)Cloud Load BalancingLoad Balancer, App Gateway
CDNCloudFrontCloud CDNAzure CDN / Front Door
DNSRoute 53Cloud DNSAzure DNS
Private connectivityPrivateLink, VPC endpointsPrivate Service ConnectPrivate Link
VPN / dedicated lineSite-to-Site VPN, Direct ConnectCloud VPN, Cloud InterconnectVPN Gateway, ExpressRoute
Firewall / WAFWAF, Network Firewall, ShieldCloud Armor, Cloud NGFWWAF, Firewall, DDoS Protection
API gatewayAPI GatewayAPI GatewayAPI Management

GCP subnets are regional (one CIDR spans zones); AWS subnets are AZ-scoped. Azure Front Door is a global entry point comparable to CloudFront plus routing intelligence. For landing-zone design on AWS, see network architecture.

Storage

CapabilityAWSGCPAzure
Object storageS3Cloud StorageBlob Storage
Block volumesEBSPersistent DiskManaged Disks
File / NASEFS, FSxFilestoreAzure Files
Archive / coldS3 GlacierArchive / ColdlineArchive / Cool tier
Hybrid transferStorage Gateway, SnowballTransfer ApplianceData Box
Backup serviceAWS BackupBackup and DRAzure Backup

S3 remains the de facto API reference; many tools speak S3-compatible protocols to GCS and Blob via adapters. For Kubernetes volumes, compare PV, PVC, and StorageClass with each cloud’s CSI drivers.

Databases and caching

CapabilityAWSGCPAzure
Managed PostgreSQLRDS, Aurora PostgreSQLCloud SQL, AlloyDBAzure Database for PostgreSQL
Managed MySQLRDS, Aurora MySQLCloud SQLAzure Database for MySQL
Managed SQL ServerRDS SQL ServerCloud SQL SQL ServerAzure SQL
Global SQL / NewSQLAurora GlobalCloud SpannerAzure SQL (geo-replication)
NoSQL documentDynamoDBFirestoreCosmos DB
Wide-columnKeyspaces (Cassandra)BigtableCassandra on Cosmos / VMs
In-memory cacheElastiCache (Redis/Memcached)MemorystoreAzure Cache for Redis
Data warehouseRedshiftBigQuerySynapse Analytics
SearchOpenSearch ServiceElastic (partner) / self-managedAzure AI Search

Approximate matches: DynamoDB and Cosmos DB both offer low-latency scale but different consistency models and APIs. BigQuery and Redshift both serve analytics; BigQuery separates storage and compute more aggressively. AlloyDB targets PostgreSQL-compatible OLTP with Google-scale replication.

Identity, access, and secrets

CapabilityAWSGCPAzure
Core IAMIAM (users, roles, policies)Cloud IAMAzure RBAC + Entra ID
Organization hierarchyOrganizations, SCPsOrganization policiesManagement groups, Azure Policy
Federation / SSOIAM Identity CenterWorkforce Identity FederationEntra ID SSO
Workload identityIAM roles for service accountsWorkload IdentityManaged identities
SecretsSecrets Manager, SSM Parameter StoreSecret ManagerKey Vault
KMS / encryption keysKMSCloud KMSKey Vault keys
Directory / B2CCognitoIdentity PlatformEntra External ID

AWS policy JSON is its own language—see IAM policy anatomy. Azure RBAC is role-based at resource scope; GCP IAM binds roles to principals on resources.

Messaging, events, and integration

CapabilityAWSGCPAzure
Pub/subSNS + SQS (patterns)Pub/SubService Bus, Event Grid
QueueSQSPub/Sub subscriptionsService Bus queues
Event busEventBridgeEventarcEvent Grid
StreamingKinesis Data StreamsPub/Sub, DataflowEvent Hubs
Workflow orchestrationStep FunctionsWorkflowsLogic Apps, Durable Functions
ETL / integrationGlue, AppFlowDataflow, Data FusionData Factory

Observability and operations

CapabilityAWSGCPAzure
Metrics & dashboardsCloudWatchCloud MonitoringAzure Monitor
LoggingCloudWatch LogsCloud LoggingLog Analytics
TracingX-RayCloud TraceApplication Insights
AlertingCloudWatch AlarmsAlerting policiesMonitor alerts
Infrastructure as codeCloudFormation, CDKDeployment Manager, TerraformBicep, ARM, Terraform
CI/CDCodePipeline, CodeBuildCloud BuildAzure DevOps, GitHub Actions

OpenTelemetry is portable across all three; managed backends differ.

Security and governance

CapabilityAWSGCPAzure
Posture / CSPMSecurity Hub, ConfigSecurity Command CenterDefender for Cloud
Threat detectionGuardDutyEvent Threat DetectionDefender for Cloud
Vulnerability scanningInspectorContainer AnalysisDefender vulnerability mgmt
Policy as codeSCPs, Access AnalyzerOrg PolicyAzure Policy
HSMCloudHSMCloud HSMDedicated HSM

Shared responsibility applies everywhere—see cloud security foundations.

AI, ML, and data science

CapabilityAWSGCPAzure
Managed notebooksSageMaker StudioVertex AI WorkbenchAzure ML compute instances
Training / MLOpsSageMakerVertex AIAzure Machine Learning
Foundation model APIsBedrockVertex AI (Gemini)Azure OpenAI Service
Speech / vision APIsRekognition, TranscribeVision, Speech APIsAzure AI services

See ML foundations and generative AI for AWS depth; Vertex and Azure OpenAI are the usual GCP/Azure starting points for GenAI.

DevOps, registry, and artifacts

CapabilityAWSGCPAzure
Container registryECRArtifact RegistryACR
Package / artifact repoCodeArtifactArtifact RegistryArtifacts (Azure DevOps)
Configuration managementSystems ManagerOS ConfigAutomation, Guest Config

How to use this mapping in practice

  1. Start with capability, not logo. Define the job (regional SQL, global NoSQL, batch ETL) then pick the row.
  2. Check region availability for your short list before design sign-off.
  3. Prototype pricing with each provider’s calculator using your traffic shape.
  4. Prefer open interfaces where teams may switch clouds: Postgres, Kafka protocol, S3 API, Kubernetes, OpenTelemetry.
  5. Document exceptions where you accept lock-in (DynamoDB access patterns, BigQuery SQL, Entra conditional access).

Further reading

  • AWS, Google Cloud, and Microsoft Learn — official documentation and learning paths
  • Each provider’s architecture center and reference architectures
  • AWS data engineering — pipelines and lakes on AWS (patterns often translate)

Blog index · Part 1: Depth comparison · Cloud platform evolution

Back to blog list