Home/Start here/The four clouds side by side
The four clouds side by side
Every cloud has the same handful of building blocks under different names. Learn the mapping once and the other three stop feeling foreign.
How each cloud is organised
Each cloud has a top level for the whole organisation, one or more grouping levels, and a level where resources actually sit. Most permissions and policies attach at that last level, which is why it is the one to learn first.
| AWS | Azure | Google Cloud | Oracle Cloud | |
|---|---|---|---|---|
| Top level | Organization | Tenant | Organization | Tenancy |
| Grouping | Organizational unit | Management group | Folder | Compartment |
| Where resources live | Account | Resource group, inside a subscription | Project | Compartment |
| The ID you paste most | 12-digit account ID | Subscription ID, a GUID | Project ID, a name you chose | OCID, a long string starting ocid1. |
The same building blocks
| AWS | Azure | Google Cloud | Oracle Cloud | |
|---|---|---|---|---|
| Audit log | CloudTrail | Activity Log | Cloud Audit Logs | Audit |
| Kept by default | 90 days of management events | 90 days | 400 days of Admin Activity, unchangeable | 365 days, unchangeable |
| Object storage | S3 | Blob Storage | Cloud Storage | Object Storage |
| Write-once lock | Object Lock | Immutability policy | Retention policy, lockable | Retention rule, lockable |
| Your own keys | KMS | Key Vault | Cloud KMS | Vault |
| Command line | aws | az | gcloud | oci |
| Terraform provider | hashicorp/aws | hashicorp/azurerm | hashicorp/google | oracle/oci |
The default retention row is why the audit log template exists on all four. Each cloud keeps something on its own, and in each case the copy you control can last longer and sits outside the reach of whoever can change the default.
How Terraform signs in to each
Terraform uses whatever the cloud's own command line tool has already set up. Sign in with the tool first, then run Terraform in the same terminal.
| Cloud | Run once | What Terraform reads |
|---|---|---|
| AWS | aws configure sso or aws configure | The profile in AWS_PROFILE, or the default one |
| Azure | az login | The CLI sign-in, plus ARM_SUBSCRIPTION_ID, which the provider has required since version 4 |
| Google Cloud | gcloud auth application-default login | Application default credentials. A plain gcloud auth login is a different thing and Terraform will not see it |
| Oracle Cloud | oci setup config | The DEFAULT profile in ~/.oci/config, including the API key and region |
On Google Cloud, gcloud auth login signs in the command line tool, and
Terraform ignores it. The command Terraform needs has
application-default in it.
On Azure, the provider stopped guessing the subscription in version 4, and version 5 keeps it that way. Without
ARM_SUBSCRIPTION_ID or a subscription_id in the provider
block, the first plan fails.
One result, four ways
The same template, audit logs nobody can delete, built on each cloud. The idea is identical. The plumbing and the trap are different every time.
| AWS | Azure | Google Cloud | Oracle Cloud | |
|---|---|---|---|---|
| What copies the logs | The trail itself | A diagnostic setting | A log sink | A Connector Hub connector |
| First file appears | Within about 15 minutes | Within the hour, one file per hour | Within the hour, in hourly batches | Within a few minutes |
| What the lock applies to | Each stored version | The container | The bucket | The bucket |
| The trap | A plain delete succeeds by adding a delete marker | The container name, and appends | The sink's own identity needs write access | Locking has to be scheduled 14 days ahead |
Words that change meaning between clouds
Role. In AWS a role is an identity: something you become for a
while, with its own permissions. In Azure and Google Cloud a role is a named list of
permissions that you grant to someone. Oracle Cloud has no roles at all. Permissions
are written as sentences in a policy, such as Allow group auditors to read
audit-events in tenancy.
Project. In Google Cloud a project is where resources live and what you are billed against. Azure and AWS use the word for nothing in particular.
Namespace. In Oracle Cloud it is the one fixed string that prefixes every bucket address in your tenancy. In Kubernetes it is a folder for objects inside a cluster. The two have nothing to do with each other.
Tenant. In Azure the tenant is your Entra ID directory, which sits above every subscription. In Oracle Cloud the tenancy is your whole account. Close in spirit, different in what they contain.
One cloud at a time
Each platform page lists everything this site has for one cloud: templates, lessons, refreshers, and the log planner.