Peter Woodworth

@MrArnoldPalmer potentially a Go issue

Hey @michalfurmanek, If you have specific places in mind where you think debug statements make sense to place, feel free to call them out. I think it would be great...

Ok @michalfurmanek, thanks for the response. It seems then that there's some issue with how we've implemented the proxy with v3. Would you be able to provide details on how...

I'm not a maintainer here anymore, @tim-finnigan this issue might need relabeling or merging with another issue (if there is a similar issue open, not sure)

This is now supported in `v3` with `output-credentials` https://github.com/aws-actions/configure-aws-credentials#retrieving-credentials-from-step-output-assumerole-with-temporary-credentials

Unfortunately I'm not really sure what to suggest aside from seconding that it is likely a secrets configuration issue. Please refer to #271 for further comments, we're working on improving...

Apologies for the delay once more, but I'll be closing this due to staleness. Thanks for the contribution

@yporwal1 this had to get closed because the PR was abandoned, not that it's the submitters fault or anything. This action was in no-mans land for a while in terms...

These quirks are now documented in the README https://github.com/aws-actions/configure-aws-credentials#claims-and-scoping-permissions

This is now documented better, and there is a helpful message that shows in the workflow logs if it's likely you need to enable this permission in `v3`