AWS gameliftstreams documentation change
Summary
Updated example configuration for large-scale events to change the number of idle sessions maintained from 1 to 100 for faster startup.
Security assessment
Change adjusts an example to maintain more idle sessions for faster scaling. No security implications.
Diff
diff --git a/gameliftstreams/latest/developerguide/stream-groups.md b/gameliftstreams/latest/developerguide/stream-groups.md index a9195401e..d01e9fa6e 100644 --- a//gameliftstreams/latest/developerguide/stream-groups.md +++ b//gameliftstreams/latest/developerguide/stream-groups.md @@ -54 +54 @@ The following examples demonstrate common stream capacity configurations for dif - 3. **Large-scale event with burst capacity:** You are planning for 1,000 users with 100 new sessions per minute at peak times. You set `Minimum` = 0, `Maximum` = 1,000, and `Target Idle` = 100. This saves money when idle. This keeps at least one session available for fast start up. + 3. **Large-scale event with burst capacity:** You are planning for 1,000 users with 100 new sessions per minute at peak times. You set `Minimum` = 0, `Maximum` = 1,000, and `Target Idle` = 100. This saves money when idle. This keeps at least 100 sessions available for fast start up.