-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
s3fs: Added documentation for SSE-C support #3498
Conversation
- `sse_customer_key` - user specified key to encrypt data uploaded when using | ||
SSE-C. The value should be base64 encoded version of 256 bit key. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! What's the value provided to sse
? Is it SSE-C
, or something like aws:ssec
(similar to aws:kms
) ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, this is AWS-specific right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. This is AWS-specific. Also, when SSE with client side keys for encryption is in question, libraries usually expect different parameter (SSECustomerAlgorithm
as key in s3_additional_kwargs dictionary) from sse (which gets added as ServerSideEncryption
as key in the s3_additional_kwargs dictionary). So, for SSE, when a user wants to use key in AWS KMS, the relevent parameters are sse
and sse_kms_key_id
. When a user wants to use their own key (which is SSE-C) then the relevant parameters are sse_customer_key
and sse_customer_algorithm
. Value of sse
is irrelevant for SSE-C.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it.
This comment was marked as resolved.
This comment was marked as resolved.
OK well this looks good (matches current iterative/dvc#7671) but needs reformatting, and Restyled is failing... Anyway I can fix that but please lmk when the core PR is merged first, @ap-kulkarni. And thanks again! |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just waiting for core merge/release. Thanks again @ap-kulkarni
I see this was merged in core. Any relevant changes @ap-kulkarni ? Thanks |
Not really sure if there is a change in the way users configure the remotes after the refactoring of related files into |
* ref: codeblocks complement to #3498 * Update content/docs/command-reference/remote/modify.md * Update content/docs/command-reference/remote/modify.md * ref: link `sse_kms_key_id` remote config param * Update content/docs/command-reference/remote/modify.md * Update content/docs/command-reference/remote/modify.md * Restyled by prettier (#3547) Co-authored-by: Restyled.io <commits@restyled.io> * ref: remote modify sse aws:kms doesn't require explicit key per #3533 (review) * Restyled by prettier (#3581) Co-authored-by: Restyled.io <commits@restyled.io> Co-authored-by: restyled-io[bot] <32688539+restyled-io[bot]@users.noreply.github.com> Co-authored-by: Restyled.io <commits@restyled.io>
Changes based on iterative/dvc#7671
❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention
Fix #issue
(if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏