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

[benkauffman]

Prerequisites

• [X] I am running the latest version. (up upgrade)
• [X] I searched to see if the issue already exists.
• [X] I inspected the verbose debug output with the -v, --verbose flag.
• [x] 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]

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