Richard H Boyd

Did you update the Role's condition on the trust policy to allow the second repository as well?

I'm looking into this now. We used 'sigstore' in an earlier version while we were testing the action.

What happens if you use `aws-actions/configure-aws-credentials@20ce4e5`?

I've been able to reproduce this. I'm working with the GitHub team to root cause it. Our plan was to use the audience `sts.amazonaws.com` since that indicates who you intend...

ecr-public is only available in us-east-1

a codecommit repository? the ecr-public registries are reachable from any region but you have to use the us-east-1 endpoint to retrieve your token to authenticate. https://stackoverflow.com/questions/69274998/could-not-connect-to-the-endpoint-url-https-api-ecr-public-xxxxxxxxx-amazona

no

You received that error when you tried to assume the role?

you're setting the region to us-west-2 in those env variables

interesting. I'm taking a look.