Skip to content

Commit 5d75a43

Browse files
committed
docs: Clarify TLS requirement
1 parent 548b2a4 commit 5d75a43

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@
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.
6+
Prior to Druid 37.0.0, the `S3Connection` `region` field is ignored because Druid uses the AWS SDK v1, which ignores the region if the endpoint is set.
77
The host is a required field, therefore the endpoint will always be set.
88
9-
TLS for S3 is not yet supported.
9+
Since Druid 37.0.0, TLS is now required for S3.
1010
====

0 commit comments

Comments
 (0)