
AWS KMS and AWS Encryption SDK use derived key methods with random nonces to automatically overcome AES-GCM encryption limits, eliminating the need for manual key rotation tracking in high-scale applications.


<div><p>This article explains how AWS KMS and AWS Encryption SDK handle AES-GCM symmetric encryption limits automatically using derived key methods, eliminating manual tracking for high-scale applications.</p><ul><li>AES-GCM has encryption invocation limits (2^32 encryptions) and data bounds (2^68 bytes) per key</li><li>AWS KMS derives a unique 256-bit key per encryption using a random 128-bit nonce and KDF</li><li>KMS generates random IV and encrypts plaintext (max 4 KB) with derived key via AES-GCM</li><li>AWS Encryption SDK uses HKDF with 256-bit random nonce to derive per-invocation keys</li><li>SDK frames data into 4 KB chunks with deterministic IVs, limiting total encrypted data to 2^44 bytes</li><li>Derived key approach ensures encryption bounds are never exceeded without manual key rotation</li></ul><p>By deriving unique keys per encryption invocation, both services automatically overcome AES-GCM bounds, simplifying secure encryption at cloud scale.</p></div>


Related articles