Amazon Encryption SDK: Difference between revisions
| Line 24: | Line 24: | ||
=Concepts= | =Concepts= | ||
<span id='Data_Key_Caching'></span>{{Internal|Amazon Encryption SDK Concepts|Amazon Encryption SDK Concepts}} | |||
< | |||
</ | |||
=Encryption= | =Encryption= | ||
Revision as of 22:45, 12 December 2018
External
Internal
Overview
Dependencies
dependencies {
implementation('org.bouncycastle:bcprov-ext-jdk15on:1.58')
implementation('com.amazonaws:aws-encryption-sdk-java:1.3.1')
}
Clarify whether I need KMS API or not: AWS KMS API Dependencies.
Concepts
Encryption
Overhead Introduced by Amazon Encryption SDK Message Format
Encrypting data with Amazon Encryption SDK introduces a certain amount of space overhead, mainly due to the fact that the data key, after being encrypted with the customer master key, is stored together with the cipher text. The amount of overhead depends on the size of the clear text data, encryption algorithm, whether additional authenticated data (AAD) is provided, and the length of that AAD, the number and type of master key providers, and the frame size. When AWS Encryption SDK is used with its default configuration, with one CMK in AWS KMS as the master key, with no AAD, and encrypt non-framed data, the overhead is approximately 600 bytes. In general, it can be reasonably assumed that Amazon Encryption SDK adds overhead of 1KB or less, not including AAD.