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
What this skill does
# Implementing Envelope Encryption with AWS KMS ## Overview 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 large volumes of data locally while keeping the master key secure in a hardware security module (HSM) managed by AWS. This skill covers implementing envelope encryption using AWS KMS GenerateDataKey API. ## When to Use - When deploying or configuring implementing envelope encryption with aws kms capabilities in your environment - When establishing security controls aligned to compliance requirements - When building or improving security architecture for this domain - When conducting security assessments that require this implementation ## Prerequisites - Familiarity with cryptography concepts and tools - Access to a test or lab environment for safe execution - Python 3.8+ with required dependencies installed - Appropriate authorization for any testing activities ## Objectives - Understand the envelope encryption pattern and its advantages - Generate data encryption keys using AWS KMS GenerateDataKey - Encrypt/decrypt data locally using DEKs - Store encrypted DEK alongside ciphertext - Implement key caching to reduce KMS API calls - Handle key rotation with automatic re-encryption - Implement multi-region encryption for disaster recovery ## Key Concepts ### Envelope Encryption Flow 1. Call `kms:GenerateDataKey` to get plaintext DEK + encrypted DEK 2. Use plaintext DEK to encrypt data locally (AES-256-GCM) 3. Store encrypted DEK alongside ciphertext 4. Discard plaintext DEK from memory 5. For decryption: call `kms:Decrypt` on encrypted DEK, then decrypt data ### Advantages Over Direct KMS Encryption | Aspect | Direct KMS | Envelope Encryption | |--------|-----------|-------------------| | Max data size | 4 KB | Unlimited | | Latency | Network round-trip per operation | Local encryption | | Cost | $0.03/10,000 requests | Fewer KMS requests | | Offline | Not possible | Yes (with cached DEKs) | ### KMS Key Types - **AWS Managed**: AWS creates and manages (`aws/s3`, `aws/ebs`) - **Customer Managed**: You create and manage policies - **Custom Key Store**: Backed by CloudHSM cluster ## Security Considerations - Never store plaintext DEK; only keep encrypted DEK - Use key policies to restrict who can call GenerateDataKey and Decrypt - Enable AWS CloudTrail logging for all KMS API calls - Implement key rotation (automatic annual rotation for CMKs) - Use encryption context for authenticated encryption metadata - Handle KMS throttling with exponential backoff ## Validation Criteria - [ ] GenerateDataKey returns plaintext and encrypted DEK - [ ] Data encrypts correctly with plaintext DEK using AES-256-GCM - [ ] Encrypted DEK can be decrypted via KMS Decrypt API - [ ] Decrypted DEK recovers the original data - [ ] Plaintext DEK is wiped from memory after use - [ ] Encryption context is validated during decryption - [ ] Key rotation re-encrypts DEKs with new master key
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.