Peter Woodworth

Results 212 comments of Peter Woodworth

@Fran-Rg `role-skip-session-tagging` ensures that [session tags](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html) are not applied to your session when you assume a role using this action. This isn't required to make role chaining work, according to...

Thanks all for your patience, I'll try to give this a review in the next week or so 🙂

If anyone is running into this issue, please specify what exactly you mean by "not working". What error message are you seeing, when are you seeing the error message?

It doesn't look like your secret is loading properly @Shiti, please ensure you've set your secret appropriately and that you've defined it properly in your `action.yml` file

I'm able to name it `AWS_REGION`, so it's interesting that fixed it for you. If you didn't have anything misconfigured (which could be a large number of things), I wonder...

We should absolutely improve error messaging. I'll try to update this thread with the errors I and others come across that are unclear

You nailed it @RichiCoder1, this needs to be defined in the JWT because [AssumeRoleWithWebIdentity()](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithWebIdentity.html#API_AssumeRoleWithWebIdentity_RequestParameters) lacks a tags parameter like [AssumeRole()](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html#API_AssumeRole_RequestParameters) does. Meaning AWS doesn't provide session tag mapping for OIDC...

We currently have a check for this https://github.com/aws-actions/configure-aws-credentials/blob/5a4b8f03d1948e564e5e97d168d19dbbab75abf4/index.js#L89-L91 Are you running into a bug where this is occurring @liwadman?

We should be able to support additional, non-required environment variables as session tags. Thanks for the suggestion! Documentation [here](https://docs.github.com/en/actions/learn-github-actions/environment-variables#default-environment-variables) for future reference

You can currently work around your specific issue through your action configuration like so until we may implement this: ``` on: pull_request_target: types: - opened branches: - 'master' push: branches:...