implementing-aws-nitro-enclave-security

Featured

Implements AWS Nitro Enclave-based confidential computing environments with cryptographic attestation, KMS policy integration using PCR-based condition keys, and secure vsock communication channels. The practitioner builds enclave images, configures attestation-aware KMS policies, validates attestation documents against the AWS Nitro PKI root of trust, and establishes isolated computation pipelines for processing sensitive data such as PII, cryptographic keys, and healthcare records. Activates for requests involving Nitro Enclave setup, enclave attestation validation, confidential computing on AWS, or KMS enclave policy configuration.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Implementing AWS Nitro Enclave Security ## When to Use - Processing sensitive data (PII, PHI, financial records, cryptographic secrets) that must be isolated from EC2 instance operators and administrators - Building confidential computing pipelines where even root-level access on the parent instance cannot read enclave memory or state - Implementing cryptographic attestation workflows that tie KMS decryption rights to a specific, verified enclave image hash - Deploying multi-party computation environments where two or more enclaves authenticate each other via attestation before exchanging data - Hardening existing workloads that currently decrypt secrets on the parent instance by migrating decryption into an enclave boundary **Do not use** when the workload does not handle sensitive data that requires hardware-level isolation, when the instance type does not support Nitro Enclaves (requires Nitro-based instances with at least 4 vCPUs), or when latency constraints make the vsock communication overhead unacceptable. ## Prerequisites - An AWS account with permissions to launch Nitro-capable EC2 instances (m5.xlarge or larger, C5, R5, M6i families) - AWS CLI v2 and the `nitro-cli` toolset installed on the parent EC2 instance (Amazon Linux 2 or AL2023) - Docker installed on the parent instance for building enclave image files (EIF) - An AWS KMS symmetric key with key policy permissions for the enclave's IAM role - The `aws-nitro-enclaves-sdk-c` or Python `aws-encryption-sdk...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

implementing-envelope-encryption-with-aws-kms

Envelope encryption is a strategy where data is encrypted with a data encryption key (DEK), and the DEK itself is encrypted with a master key (KEK) managed by AWS KMS. This approach allows encrypting

36,355 Updated 2 months ago
mukul975
DevOps & Infrastructure Listed

aws-cloudformation-security

Provides AWS CloudFormation patterns for security infrastructure including KMS encryption, Secrets Manager, IAM security, VPC security, ACM certificates, parameter security, outputs, and secure cross-stack references. Use when implementing security best practices, encrypting data, managing secrets, applying least privilege IAM policies, securing VPC configurations, managing TLS/SSL certificates, and implementing defense in depth strategies.

372 Updated 2 months ago
giuseppe-trisciuoglio
Code & Development Listed

sota-confidential-computing

State-of-the-art confidential computing and cryptographic PETs (2026) for BUILDING and AUDITING systems that protect workloads and data in use from the infrastructure they run on — the inverse of sandboxing. Covers TEE selection (AMD SEV-SNP, Intel TDX, ARM CCA realms, SGX enclaves, AWS Nitro Enclaves, NVIDIA confidential GPUs), memory encryption vs attested isolation (TME/TME-MK/MKTME), remote attestation (RATS RFC 9334, evidence appraisal, attest-then-release, RA-TLS, TCB recovery), confidential VMs/nodes/pods on Kubernetes (Confidential Containers/CoCo, Kata, Trustee KBS), and computing on encrypted data without hardware trust — FHE, MPC/threshold, ZKP, PSI/OPRF. Trigger keywords: confidential computing, TEE, enclave, SEV-SNP, TDX, ARM CCA, SGX, Nitro Enclaves, confidential VM, remote attestation, attestation report, KBS, CoCo, Kata, Trustee, MKTME, confidential GPU, FHE, homomorphic encryption, MPC, ZKP, zero-knowledge, PSI, data in use, COED.

28 Updated today
martinholovsky