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!
Lambda concurrency for Self managed Kafka event sourceasked 8 months ago
Set group.id for Kafka event source for lambda?asked 5 months ago
Missing MSK service icon within Lambda Function 'Add Trigger' dropdownasked 6 months ago
Lambda Scheduler to pull Data from Kafka Topicasked 5 months ago
Lambda trigger fails to connect with event source using RabbitMQasked a year ago
Lambda | self-managed mTLS kafka Trigger credential errorasked a month ago
How do I get trigger broker topic's routing key on lambda functionasked 6 months ago
Lambda Trigger "Service Error"asked 4 months ago
occasionally losing event/stream from kinesis to lambdaasked 2 months ago
Lambda MSK trigger not workingasked 2 years ago