- 最新
- 投票最多
- 评论最多
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.
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.
I also got "Connection ready!". Regardless, as far as I know I am not behind any proxy or vpn.
Was there ever a solution here? I'm running into the same issue and can't figure it out.
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!
相关内容
AWS 官方已更新 1 年前- AWS 官方已更新 2 年前
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