qnabot-on-aws
qnabot-on-aws copied to clipboard
Kendra Web Cwaler is executed, but the KendraCrawlerSNSTopic that launches the ClowlerLambda is not triggered
Describe the bug I have run Kendra Web Crawler and confirmed that the web crawl is successful, but the SNS (KendraCrawlerSNSTopic) that triggers the CrawlerLambda is not triggered. https://github.com/aws-solutions/qnabot-on-aws/blob/main/source/docs/Technical%20Information.md#sns The above says that the SNS (KendraCrawlerSNSTopic) that triggers the CrawlerLambda is triggered when the Kendra Web Crawler is executed, but is this documentation wrong?
To Reproduce
- Set and update KendraID in QnABot stack.
- Go to Designers UI > Settings
- Change ENABLE_KENDRA_WEB_INDEXER: true, KENDRA_INDEXER_URLS: https://aws.amazon.com/lex/faqs/ , KENDRA_INDEXER_SCHEDULER: rate (1 day) (from now on, implement Guide > Advanced setup > Integrating Amazon Kendra > Web page indexer)
- Designers UI > Amazon Kendra Web Crawler > START INDEXING
- Check Status:COMPLETE WITH ERRORS
- Check ClientUI > What is Lex?
- Check KendraCrawlerSNSTopic from AWS console, but no subscriptions are set and there is no evidence of Topic activity
- Add an Email to the subscription of KendraCrawlerSNSTopic and perform steps 4-6 again, but no Email is received
Expected behavior When the Kendra Web Crawler is executed, an API is called in ContentDesigner and the SNS (KendraCrawlerSNSTopic) that triggers the ClowlerLambda is triggered
Please complete the following information about the solution:
- [x] Version: v5.5.2
- [x] Region: ap-northeast-1
- [ ] Was the solution modified from the version published on this repository?
- [ ] If the answer to the previous question was yes, are the changes available on GitHub?
- [x] Have you checked your service quotas for the services this solution uses?
- [ ] Were there any errors in the CloudWatch Logs?
Screenshots If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context Add any other context about the problem here.