I found that with current implementation user doesn't have option to choose to use DefaultAWSCredentialsProviderChain. I think current behavior is bit odd: developers familiar with AWS SDK will expect applications to use default provider chain by default, not instance profile credentials.
I added new option awsUseInstanceProfile to choose whether to use instance profile credentials and set the default value to true to not affect the current default behavior. I also updated relevant docs.
I found that with current implementation user doesn't have option to choose to use
DefaultAWSCredentialsProviderChain
. I think current behavior is bit odd: developers familiar with AWS SDK will expect applications to use default provider chain by default, not instance profile credentials.I added new option
awsUseInstanceProfile
to choose whether to use instance profile credentials and set the default value to true to not affect the current default behavior. I also updated relevant docs.