Upgrade aws-sdk-go to v1.55.7 for EKS Pod Identity support#871
Open
phoenix1712 wants to merge 2 commits into
Open
Upgrade aws-sdk-go to v1.55.7 for EKS Pod Identity support#871phoenix1712 wants to merge 2 commits into
phoenix1712 wants to merge 2 commits into
Conversation
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.
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.
Author
|
Added commit 535df94 with an unrelated-but-necessary CI fix: the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
github.com/aws/aws-sdk-gofromv1.44.298tov1.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 theAWS_CONTAINER_CREDENTIALS_FULL_URIcredential provider along with the EKS container IP allowlist (169.254.170.23/fd00:ec2::23) andAWS_CONTAINER_AUTHORIZATION_TOKEN_FILEhandling. Without this bump,s5cmdis a blocker for deployments migrating to EKS Pod Identity.Changes
go.mod:aws-sdk-gov1.44.298->v1.55.7go mod tidy && go mod vendor)Testing
go build ./...passesgo vet ./...passesgofmtcleango mod verifypassesTestNewSessionWithProfileFromFile/use_default_profile. This test fails identically on the priorv1.44.298baseline 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.