Skip to content

Upgrade aws-sdk-go to v1.55.7 for EKS Pod Identity support#871

Open
phoenix1712 wants to merge 2 commits into
peak:masterfrom
phoenix1712:upgrade-aws-sdk-go-v1.55.7
Open

Upgrade aws-sdk-go to v1.55.7 for EKS Pod Identity support#871
phoenix1712 wants to merge 2 commits into
peak:masterfrom
phoenix1712:upgrade-aws-sdk-go-v1.55.7

Conversation

@phoenix1712

Copy link
Copy Markdown

Summary

Bumps github.com/aws/aws-sdk-go from v1.44.298 to v1.55.7 (the latest functional v1 release).

Motivation

The pinned SDK version (v1.44.298) predates EKS Pod Identity support. Newer aws-sdk-go releases add the AWS_CONTAINER_CREDENTIALS_FULL_URI credential provider along with the EKS container IP allowlist (169.254.170.23 / fd00:ec2::23) and AWS_CONTAINER_AUTHORIZATION_TOKEN_FILE handling. Without this bump, s5cmd is a blocker for deployments migrating to EKS Pod Identity.

Changes

  • go.mod: aws-sdk-go v1.44.298 -> v1.55.7
  • Re-vendored dependencies (go mod tidy && go mod vendor)
  • Added a CHANGELOG entry

Testing

  • go build ./... passes
  • go vet ./... passes
  • gofmt clean
  • go mod verify passes
  • Unit tests pass, with one pre-existing exception: TestNewSessionWithProfileFromFile/use_default_profile. This test fails identically on the prior v1.44.298 baseline in my environment (the test writes to a temp credentials file without flushing before the SDK reads it), so it is not a regression introduced by this change.

This is a minor-version bump within SDK v1, so the public API surface used by s5cmd (storage/s3.go, tests) is unchanged.

Bumps github.com/aws/aws-sdk-go from v1.44.298 to v1.55.7 (latest v1
release). This pulls in EKS Pod Identity credential support via the
AWS_CONTAINER_CREDENTIALS_FULL_URI provider, which is required for
deployments migrating to Pod Identity.

Re-vendored dependencies with go mod tidy && go mod vendor.
@phoenix1712 phoenix1712 requested a review from a team as a code owner June 15, 2026 20:22
@phoenix1712 phoenix1712 requested review from denizsurmeli and igungor and removed request for a team June 15, 2026 20:22
The bitnami/minio:2023.7.18 tag was removed from Docker Hub during
Bitnami's August 2025 registry migration, causing the test jobs to fail
at the service-container pull step. Bitnami moved legacy versioned tags
to the bitnamilegacy namespace; switch to bitnamilegacy/minio:2023.7.18
(same image) to restore CI.
@phoenix1712

Copy link
Copy Markdown
Author

Added commit 535df94 with an unrelated-but-necessary CI fix: the test jobs were failing at the service-container step because bitnami/minio:2023.7.18 no longer resolves on Docker Hub (Bitnami's Aug 2025 registry migration emptied the bitnami/minio repo and moved legacy versioned tags to the bitnamilegacy namespace). This affects master CI as well, not just this PR. Switched to bitnamilegacy/minio:2023.7.18, which is the same image and is verified to still exist. Happy to split this into a separate PR if maintainers prefer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants