- 最新
- 最多得票
- 最多評論
Unless the log group gets randomly auto-generated each time, try creating CloudWatch log group /aws/qbusiness/fe3f4ee8-9b85-4fb5-8fac-b2486fcc650c in account 342508195621, then rerun.
To create a log group
- In the AWS Console, search for CloudWatch service, then open the CloudWatch console
- In the navigation pane, choose Log groups.
- Choose Actions, and then choose Create log group.
- Enter the name for the log group, and then choose Create log group.
If this helps solve your problem, please choose this as the Accepted Answer so others on re:Post may benefit - thank you!
Hi, Birdie_007
Try upgrading the Gmail app if need be and clearing cache.
Hi Eric, I am a bit lost with your answer: Which gmail app are you refering to ? I do not have a choice on the version of the gmail connector that I select in kendra or q...
I investigated further and tried to do the same in kendra using a gmail connector to populate a kendra index. And the sympotms are the same: sync error and, again, the log group which doesn't exist. When creating it manually, it doesn't get populated.
It seems a gmail connector issue more than an Amazon Q issue by itself.
Thanks for any hint to help me understand what is wrong with my config or the connector.
相關內容
- 已提問 1 年前
AWS 官方已更新 1 年前
Thanks for your answer Eric.
In fact, I did try this trick, and it won't do the job. I do not have the missing cloud watch log group error anymore, but I do not have any log entry and no logstream gets populated upon the sync error, keeping me blind on what went wrong.