1
Add support for S3 ServerSideEncryption with KMS key ID
Source: directus/directus#24869 · opened by @rijkvanzanten
Discussed in <div type='discussions-op-text'> <sup>Originally posted by Joey92 November 27, 2023</sup> Summary I would like to build on top of At my work we're forced to use customer provided KMS keys to encrypt our data at rest in S3. So in order to CRUD the S3 bucket we need to provide the KMS key ID. Basically we'd have to add SSEKMSKeyId to the AWS SDK Commands in the S3 storage driver. For e.g. here: Basic Example _No response_ Motivation We would be able to handle more S3 KMS edge cases which are often the norm in bigger companies. Detailed Design Add SSEKMSKeyId | SSECustomerKey to the DriverS3Config and use that when communicating with S3, if defined and ServerSideEncryption == 'aws:kms' Requirements List Must Have: • Support for the SSEKMSKeyId and SSECustomerKey attribute in the aws sdk CommandInputs when ServerSideEncryption is 'aws:kms' Could have: • Additional c…
No pledges yet. Be the first to back this.
Comments
Similar requests
S3 ServerSideEncryption with KMS key ID
2 votes · 0 comments
Option to log out from Keycloak when logging out of Data Studio App
3 votes · 0 comments
Enable login with JWT from IdP via API
3 votes · 0 comments
Manage Multitenancy with Users Logging in via Keycloak
1 vote · 0 comments
Composite key support
111 votes · 0 comments
No comments yet.