Skip to content

Commit a4ac0ef

Browse files
committed
Revert "Update docs/changelog/126843.yaml"
This reverts commit 6390e9c.
1 parent 6390e9c commit a4ac0ef

File tree

1 file changed

+31
-10
lines changed

1 file changed

+31
-10
lines changed

docs/changelog/126843.yaml

Lines changed: 31 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,33 @@
11
pr: 126843
22
summary: Upgrade `repository-s3` to AWS SDK v2
33
area: Snapshot/Restore
4-
type: "breaking, upgrade"
4+
type: breaking
55
issues:
66
- 120993
77
highlight:
88
title: Upgrade `repository-s3` to AWS SDK v2
9-
body: |-
10-
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 have migrated this plugin to the newer AWS SDK v2.
11-
The two SDKs are not quite compatible, so please check the breaking changes documentation and test the new version thoroughly before upgrading any production workloads.
9+
body: >-
10+
In earlier versions of {es} the `repository-s3` plugin was based on the AWS
11+
SDK v1. AWS will withdraw support for this SDK before the end of the life
12+
of {es} {minor-version} so we have migrated this plugin to the newer AWS SDK v2.
13+
14+
The two SDKs are not quite compatible, so please check the breaking changes
15+
documentation and test the new version thoroughly before upgrading any
16+
production workloads.
1217
notable: true
1318
breaking:
1419
title: Upgrade `repository-s3` to AWS SDK v2
1520
area: Cluster and node setting
16-
details: |-
17-
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.
18-
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.
21+
details: >-
22+
In earlier versions of {es} the `repository-s3` plugin was based on the AWS
23+
SDK v1. AWS will withdraw support for this SDK before the end of the life
24+
of {es} {minor-version} so we must migrate to the newer AWS SDK v2.
25+
26+
Unfortunately there are several differences between the two AWS SDK
27+
versions which may require you to adjust your system configuration when
28+
upgrading to {es} {minor-version} or later. These differences include, but
29+
may not be limited to, the following items.
30+
1931
* AWS SDK v2 requires users to specify the region to use for signing
2032
requests, or else to run in an environment in which it can determine the
2133
correct region automatically. The older SDK would try to determine the
@@ -25,6 +37,7 @@ breaking:
2537
`us-east-1` if no better value could be found.
2638
2739
* AWS SDK v2 does not support the EC2 IMDSv1 protocol.
40+
2841
* AWS SDK v2 does not support the
2942
`com.amazonaws.sdk.ec2MetadataServiceEndpointOverride` system property.
3043
@@ -41,13 +54,20 @@ breaking:
4154
longer has any effect.
4255
4356
* AWS SDK v2 does not support the `log-delivery-write` canned ACL.
57+
4458
* AWS SDK v2 counts 4xx responses differently in its metrics reporting.
59+
4560
* AWS SDK v2 always uses the regional STS endpoint, whereas AWS SDK v2
4661
could use either a regional endpoint or the global
4762
`https://sts.amazonaws.com` one.
48-
impact: |-
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.
63+
64+
impact: >-
65+
If you use the `repository-s3` module, test your upgrade thoroughly before
66+
upgrading any production workloads.
67+
68+
Adapt your configuration to the new SDK functionality. This includes, but
69+
may not be limited to, the following items.
70+
5171
* Specify the correct signing region using the
5272
`s3.client.${CLIENT_NAME}.region` setting on each node. {es} will try and
5373
determine the correct region based on the endpoint URL and other data
@@ -66,4 +86,5 @@ breaking:
6686
which starts with `http://`.
6787
6888
* If applicable, discontinue use of the `log-delivery-write` canned ACL.
89+
6990
notable: true

0 commit comments

Comments
 (0)