By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Lambda Function Missing

0

A few months ago, I set up a Lambda Function that is invoked through a API Gateway Integration. A few days ago I noticed that endpoint was returning HTTP 500 (Internal Server Error). When I went to check the Lambda function, the main console for Lambda showed no set up functions, with a red error box with no text, and next to the refresh button the message "Last Fetched 53 years ago". Through API Gateway I was able to access the Lambda function, but the code window is missing (not empty, missing), and when I go to the "versions" tab, I once again get the red error box with no text. Same thing when I tried the "aliases" tab, and to view the function url. Oddly, when I ran the built in test, it says it passed, but when I checked the browser devtools, it showed it returned a HTTP 403 (Forbidden) error. When testing the function url in Postman, I get the same HTTP 403 error.

When I tried to create a new function, I went through the wizard without issue, but pressing "Create Function" at the end gives me a spinner that after 30min is still spinning.

Honestly, I haven't a clue how to even approach trying to solve this issue, or even what the issue is. Any guidance or assistance would be very much appreciated.

Topics
ServerlessComputeFront-End Web & MobileNetworking & Content Delivery
Tags
ServerlessAWS LambdaAmazon API Gateway
Language
English
silent-critter
asked a year ago734 views
3 Answers
0

The odd thing here is "53 years ago" which (probably not coincidentally) is the beginning of "time" as Linux/Unix operating systems measure it. It's possibly that your computer is a little bit in the future (from a clock perspective) so I would make sure that your timezone is set correctly and that the time on your computer is synced to a reliable (good) NTP source.

Having the clock wrong on your computer is an issue because the API calls are signed with the current time; and if the service (Lambda in this case) sees a request come from the future it won't process it - hence the errors that you're seeing.

profile pictureAWS
EXPERT
Brettski-AWS
answered a year ago
  • silent-critter
    a year ago

    I didn't realize that 53 years would put it at the beginning of Unix Epoch Time. I synced my computer's clock to time.nist.gov, and no change

0

Over the past few years various parts of the AWS Console have started relying on Websockets - the Lambda "Create Function" page is one of them. Are you behind a proxy that might be blocking Websockets? You can do an echo test at sites like https://socketsbay.com/test-websockets. Here, I get "Connection ready!" if I bypass our enterprise proxy but no successful connection otherwise.

EXPERT
skinsman
answered a year ago
  • silent-critter
    a year ago

    I also got "Connection ready!". Regardless, as far as I know I am not behind any proxy or vpn.

0

Was there ever a solution here? I'm running into the same issue and can't figure it out.

rePost-User-1875716
answered a year ago
  • silent-critter
    a year ago

    In my case the issue was caused by my account being frozen for some reason. Apparently, when an AWS account is frozen it only affects like 3 or so services which stop working without explanation, but everything else is fine which is not confusing at all.

    If that is the case for you, you should have gotten an email about it, and there should be a ticket in the support dashboard. Through the ticket the reps will take you through the process of unfreezing the account. You may need to prompt them with a "I did that, now what?" message as it is a multi-step process...

    Hope this helps. Good luck!

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

Relevant content