Skip to content

Commit bfbf664

Browse files
committed
Update docs/changelog/126843.yaml
1 parent 6e86bd8 commit bfbf664

File tree

1 file changed

+11
-23
lines changed

1 file changed

+11
-23
lines changed

docs/changelog/126843.yaml

Lines changed: 11 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,20 @@
11
pr: 126843
22
summary: Upgrade `repository-s3` to AWS SDK v2
33
area: Snapshot/Restore
4-
type: breaking
4+
type: "breaking, upgrade"
55
issues:
66
- 120993
7+
highlight:
8+
title: Upgrade `repository-s3` to AWS SDK v2
9+
body: "Closes #120993"
10+
notable: true
711
breaking:
812
title: Upgrade `repository-s3` to AWS SDK v2
913
area: Cluster and node setting
10-
details: >-
11-
12-
In earlier versions of {es} the `repository-s3` plugin was based on the AWS
13-
SDK v1. AWS will withdraw support for this SDK before the end of the life
14-
of {es} {minor-version} so we must migrate to the newer AWS SDK v2.
15-
16-
Unfortunately there are several differences between the two AWS SDK
17-
versions which may require you to adjust your system configuration when
18-
upgrading to {es} {minor-version} or later. These differences include, but
19-
may not be limited to, the following items.
14+
details: |2-
2015
16+
In earlier versions of {es} the `repository-s3` plugin was based on the AWS SDK v1. AWS will withdraw support for this SDK before the end of the life of {es} {minor-version} so we must migrate to the newer AWS SDK v2.
17+
Unfortunately there are several differences between the two AWS SDK versions which may require you to adjust your system configuration when upgrading to {es} {minor-version} or later. These differences include, but may not be limited to, the following items.
2118
* AWS SDK v2 requires users to specify the region to use for signing
2219
requests, or else to run in an environment in which it can determine the
2320
correct region automatically. The older SDK would try to determine the
@@ -27,7 +24,6 @@ breaking:
2724
`us-east-1` if no better value could be found.
2825
2926
* AWS SDK v2 does not support the EC2 IMDSv1 protocol.
30-
3127
* AWS SDK v2 does not support the
3228
`com.amazonaws.sdk.ec2MetadataServiceEndpointOverride` system property.
3329
@@ -44,21 +40,14 @@ breaking:
4440
longer has any effect.
4541
4642
* AWS SDK v2 does not support the `log-delivery-write` canned ACL.
47-
4843
* AWS SDK v2 counts 4xx responses differently in its metrics reporting.
49-
5044
* AWS SDK v2 always uses the regional STS endpoint, whereas AWS SDK v2
5145
could use either a regional endpoint or the global
5246
`https://sts.amazonaws.com` one.
47+
impact: |2-
5348
54-
impact: >-
55-
56-
If you use the `repository-s3` module, test your upgrade thoroughly before
57-
upgrading any production workloads.
58-
59-
Adapt your configuration to the new SDK functionality. This includes, but
60-
may not be limited to, the following items.
61-
49+
If you use the `repository-s3` module, test your upgrade thoroughly before upgrading any production workloads.
50+
Adapt your configuration to the new SDK functionality. This includes, but may not be limited to, the following items.
6251
* Specify the correct signing region using the
6352
`s3.client.${CLIENT_NAME}.region` setting on each node. {es} will try and
6453
determine the correct region based on the endpoint URL and other data
@@ -77,5 +66,4 @@ breaking:
7766
which starts with `http://`.
7867
7968
* If applicable, discontinue use of the `log-delivery-write` canned ACL.
80-
8169
notable: true

0 commit comments

Comments
 (0)