- 新しい順
- 投票が多い順
- コメントが多い順
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
Thanks, Sumit, for the response, Kafka trigger showed up after a day without making any changes. I'm sure it wasn't network/browser issue as all of my team members from different locations couldn't see that. Any way it was just a UI issue and trigger was working all the time.