Closed alistairstead closed 1 month ago
Ugh they don't seem to doing anything about it in that issue.
Yeah, unlikely to get fixed in the SDK. I guess SST used to omit the profile value in the env?
I've created a PR that should resolve this: https://github.com/sst/ion/pull/458
When using
set shell
to run scripts/tests that usewas-sdkV3
clients e.g.@aws-sdk/client-dynamodb
I run into this already documented error from the sdk package https://github.com/aws/aws-sdk-js-v3/issues/2549This appears to be being caused by the
AWS_PROFILE
value being passed through to the script fromset shell
. This has been validated to be the case with:I assume that in SST V2 the
AWS_PROFILE
was not passed to the sub command ofsst bind
?There is a user land work around as referenced in the thread above:
This resolves the issue but feels less than ideal.