From 27c52f0e0439f8e5d05e192d0208aa2516673e68 Mon Sep 17 00:00:00 2001 From: Jeremy Dahlgren Date: Tue, 19 Aug 2025 13:13:41 -0400 Subject: [PATCH] Fix an AWS SDK v2 release note Fixes a release note where AWS SDK v2 was used instead of AWS SDK v1. --- docs/reference/migration/migrate_8_19.asciidoc | 2 +- docs/reference/release-notes/8.19.0.asciidoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/migration/migrate_8_19.asciidoc b/docs/reference/migration/migrate_8_19.asciidoc index d7fa5347bbb86..b69f1f3536b51 100644 --- a/docs/reference/migration/migrate_8_19.asciidoc +++ b/docs/reference/migration/migrate_8_19.asciidoc @@ -100,7 +100,7 @@ Unfortunately there are several differences between the two AWS SDK versions whi * AWS SDK v2 counts 4xx responses differently in its metrics reporting. -* AWS SDK v2 always uses the regional STS endpoint, whereas AWS SDK v2 +* AWS SDK v2 always uses the regional STS endpoint, whereas AWS SDK v1 could use either a regional endpoint or the global `https://sts.amazonaws.com` one. diff --git a/docs/reference/release-notes/8.19.0.asciidoc b/docs/reference/release-notes/8.19.0.asciidoc index e0aa183eb9e8e..6223e4bbbb225 100644 --- a/docs/reference/release-notes/8.19.0.asciidoc +++ b/docs/reference/release-notes/8.19.0.asciidoc @@ -117,7 +117,7 @@ Existing `repository-s3` configurations may no longer be compatible. Notable dif * AWS SDK v2 requires the use of the V4 signature algorithm, therefore, the `s3.client.${CLIENT_NAME}.signer_override` setting is deprecated and no longer has any effect. * AWS SDK v2 does not support the `log-delivery-write` canned ACL. * AWS SDK v2 counts 4xx responses differently in its metrics reporting. -* AWS SDK v2 always uses the regional STS endpoint, whereas AWS SDK v2 could use either a regional endpoint or the global `https://sts.amazonaws.com` one. +* AWS SDK v2 always uses the regional STS endpoint, whereas AWS SDK v1 could use either a regional endpoint or the global `https://sts.amazonaws.com` one. **Action:** Test the upgrade in a non-production environment. Adapt your configuration to the new SDK functionality. This includes, but may not be limited to, the following items: