This repository has been archived by the owner on Jan 9, 2023. It is now read-only.
Use assume-role via .aws/config #277
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
When running tarmak as part of a jenkins pipeline I found that I was unable to use assume role config options in my ~/.aws/config file to grant tarmak the correct permissions.
For reference I was using variations on config that looked like this, where PROFILE is the name referenced by the tarmak.yaml
What you expected to happen:
After finding that this worked with the aws cli commands, I expected tarmak and terraform to work too.
Anything else we need to know?:
This is caused by a shortcoming in the aws go sdk aws/aws-sdk-go#1019 (comment)
If you're unfamiliar with the aws assumerole config options, this might be helpful: https://docs.aws.amazon.com/cli/latest/topic/config-vars.html#using-aws-iam-roles
At the time of writing, the go sdk only supports a profile with credentials referenced with source profile: https://docs.aws.amazon.com/sdk-for-go/api/aws/session/
The text was updated successfully, but these errors were encountered: