Expected behaviour:
Use claudia update to deploy to Lambda with AWS SSO credentials, not local access key and secret key.
What actually happens:
I receive an error showing I have missing credentials. I have AWS CLI credentials working through SSO.
Error [CredentialsError]: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
at Timeout.connectTimeout [as _onTimeout]
Steps to reproduce the problem:
Without AWS Access Key and Secret key in config.
Sign in to aws sso with CLI command aws sso login
Use Claudia CLI to deploy the project with claudia update
Issue caused by:
In my experience with other projects, the issue is that Claudia uses AWS SDK 2.X which does not support SSO. I know AWS 3.X will support SSO.
Expected behaviour: Use
claudia update
to deploy to Lambda with AWS SSO credentials, not local access key and secret key.What actually happens: I receive an error showing I have missing credentials. I have AWS CLI credentials working through SSO.
Error [CredentialsError]: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 at Timeout.connectTimeout [as _onTimeout]
Steps to reproduce the problem: Without AWS Access Key and Secret key in config.
aws sso login
claudia update
Issue caused by: In my experience with other projects, the issue is that Claudia uses AWS SDK 2.X which does not support SSO. I know AWS 3.X will support SSO.