crim-ca/weaver

Support AWS profiles

fmigneault opened this issue · 0 comments

Description

At the moment, S3 buckets are supported using the configuration/credential files or environment variables for the default profile.
If more configurations are needed (different ACL), it is not currently possible to provide the relevant profile as input with the S3 file reference to perform authentication.

Provided with a profile name, it would be possible to define multiple access methods. That profile would have to be passed along the input href during process execution to generate a session with the corresponding profile.

References