Add support for `--profile` flag for choosing AWS profile

[kaheicanaan]

Currently, all boto3 clients are initiated without specifying the AWS profile name. Hence, the default profile will be used.

Adding the --profile flag would significantly improve the handiness of the CLI because it is very common to switch the profile frequently during development (for example, changing the target environment between dev and prod by switching the AWS profile).

[lmouhib]

Hi, thanks for raising this. We have it in our plan, there is a PR for it already.

[dacort]

Thanks for opening the issue @kaheicanaan! As @lmouhib mentioned, in progress just need to make sure it works across all the different clients. :)

I'm curious, does setting AWS_PROFILE environment variable work for you if you want to use a different profile? Or are you looking for functionality similar to the AWS CLI?

[kaheicanaan]

Thanks for opening the issue @kaheicanaan! As @lmouhib mentioned, in progress just need to make sure it works across all the different clients. :)

I'm curious, does setting AWS_PROFILE environment variable work for you if you want to use a different profile? Or are you looking for functionality similar to the AWS CLI?

Oh, it works for me as well. I didn't notice that there is another way to change the AWS profile.

[monometa]

Hi,

I was wondering if there's any chance the following pull requests could be reviewed and merged to enable support for AWS profiles: #47 or #14? @dacort @lmouhib

[monometa]

Hi again 👋

Any luck that those PRs might be merged?
Just checking in on #47 and #14 for AWS profile support.
Tagging @dacort @lmouhib again in case this slipped through