We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, we are requiring static credentials (in the form of access key and secret key). But if we are running in aws (e.g. ec2, ecs, lambda), then we already have temporary credentials (iam role). In these cases, I would like to not use an iam user. See: https://github.com/amzapi/selling-partner-api-sdk/blob/cf9bdde067d8ef6e33eafc1dc3e607ecd05a0b60/pkg/selling-partner/selling-partner.go
Can we use a credential provider chain from the aws-sdk to handle all cases? See: https://docs.aws.amazon.com/sdk-for-go/api/aws/credentials/#NewChainCredentials. Or we make the credentials object configurable.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, we are requiring static credentials (in the form of access key and secret key). But if we are running in aws (e.g. ec2, ecs, lambda), then we already have temporary credentials (iam role). In these cases, I would like to not use an iam user. See: https://github.com/amzapi/selling-partner-api-sdk/blob/cf9bdde067d8ef6e33eafc1dc3e607ecd05a0b60/pkg/selling-partner/selling-partner.go
Can we use a credential provider chain from the aws-sdk to handle all cases? See: https://docs.aws.amazon.com/sdk-for-go/api/aws/credentials/#NewChainCredentials. Or we make the credentials object configurable.
The text was updated successfully, but these errors were encountered: