Is it AWS bug: Created Self-Managed-Kafka trigger is not showing up on Lambda Console page

Question

In my project I created event-source-mapping for lambda to integrate with self-managed-Kafka cluster, it used to display the trigger connection to lambda when you go on Lambda console page but today it is not displaying the trigger anymore. However, the trigger exists and working without any problem, is it an AWS bug to not showing the self-managed-kafka trigger? Even you can check that the trigger exists using aws-cli.

Answer

Kafka triggers are owned by Lambda pollers and Lambda disables the trigger if there are any issues with permissions or any other issues. 
Since the trigger is working as expected, it should show up on console. Could you please verify if the trigger is configured on specific version of function? If yes, then the trigger will show up on the function's specific version page and not on default page of Lambda function which is for "$LATEST" version.

There might be a network issue or an issue with browser which could lead to trigger details not showing up. Please try different browsers and network and review browser console logs as well for any errors.

If the above recommendations doesn't help to identify the issue, we would need details that are non-public information. Please open a support case with AWS using the following [link](https://support.console.aws.amazon.com/support/home#/case/create)

Is it AWS bug: Created Self-Managed-Kafka trigger is not showing up on Lambda Console page

Relevant content