Skip to content

docs: Clarify region and TLS requirements #836

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
NickLarsenNZ merged 3 commits into from
Jun 29, 2026
Merged

docs: Clarify region and TLS requirements #836

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f0346da
docs: Clarify TLS requirement
NickLarsenNZ Jun 29, 2026
548b2a4
Revert "docs: Clarify TLS requirement"
NickLarsenNZ Jun 29, 2026
5d75a43
docs: Clarify TLS requirement
NickLarsenNZ Jun 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/modules/druid/partials/s3-note.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
====
Loading