From f0346da3b2a9c11aacbc9cbbb8a808ba7ec4e6bf Mon Sep 17 00:00:00 2001 From: Nick Larsen Date: Mon, 29 Jun 2026 19:21:54 +0200 Subject: [PATCH 1/3] docs: Clarify TLS requirement --- docs/modules/druid/partials/s3-note.adoc | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/modules/druid/partials/s3-note.adoc b/docs/modules/druid/partials/s3-note.adoc index 23ad4b7b..dc0b1257 100644 --- a/docs/modules/druid/partials/s3-note.adoc +++ b/docs/modules/druid/partials/s3-note.adoc @@ -3,8 +3,5 @@ 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. 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. -The `S3Connection` `region` field is ignored because Druid uses the AWS SDK v1, which ignores the region if the endpoint is set. -The host is a required field, therefore the endpoint will always be set. - -TLS for S3 is not yet supported. +Since Druid 37.0.0, TLS is now required for S3. ==== From 548b2a4858001f832373679363d67e069682eec5 Mon Sep 17 00:00:00 2001 From: Nick Larsen Date: Mon, 29 Jun 2026 21:44:09 +0200 Subject: [PATCH 2/3] Revert "docs: Clarify TLS requirement" This reverts commit f0346da3b2a9c11aacbc9cbbb8a808ba7ec4e6bf. --- docs/modules/druid/partials/s3-note.adoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/modules/druid/partials/s3-note.adoc b/docs/modules/druid/partials/s3-note.adoc index dc0b1257..23ad4b7b 100644 --- a/docs/modules/druid/partials/s3-note.adoc +++ b/docs/modules/druid/partials/s3-note.adoc @@ -3,5 +3,8 @@ 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. 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. -Since Druid 37.0.0, TLS is now required for S3. +The `S3Connection` `region` field is ignored because Druid uses the AWS SDK v1, which ignores the region if the endpoint is set. +The host is a required field, therefore the endpoint will always be set. + +TLS for S3 is not yet supported. ==== From 5d75a431e83f9c5d047bf2a1b54b9e645f8ace3a Mon Sep 17 00:00:00 2001 From: Nick Larsen Date: Mon, 29 Jun 2026 21:45:30 +0200 Subject: [PATCH 3/3] docs: Clarify TLS requirement --- docs/modules/druid/partials/s3-note.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/modules/druid/partials/s3-note.adoc b/docs/modules/druid/partials/s3-note.adoc index 23ad4b7b..511eef5b 100644 --- a/docs/modules/druid/partials/s3-note.adoc +++ b/docs/modules/druid/partials/s3-note.adoc @@ -3,8 +3,8 @@ 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. 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. -The `S3Connection` `region` field is ignored because Druid uses the AWS SDK v1, which ignores the region if the endpoint is set. +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. The host is a required field, therefore the endpoint will always be set. -TLS for S3 is not yet supported. +Since Druid 37.0.0, TLS is now required for S3. ====