AWS connect: Reworded Amazon Lex resource-based policy description for Connect
Summary
Editorial rewrite clarifying that Connect Customer shows the service role and service-linked role name it uses and updates the Amazon Lex bot's resource-based policy to allow invocation.
Security assessment
The change only rephrases existing text about how Connect Customer is granted invoke permission on an Amazon Lex bot via resource-based policies; no new permission, boundary, or vulnerability is introduced or fixed.
Evidence
+Connect Customer shows the service role and service-linked role name that it uses. It uses Amazon Lex resource-based policies to call your Amazon Lex bot. When you link an Amazon Lex bot to your instance, Connect Customer updates the bot's resource-based policy so it can call the bot.
Diff
diff --git a/connect/latest/adminguide/enable-bot-building.md b/connect/latest/adminguide/enable-bot-building.md index 98ff6a9d6..9ba65d0ed 100644 --- a//connect/latest/adminguide/enable-bot-building.md +++ b//connect/latest/adminguide/enable-bot-building.md @@ -29 +29 @@ If you already have existing Service Control Policies (SCP) in place that block -Connect Customer displays the service role and service linked role name it uses. uses Amazon Lex resource-based policies to make calls to your Amazon Lex bot. When you associate an Amazon Lex bot with your Connect Customer instance, the resource-based policy on the bot is updated to give Connect Customer permission to invoke the bot. +Connect Customer shows the service role and service-linked role name that it uses. It uses Amazon Lex resource-based policies to call your Amazon Lex bot. When you link an Amazon Lex bot to your instance, Connect Customer updates the bot's resource-based policy so it can call the bot.