Skip to content

Commit f0346da

Browse files
committed
docs: Clarify TLS requirement
1 parent 895b2c7 commit f0346da

1 file changed

Lines changed: 1 addition & 4 deletions

File tree

docs/modules/druid/partials/s3-note.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,5 @@
33
You can specify just a connection/bucket for either ingestion or deep storage or for both, but Druid only supports a single S3 connection under the hood.
44
If two connections are specified, they must be the same. This is easiest if a dedicated S3 Connection Resource is used - not defined inline but as a dedicated object.
55
6-
The `S3Connection` `region` field is ignored because Druid uses the AWS SDK v1, which ignores the region if the endpoint is set.
7-
The host is a required field, therefore the endpoint will always be set.
8-
9-
TLS for S3 is not yet supported.
6+
Since Druid 37.0.0, TLS is now required for S3.
107
====

0 commit comments

Comments
 (0)