
                    For iam, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

I got it to work! For anyone else finding this issue here's what I did In my configmap for aws-iam-authenticator I set up a role like this:

Then 

aws iam authenticator QUESTION: How to create the k8s users and groups to map to?

You need to map IAM users or roles into the cluster using the aws-auth ConfigMap This is done automatically for the user who creates the cluster 

aws iam authenticator error: You must be logged in to the server (Unauthorized) -- same IAM user created cluster

Possible solution if you created the cluster in the UI
If you created the cluster in the UI it's possible the AWS root user created the cluster 

aws iam authenticator error: the server doesn't have a resource type "svc"

I'm glad to see that I'm not the only one who had issues with it 😄
This is how I'm using aws-vault in WSL2 and Ubuntu 20.04
Short version

Long Version

Expand/Collapse
All the commands are executed in WSL2

aws vault Using aws-vault with WSL

@bilby91 nice!  Yeah I'm not sure of the precedence but that sounds right (For others: unset AWS_ACCESS_KEY_ID 

aws iam authenticator error: You must be logged in to the server (Unauthorized)

Hey folks I'm looking to get the binaries notorized When upgrading to Mac OS Catalina the following error appears as a pop up when using aws-vault
“aws-vault-darwin-amd64” can’t be opened because Apple cannot check it for malicious software

aws vault Not working in Mac OS Catalina

@pingles Thanks for sending me down the correct path I've tried with just using the role name and the full ARN in the pod deployment 

kiam failed to load system roots and no roots provided - TLS error

@plektra if you need access to IAM operations with a session token it should be MFA authenticated It's a requirement from AWS 

aws vault "The security token included in the request is invalid"

FML Was testing this and accidentally entered rather than tabbed on rm -rf ~/Library/Keychains Le sigh. 

aws vault Constantly have to re-enter keychain password, part 2

Hi @3r1co - i found the script in a separate Issue here I repost it below 👍 I wish to connect to an EKS Instance using kubectl with the authenticator 