4 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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.
répondu il y a un an
0
i am getting the same error I don't know how to fix it
répondu il y a un an
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.
répondu il y a un an
Contenus pertinents
- demandé il y a un an
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans
+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.