Custom authorizer gives 403 after put and get in quick succession

lambda

#1

I have a page in my UI where I call an api gateway to update (PUT) an entity, and then on success I forward to a view page where I call an api gateway to retrieve (GET) the entity. I notice that I get random 403 failures.

If I switch off the authorizer there are no issues.

Just wondering if there is some sort of default throttle on my api that is getting hit… its really weird. My authorizer just verifys a jwt token each time -really weird


#2

I’m seeing the same behavior. Almost every other call fails with a 403. Have you figured anything out since you posted this?