Skip to content

Use supplied credentials in AWS SDK client#6893

Merged
vimtor merged 1 commit into
devfrom
aws-sdk-override-account
May 29, 2026
Merged

Use supplied credentials in AWS SDK client#6893
vimtor merged 1 commit into
devfrom
aws-sdk-override-account

Conversation

@vimtor

@vimtor vimtor commented May 29, 2026

Copy link
Copy Markdown
Collaborator

Closes #6888

  • The aws4fetch client constructor previously only used env variables or ECS container credentials, ignoring any credentials passed through the aws options
  • Update client() to accept optional AwsOptions and use accessKeyId/secretAccessKey from supplied options before falling back to env or container metadata
  • Pass options?.aws from awsFetch() into client() so all SDK consumers (task, bus, workflow) inherit the fix

@vimtor vimtor changed the title Use supplied AwsOptions credentials in AWS SDK client Use supplied credentials in AWS SDK client May 29, 2026
@vimtor vimtor merged commit 817ac33 into dev May 29, 2026
1 check passed
@vimtor vimtor deleted the aws-sdk-override-account branch May 29, 2026 11:06
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.

SST Task SDK does not support loading credentials from supplied aws4fetch options

1 participant