- 最新
- 最多得票
- 最多評論
Hello Jose, If possible, please file a technical support ticket so we can assist you further. We will need the UUID and region of an existing event source mapping experiencing this issue, we believe the one with the UUID above may have already been deleted.
Hi Jose,
As indicated by Chris in a previous answer, the error you are currently seeing is a generic error message displayed when there is no dedicated error message available to explain the cause of the ESM’s failure. The only way to determine the exact cause of this error is creating a ticket with AWS Premium Support so that the service team can investigate the logs for your resource.
There are a few things you can try though:
-
If the ESM and Lambda function had been working fine and suddenly failed, the issue could be transient; after the failure occurs, wait 15 minutes and then try re-enabling the ESM .
-
Check the Lambda execution role for any changes.
-
Determine the size of each message in the topic. Since the Lambda payload size limit is 6MB, a topic containing large records will be incompatible with Lambda. If there is any doubt, change the batch size to 1 and enable.
-
Check the Kafka broker logs for any traces of the ESM’s polling.
相關內容
- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前