Skip to content

Commit fb9a881

Browse files
committed
2 parents ab38373 + f21603b commit fb9a881

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed
Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,13 @@
1-
## Update to AWS SDK v2.x for S3
2-
The v1 AWS SDK Dataverse used for S3 is in maintenance mode and will reach it's end of life in Dec. 2025.
3-
With this release, Dataverse has switched to v2.x of the SDK. Older versions of localstack, e.g. v2.3.2 appear to be incompatible and users of localstack should update (v.4.2.0 was tested).
4-
As part of the update the payload-signing setting for S3 stores has been removed. With the new toolkit a payload signature will automatically be sent when required (and not sent when not required).
5-
1+
## Upgrade to AWS SDK v2 (for S3), v1 EOL in December 2025
2+
3+
To support S3 storage, Dataverse uses the AWS SDK. We have upgraded to v2 of this SDK because v1 reaches End Of Life (EOL) in [December 2025](https://aws.amazon.com/fr/blogs/developer/announcing-end-of-support-for-aws-sdk-for-java-v1-x-on-december-31-2025/).
4+
5+
As part of the upgrade, the payload-signing setting for S3 stores (`dataverse.files.<id>.payload-signing`) has been removed because it is no longer necessary. With the updated SDK, a payload signature will automatically be sent when required (and not sent when not required).
6+
7+
Dataverse developers should note that LocalStack is used to test S3 and older versions appear to be incompatible. The development environment has been upgraded to LocalStack v2.3.2 to v4.2.0, which seems to work fine.
8+
9+
See also #11073 and #11360.
10+
11+
### Settings Removed
12+
13+
- `dataverse.files.<id>.payload-signing`

0 commit comments

Comments
 (0)