AWS gameliftservers documentation change
Summary
Added new 'Player gateway limits' section documenting 100pps UDP rate limit per player
Security assessment
Documents a new security feature that mitigates DDoS risks by limiting per-player traffic. Explicitly states it prevents malicious traffic overload but isn't tied to a specific vulnerability disclosure.
Diff
diff --git a/gameliftservers/latest/developerguide/ddos-protection-howitworks.md b/gameliftservers/latest/developerguide/ddos-protection-howitworks.md index 236996cae..da4f61a71 100644 --- a//gameliftservers/latest/developerguide/ddos-protection-howitworks.md +++ b//gameliftservers/latest/developerguide/ddos-protection-howitworks.md @@ -7 +7 @@ -Traffic flowCore conceptsMonitoring player gatewayIPv4 and IPv6 compatibility +Traffic flowCore conceptsMonitoring player gatewayPlayer gateway limitsIPv4 and IPv6 compatibility @@ -46,0 +47,6 @@ Player gateway publishes metrics to Amazon CloudWatch to help you monitor networ +## Player gateway limits + +To protect your game servers from traffic abuse, player gateway enforces a rate limit on UDP traffic for each player. With a valid player gateway token, player gateway limits each player token to 100 packets per second (pps). The relay network throttles traffic that exceeds this limit, and the traffic does not reach the game server. + +This per-player rate limit helps prevent individual players from overwhelming game servers with excessive traffic, whether because of misconfigured clients or malicious intent. +