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
질문됨 일 년 전257회 조회
4개 답변
2
수락된 답변

+=================+ 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
답변함 일 년 전
profile picture
전문가
검토됨 10일 전
profile picture
전문가
검토됨 일 년 전
0
profile picture
David
답변함 일 년 전
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
답변함 일 년 전
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
답변함 일 년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠