1 Resposta
- Mais recentes
- Mais votos
- Mais comentários
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.
respondido há 2 anos
Conteúdo relevante
- AWS OFICIALAtualizada há 2 meses
- AWS OFICIALAtualizada há 2 anos
can you please explain more the solution