Skip to content

Conversation

mauro13983
Copy link

In the current state the AwsProvider take the "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY" only from os.env.
The boto3.client instance is created with the default client that take the above parameters from os.env (and internally create a static shared instance of Session)
This is very limiting when using multiple credentials on parallel processes (like web applications and each user has is own keys) or simply you don't won't to export your private keys in your env.

My proposed solution, allows to create indipendent instances of the AwsProvider (no static shared boto3.Session) and also allows to specify the "access_key_id" and "secret_access_key" parameters via the provider configuration dictionary (directly in python).

@rohitprasad15
Copy link
Collaborator

@mauro13983 - thanks for raising this PR.
The approach looks good to me. Can you paste a screenshot showing that an example works! We are merge it after that.

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

Successfully merging this pull request may close these issues.

3 participants