AWS Nitro Enclaves - Bryant McGill

# AWS Nitro Enclaves **Aliases:** Nitro enclave administrator; Nitro Enclaves **Entity class:** Confidential hosting **Integration priority:** P1 **Collections:** [[collections/Consciousness Continuity|Consciousness Continuity]] · [[collections/Neurotech|Neurotech]] · [[collections/Machine Succession|Machine Succession]] **Canonical source article:** [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]] ## Definition **AWS Nitro Enclaves** — Splits host lifecycle administration from access to resident secrets/data. ## Relationships  This entry is routed through [[collections/Consciousness Continuity|Consciousness Continuity]], [[collections/Neurotech|Neurotech]], and [[collections/Machine Succession|Machine Succession]]. Its source context is developed in [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]] and [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]]. Status-qualified source edges are preserved in the terminal Research Edges section. ### Key Relationships - **AWS Nitro Enclaves** is associated with vCPU and memory from parent instance. Parent root/admin cannot access enclave data/apps. - **AWS Nitro Enclaves** is associated with persistent storage. Explicit property. - **AWS Nitro Enclaves** is associated with SSH access. Explicit property. - **AWS Nitro Enclaves** is associated with external networking. Explicit property. ### Technology and research relationships - **AWS Nitro Enclaves** supports cryptographic attestation. Measured enclave identity. ### Connections in this corpus - **AWS Nitro Enclaves** is connected in the corpus with [[wiki/Residual Sovereign|Residual Sovereign]]. Resident state can be cryptographically withheld from infrastructure admins while still depending on host lifecycle. - **AWS Nitro Enclaves** is connected in the corpus with [[wiki/Substrate Administrator|Substrate Administrator]]. Shows a possible separation between operational administrator and data visibility. - **AWS Nitro Enclaves** is connected in the corpus with [[wiki/Continuity Custody|Continuity Custody]]. Custody can be split: host controls lifecycle while key owner controls decryption. ### Additional Documented Relationships - The technical comparison identifies a convergence: **AWS Nitro Enclaves** converges technically with [[wiki/Ring Zero|Ring Zero]]. Attested code measurement can gate secret release. - The technical comparison identifies a convergence: **AWS Nitro Enclaves** is connected in the corpus with [[wiki/Root of Trust Succession|Root of Trust Succession]]. AWS root-of-trust signs attestation. exposing dependence on external trust anchor. - The technical comparison identifies a convergence: **AWS Nitro Enclaves** converges technically with [[wiki/Platform Custody|Platform Custody]]. Concrete design showing host operator can be denied visibility into resident data. but still controls lifecycle.  ## Related Work in the Corpus  - In [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]], **XVII. The landlord problem** provides the narrative context for **AWS Nitro Enclaves**: Confidential-computing systems such as AWS Nitro Enclaves show that this power can be decomposed.  ## Research Edges  #### Host–residual infrastructure patch — 2026-09-10 **Resolved aliases:** `Nitro enclave administrator`, `Nitro Enclaves` **Collections:** [[collections/Consciousness Continuity|Consciousness Continuity]] · [[collections/Neurotech|Neurotech]] · [[collections/Machine Succession|Machine Succession]] **Canonical source article:** [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]] **Related acquisition source:** [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] **Relationship source:** [[research/Mind Uploading and AI Host-Residual Ecosystem Relationship Graph - 2026-09-10|Mind Uploading and AI Host-Residual Ecosystem Relationship Graph — 2026-09-10]] #### Host-infrastructure integration Splits host lifecycle administration from access to resident secrets/data. #### Outgoing typed edges - **HR-0144 — `isolates` → `vCPU and memory from parent instance`** — **VERIFIED EXTERNAL**; evidence `WEB_NITRO_SECURITY`. Parent root/admin cannot access enclave data/apps. - **HR-0145 — `has_no` → `persistent storage`** — **VERIFIED EXTERNAL**; evidence `WEB_NITRO_SECURITY`. Explicit property. - **HR-0146 — `has_no` → `SSH access`** — **VERIFIED EXTERNAL**; evidence `WEB_NITRO_SECURITY`. Explicit property. - **HR-0147 — `has_no` → `external networking`** — **VERIFIED EXTERNAL**; evidence `WEB_NITRO_SECURITY`. Explicit property. - **HR-0148 — `supports` → `cryptographic attestation`** — **VERIFIED EXTERNAL**; evidence `WEB_NITRO_SECURITY`, `WEB_NITRO_KMS`. Measured enclave identity. - **HR-0150 — `can_control` → `enclave lifecycle`** — **VERIFIED EXTERNAL**; evidence `WEB_NITRO_FLOW`. Parent admin launches/controls lifecycle while ideally lacking key-decrypt authority. - **HR-0151 — `technical_convergence_with` → [[wiki/Platform Custody|Platform Custody]]** — **STRONG ANALYTIC CONVERGENCE**; evidence `WEB_NITRO_SECURITY`, `WEB_NITRO_FLOW`, `WIKI_ARCHIVE`. Concrete design showing host operator can be denied visibility into resident data, but still controls lifecycle. - **HR-0152 — `technical_convergence_with` → [[wiki/Ring Zero|Ring Zero]]** — **ANALYTIC CONVERGENCE**; evidence `WEB_NITRO_KMS`, `WIKI_ARCHIVE`. Attested code measurement can gate secret release. - **HR-0153 — `cross_threads` → [[wiki/Root of Trust Succession|Root of Trust Succession]]** — **ANALYTIC CONVERGENCE**; evidence `WEB_NITRO_KMS`, `WIKI_ARCHIVE`. AWS root-of-trust signs attestation, exposing dependence on external trust anchor. - **HR-1397 — `cross_threads` → [[wiki/Residual Sovereign|Residual Sovereign]]** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Resident state can be cryptographically withheld from infrastructure admins while still depending on host lifecycle. - **HR-1398 — `cross_threads` → [[wiki/Substrate Administrator|Substrate Administrator]]** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Shows a possible separation between operational administrator and data visibility. - **HR-1399 — `cross_threads` → [[wiki/Continuity Custody|Continuity Custody]]** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Custody can be split: host controls lifecycle while key owner controls decryption.