Skip to content

feat: Upgrade AWS SDK Go v2 to v1.41.1 with IMDSv2 support#649

Open
the-mann wants to merge 1 commit intomainfrom
feat/upgrade-sdk-v2-imdsv2
Open

feat: Upgrade AWS SDK Go v2 to v1.41.1 with IMDSv2 support#649
the-mann wants to merge 1 commit intomainfrom
feat/upgrade-sdk-v2-imdsv2

Conversation

@the-mann
Copy link
Contributor

Upgrade aws-sdk-go-v2 from v1.23.5 to v1.41.1 and all service SDKs to latest versions.

Problem

SDK v1.40+ (Nov 2025) disables IMDSv1 fallback by default, causing "no EC2 IMDS role found" errors after StopAgent() in integration tests.

Changes

  • Upgraded all aws-sdk-go-v2 dependencies to latest
  • Added config.WithEC2IMDSClientEnableState(imds.ClientEnabled) to all LoadDefaultConfig call sites:
    • util/awsservice/constant.go
    • util/common/metrics.go
    • test/amp/amp_test.go
    • test/ca_bundle/ca_bundle_test.go

Testing

Integration tests triggered via agent repo workflow.

🤖 Assisted by AI

Upgrade aws-sdk-go-v2 from v1.23.5 to v1.41.1 and all service SDKs to
latest versions. SDK v1.40+ disables IMDSv1 fallback by default, so
explicitly configure EC2IMDSClientEnableState in all LoadDefaultConfig
call sites to ensure credential resolution continues working on EC2.

Updated files:
- util/awsservice/constant.go
- util/common/metrics.go
- test/amp/amp_test.go
- test/ca_bundle/ca_bundle_test.go

🤖 Assisted by AI
@the-mann the-mann requested a review from a team as a code owner February 13, 2026 22:48
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.

1 participant