1 個回答
- 最新
- 最多得票
- 最多評論
0
I found the answer to my question. The underlying reason for the error was that the assumed role that was creating the Lexbot intent did not have the ability to edit the IAM service role on the Lexbot.
After the assumed role (mine as the console user) was granted this permission, I recreated the KendraSearchIntent, and the Lex IAM service role was updated. The error no longer appears, and Lex can access the Kendra.
已回答 2 年前
相關內容
- 已提問 6 個月前
- AWS 官方已更新 2 年前
can you please explain more the solution