Cloud Provider Notes
Published on
Cloud architecture should begin with workload, risk, operational, and economic requirements. Product names differ, but the enduring decisions are organization boundaries, identity, networking, compute, data, observability, recovery, policy, and cost allocation.
| Capability | AWS | Azure | Google Cloud |
|---|---|---|---|
| Organization boundary | Organizations and accounts | Tenant, management groups, subscriptions | Organization, folders, and projects |
| Workforce identity | IAM Identity Center and federation | Microsoft Entra ID | Cloud Identity and federation |
| Virtual network | VPC | Virtual Network | VPC |
| Managed Kubernetes | EKS | AKS | GKE |
| Object storage | S3 | Blob Storage | Cloud Storage |
| Audit events | CloudTrail | Activity Log | Cloud Audit Logs |
The table is a discovery map, not a claim that similarly named services have identical semantics. Evaluate quotas, failure behavior, identity integration, network topology, data guarantees, regional availability, support, and pricing in the specific provider.
Continue with AWS, Azure, Google Cloud, and the Infrastructure Engineering path.
Last updated on