rbIAM and assumedRoles

[casey-robertson]

We are leveraging assumed Roles and don't authenticate using IAM users. I get this error - not sure which user I should be specifying?

Gathering info from IAM and Kubernetes. This may take a bit, please stand by ...
Can't get user: ValidationError: Must specify userName when calling with non-User credentials
        status code: 400, 

[mhausenblas]

Interesting! Okay, I think I have a hunch. Once back from PTO I'll fix it and cut a new release, ETA: mid next week.

[siwyd]

Same issue here, using AWS federation with OneLogin, so same use case of assumed roles. Having read https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/, longing to get started with this :)

[yrsurya]

Gathering info from IAM and Kubernetes. This may take a bit, please stand by ... Can't get user: ValidationError: Must specify userName when calling with non-User credentials status code: 400, request id: 4d027ab7-fe1d-4162-9dff-9255b319e025⏎

Same issue we use okta assigned assume roles facing this issue while running rbiam

[T00mm]

Same issue, tried setting AWS_PROFILE but that didn't work. A --profile tag would be appreciated.

[mhausenblas]

Thanks for the reminder, yep such a flag makes sense. Hope to get to it soon!

[karstenmueller]

Since I am using assumed roles too sometimes soon would be much appreciated 😉

[mhausenblas]

If someone wants to PR it …

[joebowbeer]

@mhausenblas Is there a workaround?

[mhausenblas]

@joebowbeer not that I know of, I'm afraid.