AWS chatbot documentation change
Summary
Expanded throttling documentation to include Slack workspace-level limits and clarify interaction between Amazon Q Developer and Slack throttling
Security assessment
Change explains operational throttling limits rather than addressing security vulnerabilities. No evidence of security incident mitigation.
Diff
diff --git a/chatbot/latest/adminguide/chatbot-troubleshooting.md b/chatbot/latest/adminguide/chatbot-troubleshooting.md index 725dfdcd1..d09f62f28 100644 --- a/chatbot/latest/adminguide/chatbot-troubleshooting.md +++ b/chatbot/latest/adminguide/chatbot-troubleshooting.md @@ -60 +60,7 @@ Don't enable the **Enable raw message delivery** feature for any SNS topic subsc -Amazon Q Developer allows for 10 events per second. If more than 10 events per second are received, any event above 10 is throttled. +Events are throttled for the following reasons: + + * Slack has throttling limits that are applied per workspace. Workspaces can have multiple channels, so it's easy to exceed the limit. For more information, see [Rate Limits](https://api.slack.com/apis/rate-limits). + + * Amazon Q Developer allows for 10 events per second. If more than 10 events per second are received, any event above 10 is throttled. + +Even if Amazon Q Developer doesn't throttle the event while posting a message to Slack, Slack might because limits are applied at the workspace level.