Security

Confidential Computing - Isolating and Protecting Data in Use with AWS Nitro Enclaves

Learn about isolated processing of sensitive data using AWS Nitro Enclaves. Covers cryptographic attestation, KMS integration, and use cases for PII processing and encryption key management.

約 4 分で読めます

The Need for Confidential Computing

In traditional security models, data protection has been achieved through encryption at rest and in transit. However, when processing data, it must be decrypted and loaded into memory, making this "data in use" a target for attacks. Vulnerabilities in the OS or hypervisor, memory dumps, and side-channel attacks can lead to data-in-use leakage. AWS Nitro Enclaves, available on Nitro-based EC2 instances (C5, M5, R5 and later), is a confidential computing service that creates fully isolated virtual machines (Enclaves) within an EC2 instance, executing sensitive data processing in an environment inaccessible from outside. Enclaves are completely isolated from the parent instance by the Nitro Hypervisor, with no network connectivity, persistent storage, SSH access, or external memory access. No one, including AWS operators, can access data inside the Enclave.

How Enclaves Work and Attestation

An Enclave is created by partitioning a portion of the parent EC2 instance's vCPUs (up to half of the parent) and memory. Communication with the parent instance is limited to vsock (virtual socket) only; TCP/IP networking cannot be used. Applications are deployed to the Enclave as Docker images and launched with the Nitro CLI. Cryptographic attestation is a mechanism for verifying Enclave integrity. When an Enclave starts, the Nitro Hypervisor generates an attestation document containing hash values of the Enclave's image (code, configuration). This document is signed by the AWS Nitro Attestation PKI, cryptographically proving that the Enclave has not been tampered with. KMS can verify the attestation document and apply encryption key policies that allow decryption only by a specific Enclave image.

Use Cases and KMS Integration

The primary use case for Nitro Enclaves is PII (Personally Identifiable Information) processing. By processing medical data, financial data, and personal identification information within the Enclave and returning only aggregated results to the parent instance, you eliminate the risk of raw data leakage. For encryption key management, keys are generated and used within the Enclave as an alternative to CloudHSM, ensuring keys never leave the Enclave. With KMS integration, you set the Enclave's image hash (PCR values) as conditions in KMS key policies. This ensures that KMS keys can only be used by a specific Enclave running specific code, making KMS key access impossible even if the parent instance is compromised. For multi-party computation, multiple organizations can send their data to the Enclave, perform joint computation within the Enclave, and return only the results. There are no additional charges; only the EC2 instance pricing applies. For comprehensive learning on Nitro Enclaves best practices, refer to technical books (Amazon).

Nitro Enclaves Pricing

Nitro Enclaves itself incurs no additional charges. The cost is that the parent instance's resources are reduced by the vCPUs and memory allocated to the Enclave. For example, if you allocate 2 vCPUs and 8 GB to an Enclave on an m5.2xlarge (8 vCPU, 32 GB), the parent instance operates with 6 vCPUs and 24 GB. If you need to select a larger instance for the Enclave, the difference in instance pricing is the effective cost. KMS key charges ($1/month per key) used with KMS integration also apply.

Summary - Nitro Enclaves Usage Guidelines

AWS Nitro Enclaves is a confidential computing service that fully isolates and protects data in use. Its key strengths are isolation by the Nitro Hypervisor, cryptographic attestation, and encryption key protection through KMS integration. It is suitable for use cases where protection of data in use is required by regulations or security policies, such as PII processing, encryption key management, and multi-party computation. Available at no additional charge, it can be adopted by adding Enclaves to existing EC2 workloads.

Related Services

AWS Nitro EnclavesA service that creates isolated execution environments within EC2 instances for securely processing sensitive dataAmazon EC2A compute service that provides virtual servers in the cloudAWS KMSA managed encryption key service for securely creating and managing keys used to encrypt data

Related Articles

Hardware Security Modules - Dedicated Cryptographic Key Management with AWS CloudHSMLearn about dedicated cryptographic key management with AWS CloudHSM. Covers when to choose CloudHSM over KMS, FIPS 140-2 Level 3 compliance, TLS offloading, and Oracle TDE integration.Data Privacy Protection - Automated Sensitive Data Discovery and Threat Defense with Amazon Macie and GuardDutyLearn practical data privacy protection techniques combining Amazon Macie's automated sensitive data discovery in S3 with Amazon GuardDuty's threat intelligence. This article covers comprehensive security measures from identifying personal information to real-time threat detection.Confidential Data Processing with AWS Nitro Enclaves - Encryption and Attestation in an Isolated EnvironmentLearn how to process sensitive data in the isolated environment of Nitro Enclaves, and control encryption key access through KMS integration and attestation.

More on This Topic

Detecting Excessive Permissions with IAM Access Analyzer - External Access and Unused Permission AnalysisDetect unused permissions on IAM roles using CloudTrail-based analysis and auto-generate least-privilege policies. This guide covers external access detection and integrating custom policy checks into your CI/CD pipeline.Automating SSL/TLS Certificate Management with AWS Certificate Manager - From Issuance to RotationLearn how ACM handles free public certificate issuance, DNS validation, automatic renewal, and deployment to ALB and CloudFront.Retrieving Compliance Reports with AWS Artifact - Audit Response and Agreement ManagementLearn how to retrieve SOC, PCI DSS, and ISO audit reports on demand and apply BAA and GDPR DPA agreements across your entire AWS Organizations structure.Automating Audits - Continuously Collecting Compliance Evidence with AWS Audit ManagerLearn how to automate audit evidence collection with AWS Audit Manager. This guide covers automated assessments based on frameworks such as SOC 2, PCI DSS, and GDPR, centralized evidence management, and audit report generation.The Hidden Structure of AWS Account IDs' 12 Digits - Why 12 Digits, and What Can You Infer?A trivia-style exploration of why AWS account IDs are 12-digit numbers, the design intent embedded in the ARN structure, and the security considerations around what can be inferred from an account ID.Why the AWS Account Root User Is Dangerous - The Design Philosophy of Privilege Separation and Practical LockdownWe explain why the AWS root user holds privileges that cannot be restricted by IAM, list the operations only the root user can perform, cover MFA setup methods, and describe the lockdown strategy using Organizations' centralized root access management.Certificate Management and HTTPS - Automated TLS Certificate Operations with AWS Certificate ManagerLearn about TLS/SSL certificate issuance, automatic renewal, and deployment using AWS Certificate Manager (ACM). Covers integration with CloudFront, ALB, and API Gateway, DNS validation, and Private CA usage.Dedicated Key Management with AWS CloudHSM - FIPS 140-2 Level 3 Compliant EncryptionAchieve FIPS 140-2 Level 3 compliant key management with dedicated HSM instances. Learn when to choose CloudHSM over KMS and how to integrate both through KMS custom key stores.

Similar Articles and Services

Confidential Data Processing with AWS Nitro Enclaves - Encryption and Attestation in an Isolated EnvironmentLearn how to process sensitive data in the isolated environment of Nitro Enclaves, and control encryption key access through KMS integration and attestation.AWS Encryption and Data Sovereignty - Hardware-Level Isolation from KMS to Nitro EnclavesWe explain hardware-level encryption and data sovereignty assurance through AWS KMS, CloudHSM, and Nitro Enclaves, and compare design differences with other cloud providers.How the Nitro System Transformed EC2 - From Xen to KVM, Eliminating Virtualization OverheadLearn about the technical background behind EC2's migration from the Xen hypervisor to the Nitro System, the three-layer architecture of Nitro Cards, Nitro Hypervisor, and Nitro Enclaves, and the design philosophy that achieved bare-metal-level performance.AWS Nitro System Hardware Innovation - How Custom Chips Redefined Virtualization and SecurityThis article explains the design philosophy behind the AWS-developed Nitro System, analyzing how the elimination of virtualization overhead, hardware-level security isolation, and bare-metal performance create competitive advantages unavailable from other providers.