AWS Nitro Enclaves

An AWS Nitro Enclave is a hardware-isolated virtual machine (VM) created from a parent EC2 instance. It leverages the Nitro Hypervisor to provide a strong security boundary with dedicated CPU and memory that is inaccessible to the parent instance, the host OS, AWS personnel, or other tenants. The enclave has no persistent storage, interactive access, or external networking, eliminating traditional attack vectors. It is designed to run a single-purpose application that processes sensitive data.

This is a critical feature for establishing trust. Before releasing sensitive data or keys to an enclave, an external verifier can request a cryptographically signed attestation document. This document, generated by the Nitro Hypervisor, contains:

• Platform Configuration Registers (PCRs): Hashes that uniquely identify the enclave's identity, including its kernel, application, and IAM role.
• A public key: Generated inside the enclave for secure channel establishment.
• A certificate: Signed by the Nitro Attestation service, proving the document originated from a genuine Nitro Enclave on AWS. This allows clients to cryptographically verify that their data will only be processed by the exact, intended application running in a genuine enclave.

Enclaves have no IP network interfaces. All communication with the parent instance occurs exclusively through a local socket (vsock). This is a secure, memory-based communication channel that functions like a local network socket but operates entirely within the host machine's memory bus. The parent instance acts as a proxy, handling all external network I/O, while the enclave processes data received via vsock. This design enforces a simple, auditable data flow and prevents the enclave from making unauthorized external connections.

An enclave's filesystem is an EIF (Enclave Image File), which is built from a Docker container. This image is cryptographically measured at launch. Key characteristics:

• Immutable: The filesystem is read-only after launch; no changes can be persisted.
• Minimal: The EIF should contain only the application binaries, libraries, and data strictly necessary for its function, reducing the attack surface.
• Measured: The hash of the EIF is included in the attestation document, allowing verifiers to confirm the exact code that is running. This principle ensures the enclave runs a known, verified, and unchangeable software stack.

In the context of Retrieval-Augmented Generation (RAG), Nitro Enclaves enable privacy-preserving retrieval. A sensitive enterprise knowledge base can be encrypted and stored in a standard database (e.g., Amazon S3). The retrieval application runs inside an enclave. The workflow:

1. The enclave is attested to by a client.
2. The client sends an encrypted query.
3. The enclave retrieves encrypted chunks from the database.
4. Using keys delivered via attested KMS calls, it decrypts the data internally, performs semantic search/reranking, and then re-encrypts the relevant context.
5. The encrypted context is sent back to the parent instance to be passed to the LLM. The sensitive source data is never exposed in plaintext to the cloud provider, the host OS, or the LLM service.

A secure, isolated area of a main processor that provides hardware-level protection for code and data. A TEE guarantees confidentiality and integrity even from privileged system software like the operating system or hypervisor. Key implementations include:

• Intel SGX: Creates enclaves within application processes.
• AMD SEV: Encrypts the memory of an entire virtual machine.
• AWS Nitro Enclaves: Provides isolated, constrained VMs with no persistent storage or external networking, built on the Nitro System's hardware root of trust.

A cryptographic protocol that enables multiple parties to jointly compute a function over their private inputs while keeping those inputs concealed. It reveals only the final output. Common techniques include Garbled Circuits and Secret Sharing. Unlike a TEE like Nitro Enclaves, which relies on hardware isolation for a single party's data, MPC is a cryptographic solution for collaborative computation between mutually distrusting parties without a trusted third party.

A rigorous mathematical framework for quantifying and limiting privacy loss. It ensures that the output of an algorithm does not reveal whether any specific individual's data was in the input dataset. This is achieved by carefully injecting statistical noise, often via the Laplace Mechanism or Gaussian Mechanism. While Nitro Enclaves protects data during processing, differential privacy protects the outputs of that processing, making them safe to release. They are often used in tandem for end-to-end privacy guarantees.