5 Replies
0cb0559898e1728b55aba4e2e8923479
Looks like it could be related, will check with the team handling the incident.
I just did an extra thing, which is adding metadata with the following header:
x-amz-meta-userr and I'm getting a 403 which could be related to the incident
without the meta header, it straights fails with a 500.If it's a new token, it will become a 500 it seems
It works now - it seems it was related to the incident