3 Answers
- Newest
- Most votes
- Most comments
1
Just spitballing here, but does your machine think it's 1970 (start of the Unix epoch)? "Last fetched 53 years ago" is... suggestive. If the time is that far off, a whole bunch of things will cease to work properly.
answered 3 years ago
0
That's strange. Is it possible for you to try creating a function using AWS CLI? There could be an issue with your IAM permission but could not tell from that screenshot. Using the CLI could give you additional insights on the actual problem.
0
I am getting the same issue. I try with other computer and sync computer time online but can't fixed error.
answered 3 years ago
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago

+1 on this. I saw this just the other day with a laptop where the time was 4 minutes slow and all sorts of odd things were happening in the AWS console.