hyperscaler-framing-responsibility-identity-and-hierarchylisted

# AWS, GCP and Azure: The Honest Framing, Shared Responsibility, Identity and Access, and Resource Hierarchy > **Part 1 of 5** of the *AWS, GCP and Azure Deep Dive* reference (plugin `aws-gcp-azure-deep-dive`), covering §0–§4. Sibling skills: `hyperscaler-networking-compute-containers-and-serverless` (§5–§8), `hyperscaler-storage-databases-analytics-and-observability` (§9–§13), `hyperscaler-cost-reliability-iac-lock-in-and-migration` (§14–§18), `hyperscaler-reference` (§19–§26). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill. > > **Currency:** Architecture and IAM models are stable. Two areas moved. See §21 → `hyperscaler-reference` for egress pricing under the EU Data Act switching regime, and the AI-driven shift in market position. > **⚠️ Scope.** Assumes you know what cloud computing *is*. This is **the comparative > layer**: where the three genuinely differ, and where the differences bite. > Complements a cloud-computing reference (general concepts), a Linux server admin > reference (what runs on the instances), and an IT infrastructure/governance reference > (identity governance, RBAC theory, on-prem). > > **⚠️ GOTCHA** boxes mark things that cause outages or surprise bills. > > **The three ideas that organize everything below:** > 1. **⚠️ The three clouds are not interchangeable, and the service feature lists are the > least important difference.** **What actually differs is the identity model, the >