403 intermittently on public lambda URL invocation

0

Good day,

We have 2 lambda functions with public URLs hosted in eu-west-1 AZ both set to Auth: NONE

These URL's have been operating fine for months now without any further changes from our side.

Since the early hours of this morning we are intermittently getting a 403 response from both lambdas:

X-Amzn-Errortype: IncompleteSignatureException

Is anyone else experiencing this issue, I've tried re-deploying both lambdas without any success.

Matt
asked 10 months ago240 views
4 Answers
1
Accepted Answer

+=================+ On July 4, 2023 at approximately 11:00 PM PDT (July 5, 2023 6am UTC), we became aware of an issue where a subset of customers began experiencing an increase in 403 errors when invoking function URLs in the EU-WEST-1 Region. The underlying issue has been addressed and changes to resolve the issue are currently being deployed. We expect to see recovery by July 5, 2023 at 6:00 AM PDT (1pm UTC). We do not require any additional actions from customers at this time. +=================+

thanks for your input David!

Matt
answered 10 months ago
profile picture
EXPERT
reviewed 10 months ago
0
profile picture
David
answered 10 months ago
0

Yes CORS and resource policies set on both and nothing has changed in months in respect of this.

The fact that its working intermittently, I would say about 10% of the calls, leads me to believe this is some sort of AWS internal issue..

Matt
answered 10 months ago
0

If you have a high amount of request you can use reserved concurrency - https://docs.aws.amazon.com/lambda/latest/dg/configuration-concurrency.html

profile picture
David
answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions