AWS gameliftservers documentation change
Summary
Added note about built-in retry logic for SNS notifications during delivery failures/throttling
Security assessment
The change documents reliability improvements for notification delivery but doesn't address security vulnerabilities or introduce security features. Mentions of authorization failures are incidental to describing error scenarios, not security fixes.
Diff
diff --git a/gameliftservers/latest/flexmatchguide/match-notification.md b/gameliftservers/latest/flexmatchguide/match-notification.md index 3552ce2a3..64cb358c6 100644 --- a//gameliftservers/latest/flexmatchguide/match-notification.md +++ b//gameliftservers/latest/flexmatchguide/match-notification.md @@ -25,0 +26,4 @@ For high-volume matchmaking systems, we recommend using standard (non-FIFO) Amaz +###### Note + +Amazon GameLift Servers automatically handles Amazon SNS delivery failures and throttling with built-in retry logic. When Amazon SNS returns throttling errors or temporary failures, Amazon GameLift Servers retries the notification delivery with progressive delays between attempts. This helps ensure event notifications are delivered reliably. However, notifications may be lost if failures persist after all retry attempts, or for non-retryable errors such as authorization failures or missing topics. +