4 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
beantwortet vor einem Jahr
0
i am getting the same error I don't know how to fix it
beantwortet vor einem Jahr
You might also look at this other question: https://repost.aws/questions/QUyWa5mBnCRCygCUqduKBiPg/error-in-creating-lambda-function
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.
beantwortet vor einem Jahr
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
+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.