GitHub OIDC assume role fails when limiting S3 bucket resource in IAM policy #835
Unanswered
tobiasehlert
asked this question in
Q&A
Replies: 2 comments
-
The run was started from a branch.. so the main reference in the trust policy was the issue to this. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to authenticate a GitHub Action workflow towards a S3 bucket in my AWS account and most stuff seems to be working, except that I can't limit my IAM policy to only be towards one S3 bucket.
Error from aws-actions/configure-aws-credentials
This is the workflow authentication step:
I set up my stuff with Terraform, similar to this example, but slightly different:
https://github.com/terraform-aws-modules/terraform-aws-iam/blob/master/examples/iam-github-oidc/main.tf
This is the trust policy on the
GH-my-poc-bucket-role
role:Working IAM policy
Failing IAM policy
Why the heck can't I limit the policy to allow access to only one bucket?
Kind regards,
Tobias
Beta Was this translation helpful? Give feedback.
All reactions