1 個回答
- 最新
- 最多得票
- 最多評論
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
已回答 2 年前
相關內容
- 已提問 7 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前