library · inferred from evidence
AWS SDK
The AWS SDK used by the repository-s3 plugin, referenced as the source of the trailing checksum issue.
- OpenSearch 3.x snapshot repository fails on S3-compatible storage: "trailing checksum is not supported"
The 3.0.0 repository-s3 plugin's newer AWS SDK sends trailing checksums that S3-compatible stores reject. Verified workaround (confirmed by multiple users): set legacy MD5 checksum calculation per repository via the create-repository API, e
- Request is missing Authentication Token after upgrading Serverless Framework to 3.25.0
This was a regression in the AWS SDK bundled with Serverless Framework 3.25.0, not a problem with your credentials or config. Upgrade to v3.25.1, which contains the fix. Multiple reporters confirmed deploys started working again immediately
- XAmzContentSHA256Mismatch when creating a DigitalOcean Spaces bucket (PHP)
DigitalOcean's Spaces API does not expect a signed request body on the create-bucket call, while the AWS SDK signs the body by default, producing XAmzContentSHA256Mismatch. The package maintainer reproduced the error and updated the library
- SignatureDoesNotMatch 403 on DigitalOcean Spaces UploadFile (leading slash in path)
A leading forward slash on the object path breaks AWS Signature V4 signing against Spaces: UploadFile('/file.txt') fails while UploadFile('file.txt') succeeds. The reporter found this themselves and a second user confirmed the same fix on u
- Spaces-API PHP: temporary links crash with "Trying to access array offset on value of type null"
The v1 wrapper's temporary-link function was broken against the newer AWS SDK's retry middleware. The maintainer rewrote the package as v2 with a new API for signed URLs: Spaces("ACCESS KEY", "SECRET KEY")->space("my_space", "nyc3")->signed