1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
It sounds like a problem with the underlying Lambda service, so it is not much you can do. Stuff like this is quite rare, but it happens and will resolve itself when AWS finds the issue.
However, it can also be a bad error message for another issue, so try the following:
- Doing it via the CLI or SDK. It would be an issue with the console.
- Give yourself a lot of access (ex lambda:*) to verify that it's not access related. Sometimes AccessDenied can give weird errors, and a new version of the console, CLI or SDK can have added new APIs (like describe actions).
- Open a support ticket.
- Make sure you are not hitting any limitations (support can help with this).
I hope it helps!
//Carl
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr