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.
 ====