API headers not signed when AWS_PROFILE env var is set

I have a local node script used for testing our AWS Amplify app. Another product that I use requires the AWS_PROFILE env var to be set. This causes the local profile to be picked up while calling Auth.signIn which then causes a call to API.graphql to not set the x-amz-date and x-amz-security-token headers.

Steps to reproduce the behavior:

1. Run export AWS_PROFILE=... pointing to custom profile in ~/.aws/credentials
2. Auth.Config({ identityPoolId: XXX, region: XXX, userPoolId: XXX, userPoolWebClientId: XXX })
3. Auth.signIn(...)
4. API.graphql(...)
5. API gateway will throw a 403 error due to missing x-amz-date and x-amz-security-token headers

• MacOS 10.14.3
• aws-amplify 1.1.26

The fix is quite simple, just unset AWS_PROFILE, but it would be great if aws-amplify would ignore this env var or if it were documented somewhere.

[haverchuck]

@mikelduffy - Thanks. The aws-sdk loads the credentials from the environment variable, and this sdk is one of the Amplify dependencies. We are reviewing this issue.

[github-actions[bot]]

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.