Ben Anderson

Just dropping in to add we're also investigating options for reporting job latency & queued count, per queue, to cloudwatch in the interest of alerting and autoscaling. for our use...

Unfortunately that didn't seem to work: ``` Run aws-actions/configure-aws-credentials@v4 Assuming role with OIDC Authenticated as assumedRoleId ``` my yml has: ``` - name: Configure AWS creds uses: aws-actions/configure-aws-credentials@v4 id: creds...

ah, just spotted the typo there - fixing and trying again.

with those typos fixed, it still fails, here's some debug logs: partially cropped to preserve IDs that aren't really sensitive but i'm paranoid

I've just noticed this, have I just forgotten some key somewhere?

that same link says there is a default audience (which should be correct for our partition) and it does seem that the login is working fine on the AWS task...

> This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions....

This is still not stale stale-bot.

> This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions....

> Won't this prevent any project that's still using react 18 from using this version? No, the minimum sdk constraint is unchanged - this is just bumping the version of...