Amazon Encryption SDK Concepts: Difference between revisions
| Line 22: | Line 22: | ||
* https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/faq.html | * https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/faq.html | ||
</font> | </font> | ||
=Encrypted Message= | |||
{{External|[https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#message Amazon Encryption SDK Developer Guide - Message]}} | |||
Revision as of 23:15, 12 December 2018
Internal
Supported Algorithms
The library uses an AES-GCM encryption algorithm with 256-bit, 192-bit and 128-bit encryption keys. The length of the Initialization Vector is 12 bytes. The length of the authentication tag is 16 bytes. By default, the SDK uses the data key as an input to the HMAC-based extract-and-expand key derivation function (HKDF) to derive the AES-GCM encryption key, and also adds an Elliptic Curve Digital Signature Algorithm (ECDSA) signature.
Data Key Management
By default, the SDK uses AWS KMS as the master key provider and its GenerateDataKey API operation to generate data keys and the Decrypt API operation to decrypt a data key that was stored alongside cipher text. AWS KMS encrypts and decrypts the data key by using the Customer Master Key that was specified when configuring the master key provider before the SDK use.
When data is encrypted, the SDK encrypts the data key and stores it along with the encrypted data in an encrypted message. When data is decrypted, the AWS Encryption SDK extracts the encrypted data key from the encrypted message, decrypts it, and uses it to decrypt the data.
Data Key Caching
TODO:
- https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/data-key-caching.html
- https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/faq.html