-
Type: New Feature
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: S3
-
Release Notes Summary:AWS S3 Client-side encryption with KMS is now possible
-
Release Notes Description:
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform #119
-
Story Points:5
Today, we only support S3 client-side encryption using a local key store (See https://doc.nuxeo.com/nxdoc/amazon-s3-online-storage/#client-side-crypto-options)
We'd like to support the client-side encryption as described in https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/examples-crypto-kms.html
Note that there is already a nuxeo.s3storage.crypt.kms.key nuxeo.conf property to define the KMS key ID to be used by AWS to encrypt data server-side. We'll introduce a new nuxeo.conf property nuxeo.s3storage.crypt.kms.clientside.key that should be defined to enable this client-side encryption type.
Considerations
- We assume nuxeo.s3storage.crypt.kms.key and nuxeo.s3storage.crypt.kms.clientside.key are different keys.
- The KMS key id (for client-side encryption) region could differ from the deployment environment or bucket one.
- The nuxeo.s3storage.crypt.keystore.file property enables client-side encryption using a private keystore. It takes precedences on nuxeo.s3storage.crypt.kms.clientside.key.
- depends on
-
NXBT-3814 Add KMS Key Id secrets in our CI
- Resolved
- is related to
-
NXP-32842 Allow to use S3 StrictAuthenticatedEncryption with a local keystore
- Resolved
-
NXP-32315 Upgrade to AWS SDK 2
- Resolved
- is required by
-
NXDOC-2704 Document AWS S3 KMS Client-Side Encryption Configuration
- Resolved