Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js AWS SDK V3 credential issue when using "profile" in up.json #829

Open
4 tasks done
benkauffman opened this issue Aug 11, 2021 · 1 comment
Open
4 tasks done

Comments

@benkauffman
Copy link

benkauffman commented Aug 11, 2021

Prerequisites

  • I am running the latest version. (up upgrade)
  • I searched to see if the issue already exists.
  • I inspected the verbose debug output with the -v, --verbose flag.
  • Are you an Up Pro subscriber?

Description

AWS_PROFILE environment variable is interfering with AWS SDK V3 credentials

Describe the bug or feature.
When migrating from V2 to V3 AWS SDK i discovered that AWS_PROFILE is persisted in the lambda execution environment variables.
The only location that I defined this was in the "profile" section of up.json, the new AWS SDK version fails to load because of this.

Steps to Reproduce

I created a sample app and published the repo to demonstrate this issue:
https://github.com/benkauffman/apex-up-aws-sdk-v3-bug-example

Describe the steps required to reproduce the issue if applicable.
you can either run the ./run.test.sh or follow the outlined steps in the project README.md

Slack

Join us on Slack https://chat.apex.sh/

@nothingrealhappen
Copy link

Thanks for raise this issue, saved my life. after delete profile in up.json everything works!

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

No branches or pull requests

2 participants