Remove SSL consideration in S3 migration guide #24772
Conversation
| @@ -346,7 +346,6 @@ implementation is recommended. Legacy support will be deprecated and removed. | |||
| The following considerations apply to legacy configurations moving to the native | |||
| implementation: | |||
|
|
|||
| * SSL is always enabled and cannot be disabled. | |||
| * Client-side encryption is not supported. Server-side encryption (SSE) is | |||
There was a problem hiding this comment.
I don't understand this one too. Is the client-side referring to Trino doing encryption or else?
There was a problem hiding this comment.
Maybe things got mixed up in writing this .. spooling protocol vs native file system ..
There was a problem hiding this comment.
yeah, it seems so. SSL is required for S3 spooling as it generates presigned URIs.
There was a problem hiding this comment.
Is this still worth mentioning: "Multipart (non-streaming) writes and upload are not supported."? Does it really add value or should the entire "considerations" section be removed?
There was a problem hiding this comment.
I am not sure what that means in the context eithere.. lets wait for @jhlodin to chime in about where that info came from, but I think we can remove it all.
Description
Additional context and related issues
Release notes
(x) 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.
( ) Release notes are required, with the following suggested text: