[Feature]: Support S3 Server Side Encryption

[utay]

Description

When configuring Nessie with Iceberg REST, we should be able to configure S3 with SSE (Server Side Encryption) type and key.

Expected Use Cases

It could look like this:

nessie.catalog.service.s3.default-options.sse.type=customer
nessie.catalog.service.s3.default-options.sse.customer-key=<base64 encoded key>

or:

nessie.catalog.service.s3.default-options.sse.type=kms
nessie.catalog.service.s3.default-options.sse.kms-key-id=<kms key id>

Trino S3 storage supports it already as an example (see s3.sse.type, s3.sse.kms-key-id and s3.sse.customer-key): https://trino.io/docs/current/object-storage/file-system-s3.html

Requested Changes in public API

No response

[dimas-b]

@utay : Thanks for filing this feature request. It looks valuable to users. Do you also intend to contribute a PR for this?

[utay]

@dimas-b Cool, I’m afraid I won’t have time to open a PR in the next few days, but I’d be very happy if someone else picks this issue up