Skip to content

If the assumed role name is GitHubActions the action will fail with a non specific error #953

Closed
@kle-sd

Description

@kle-sd

Describe the issue

Ran into this for a few hours tonight where I was naming my role to be assumed GitHubActions and was failing to assume role via OIDC. The action spat out this error. Simply renaming the role to anything else ran successfully.

Could not assume role with OIDC: Not authorized to perform sts:AssumeRoleWithWebIdentity

The pitfall is especially time consuming because web searching the error leads to posts suggesting to fix the conditions in the IAM trust policy which are unrelated.

I suggest either highlighting this restricted role name in the documentation, or fixing the issue preventing use of this role name.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdocumentationThis is an issue with documentationp2

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions