Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add support AWS-KMS on S3 for FTE #22529

Conversation

marcinsbd
Copy link
Contributor

@marcinsbd marcinsbd commented Jun 27, 2024

Description

This PR adds support for encrypting the files stored in S3 bucket as a part of files generated by FTEs.

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

# Section
* Allow configuring encryption for S3 Filesystem when used for FTE

@cla-bot cla-bot bot added the cla-signed label Jun 27, 2024
@marcinsbd marcinsbd marked this pull request as draft June 27, 2024 13:10
@marcinsbd marcinsbd force-pushed the marcinsbd/FTE-to-support-self-managed-keys-on-S3 branch 3 times, most recently from b97d5f7 to 52f3752 Compare July 23, 2024 19:45
@marcinsbd marcinsbd marked this pull request as ready for review July 23, 2024 20:51
@marcinsbd marcinsbd force-pushed the marcinsbd/FTE-to-support-self-managed-keys-on-S3 branch 3 times, most recently from 2d96da6 to 016c10e Compare July 26, 2024 10:40
@Praveen2112
Copy link
Member

@marcinsbd Can you please rebase the PR ?

@marcinsbd marcinsbd force-pushed the marcinsbd/FTE-to-support-self-managed-keys-on-S3 branch 2 times, most recently from 6b5178b to 6d22b83 Compare July 31, 2024 18:11
@marcinsbd marcinsbd force-pushed the marcinsbd/FTE-to-support-self-managed-keys-on-S3 branch 2 times, most recently from 8f6cd1e to 0cc6d27 Compare August 12, 2024 10:37
@marcinsbd marcinsbd force-pushed the marcinsbd/FTE-to-support-self-managed-keys-on-S3 branch from 0cc6d27 to a64ae47 Compare August 13, 2024 08:09
@marcinsbd marcinsbd force-pushed the marcinsbd/FTE-to-support-self-managed-keys-on-S3 branch 2 times, most recently from 5b312b8 to 9f28c49 Compare August 14, 2024 11:59
@marcinsbd marcinsbd force-pushed the marcinsbd/FTE-to-support-self-managed-keys-on-S3 branch from 9f28c49 to 3a7db93 Compare August 14, 2024 12:42
@marcinsbd marcinsbd requested a review from ssheikin August 14, 2024 14:16
Comment on lines 309 to 314
@AssertTrue(message = "Property value of exchange.s3.sse.kms-key-id needs to be provided only when exchange.s3.sse.type=KMS")
public boolean isSseConfigValid()
{
return sseType == KMS ^ getSseKmsKeyId().isEmpty();
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Would be a bit more readable to have two separate validations for

  • sseType != KMS && sskeKeyId not emtpy
  • sseType == KMS && sskKeyId empty

Then you could provide easier to understand error messages.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@marcinsbd marcinsbd force-pushed the marcinsbd/FTE-to-support-self-managed-keys-on-S3 branch from 3a7db93 to 51bc447 Compare August 28, 2024 11:43
@Praveen2112 Praveen2112 merged commit 739aeff into trinodb:master Aug 29, 2024
94 checks passed
@github-actions github-actions bot added this to the 455 milestone Aug 29, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Development

Successfully merging this pull request may close these issues.

4 participants