cli: support AWS_PROFILE environment variable for using named profiles

• 🪲 bug report

• What is the current behavior? CDK doesn’t use exported AWS_PROFILE cdk deploy Unable to resolve AWS account to use. It must be either configured when you define your CDK or through the environment

• What is the expected behavior (or behavior of feature suggested)?

export AWS_PROFILE=test cdk deploy should read profile from AWS_PROFILE and deploy the template

• What is the motivation / use case for changing the behavior or adding this feature? It should work using same env variables as AWS CLI

• Please tell us about your environment:

  • CDK CLI Version1.1.0 (build 1a11e96)
  • Module Version: xx.xx.xx
  • OS: Manjaro Linux
  • Language: all

[athewsey]

Not worth reopening I guess, but to help any future travellers that wind up here:

I recently encountered this on a fresh install using credential helpers: CDK did not respect $AWS_PROFILE even when it was definitely available in the environment (env), exported, and even visible to node (node, process.env.AWS_PROFILE).

…But the problem magically fixed after I created a blank credentials file: touch ~/.aws/credentials. Now cdk is automatically using my selected AWS_PROFILE.

So if you’re in a context where you don’t have a credentials file created because you don’t really use one - maybe give this a try!

[mateja82]

Not sure if this help, but in my organisation we use AWS SSO, with over 90 AWS Accounts, with MFA, so it was impossible to manage CDK without AWS CLIv2 with profiles, and AWS SSO support.

I found a way to solve it, so till its officially released, you can use this, it works quite all right: MatsCloud blog - CDK with AWS SSO multi account multi profile