AWS gameliftservers documentation change
Summary
Restructured documentation to emphasize Spot fleet queue implementation tasks, added detailed guidance on queue configuration strategies, and expanded best practices for Spot instance resilience and cost optimization.
Security assessment
The changes focus on operational reliability and cost optimization when using Spot instances, not security vulnerabilities. While they mention handling Spot interruptions (a reliability concern), there is no evidence of addressing security flaws, vulnerabilities, or security feature enhancements. The updates improve documentation clarity and implementation guidance without introducing security-specific content.
Diff
diff --git a/gameliftservers/latest/developerguide/spot-tasks.md b/gameliftservers/latest/developerguide/spot-tasks.md index d48431072..33fb2247d 100644 --- a//gameliftservers/latest/developerguide/spot-tasks.md +++ b//gameliftservers/latest/developerguide/spot-tasks.md @@ -5 +5 @@ -Best practices for queues with Spot fleets +Implementation tasksBest practices @@ -7 +7 @@ Best practices for queues with Spot fleets -# Design a queue for Spot Instances +# Build a queue for Spot Instances @@ -9 +9 @@ Best practices for queues with Spot fleets -You can take advantage of significant savings in hosting costs by using Spot fleets. For more details, see [On-Demand Instances versus Spot Instances](./gamelift-compute.html#gamelift-compute-spot). To add Spot fleets to your hosting solution, you need to configure a game session queue with a combination of Spot fleets and On-Demand fleets. Amazon GameLift Servers uses a queue during the game session placement process to search across multiple fleets and find the best available hosts for new game sessions. This topic provides guidance on how to start using Spot fleets. +You can achieve of potentially significant savings in hosting costs by using Spot fleets. For more details about Spot fleets and how to use them, see [On-Demand Instances versus Spot Instances](./gamelift-compute.html#gamelift-compute-spot). @@ -11 +11 @@ You can take advantage of significant savings in hosting costs by using Spot fle -Are you using FlexMatch for matchmaking? You can use the following steps to add Spot fleets to your existing game session queues for matchmaking placements. +If your game hosting solution includes Spot fleets, you must use a game session placement queue. Amazon GameLift Servers uses queues to search across multiple game hosting resources and select the best one available to host a new game session. With Spot fleets, queues are particularly important for minimizing hosting costs and avoiding possible Spot interruptions. This topic helps you set up a resilient queue that can continue to host games for players even in the event of interruptions, slowdowns and outages. You can customize how the queue prioritizes available hosting resources based on several factors including hosting cost. @@ -13 +13 @@ Are you using FlexMatch for matchmaking? You can use the following steps to add - 1. **Determine the destinations for your game session queue.** +Are you using FlexMatch for matchmaking? You can use a queue with Spot fleets to make game session placements for your matches. @@ -15 +15 @@ Are you using FlexMatch for matchmaking? You can use the following steps to add -Managing game session placement with a queue is best practice, and it's required when using Spot Instances. Because Spot Instances might not always be available when you need them, you need to design a resilient queue that includes both Spot fleets and On-Demand fleets to offer backup capacity. You can keep your On-Demand fleets scaled down until they're needed. To design your queue, consider the following: +## Implementation tasks for Spot fleets @@ -17 +17 @@ Managing game session placement with a queue is best practice, and it's required - * Locations – If possible, your Spot fleets and On-Demand fleets should be in the same Region as the players. Position both Spot resources and On-Demand resources in each location that you want to support. Multi-location fleets support both Spot and On-Demand instances. +When creating or updating your game hosting solution to use Spot fleets, complete the following tasks. For more detailed guidance on how to build a queue that optimizes Spot availability and resiliency, see [Reduce game hosting costs with Spot fleets ](./fleets-spot.html). @@ -19 +19 @@ Managing game session placement with a queue is best practice, and it's required - * Instance types – Consider your game server's hardware requirements and availability of instances in the locations you choose. + 1. **Choose and create a set of fleet destinations for your game session queue.** @@ -21 +21 @@ Managing game session placement with a queue is best practice, and it's required -To try a queue that optimizes Spot availability and resiliency, see [Tutorial: Create an Amazon GameLift Servers queue with Spot Instances](./tutorial-queues-spot.html). For Spot design best practices, see [Best practices for Amazon GameLift Servers game session queues](./queues-design.html#queues-best-practices). +Start by deciding where you want your queue to place game sessions. A queue can search across multiple fleets to find the best possible placement. Each fleet has one instance type but can have multiple geographic locations. Queues with fleets that offer variety in both location and instance type are more likely to make successful placements. See these best practices for designing an effective and resilient Spot-optimized queue. @@ -23 +23 @@ To try a queue that optimizes Spot availability and resiliency, see [Tutorial: C - 2. **Create the fleets for your Spot-optimized queue.** + 2. **Create your Spot-optimized game session queue.** @@ -25 +25 @@ To try a queue that optimizes Spot availability and resiliency, see [Tutorial: C -Based on your queue design, create fleets to deploy your game servers to your desired locations and instance types. See [Create an Amazon GameLift Servers managed EC2 fleet](./fleets-creating.html) for help creating and configuring new fleets. +Create a queue and configure it for your Spot fleets. See [Create a game session queue](./queues-creating.html) for help creating and configuring the new queue. You can use the Amazon GameLift Servers console or the AWS CLI to create or edit a queue. @@ -27 +27 @@ Based on your queue design, create fleets to deploy your game servers to your de - 3. **Create your game session queue.** + * Add the fleet destinations from Step 1. @@ -29 +29 @@ Based on your queue design, create fleets to deploy your game servers to your de -Add the fleet destinations, configure the game session placement process, and define placement priorities. See [Create a game session queue](./queues-creating.html) for help creating and configuring the new queue. + * Prioritize the destination order as appropriate. By default, Amazon GameLift Servers prioritizes by cost before destination, so destination order is used only when the lowest costs between destinations are equal. @@ -31 +31 @@ Add the fleet destinations, configure the game session placement process, and de - 4. **Update your game client service to use the queue.** + * If you want to prioritize game hosting cost before player latency, provide a custom placement priority. See [Prioritize game session placement](./queues-design-priority.html). @@ -33 +33 @@ Add the fleet destinations, configure the game session placement process, and de -When your game client uses a queue to request resources, the queue avoids resources with a high chance of interruption and selects the location that matches your defined priorities. For help implementing game session placements in your game client, see [Create game sessions](./gamelift-sdk-client-api.html#gamelift-sdk-client-api-create). + 3. **Update other components in your solution to use the new queue.** @@ -35 +35 @@ When your game client uses a queue to request resources, the queue avoids resour - 5. **Update your game server to handle a Spot interruption.** +When your solution uses a Spot-optimized queue to start new game sessions, the queue automatically avoids placing game sessions with fleets that have a high likelihood of interruption. It instead searches all viable fleets for resources that match your defined priorities, including player latency, hosting cost, and destination order. @@ -37 +37 @@ When your game client uses a queue to request resources, the queue avoids resour -AWS can interrupt Spot Instances with a 2 minute notification, when it needs the capacity back. Set up your game server to handle interruption to minimize player impact. + * If you're not using FlexMatch – Update your backend service to specify the new Spot-optimized queue in game session requests. The backend service makes API requests to Amazon GameLift Servers on behalf of your game client (using `StartGameSessionPlacement()`), and each request must specify a queue name. For help implementing game session placements in your game client, see [Create game sessions](./gamelift-sdk-client-api.html#gamelift-sdk-client-api-create). @@ -39 +39 @@ AWS can interrupt Spot Instances with a 2 minute notification, when it needs the -Before AWS reclaims a Spot Instance, it sends a termination notification. Amazon GameLift Servers passes the notification to all affected server processes by invoking the Amazon GameLift Servers Server SDK callback function `onProcessTerminate()`. Implement this callback to end the game session or move the game session and players to a new instance. See [Respond to a server process shutdown notification](./gamelift-sdk-server-api.html#gamelift-sdk-server-terminate) for help implementing `onProcessTerminate()`. + * If you are using FlexMatch – Update your matchmaking configuration to send game session requests to the new Spot-optimized queue. When the matchmaking system forms a player match, it sends a game session placement request to the designated queue to start a new game session for the match. Only matchmaking configurations with FlexMatch mode set to "Managed" can designate a placement queue. You can update a matchmaking configuration using the AWS CLI or the Amazon GameLift Servers console (see [Edit a matchmaking configuration](https://docs.aws.amazon.com/gameliftservers/latest/flexmatchguide/match-create-configuration-edit.html)). @@ -41,5 +41 @@ Before AWS reclaims a Spot Instance, it sends a termination notification. Amazon -###### Note - -AWS makes every effort to provide the notification before it reclaims an instance, but it's possible that AWS reclaims the Spot Instance before the warning arrives. Prepare your game server to handle unexpected interruptions. - - 6. **Review the performance of your Spot fleets and queues.** + 4. **Review the performance of your Spot fleets and queues.** @@ -49 +45 @@ View Amazon GameLift Servers metrics in the Amazon GameLift Servers console or w - * Interruption rate – Use the `InstanceInterruptions` and `GameSessionInterruptions` metrics to track the number and frequency of Spot-related interruptions for instances and game sessions. Game sessions that are reclaimed by AWS have a status of `TERMINATED` and a status reason of `INTERRUPTED`. + * Interruption rate – Use the `InstanceInterruptions` and `GameSessionInterruptions` metrics to track the number and frequency of Spot-related interruptions for instances and game sessions. Game sessions on reclaimed instances have a status of `TERMINATED` and a status reason of `INTERRUPTED`. @@ -60 +56,21 @@ View Amazon GameLift Servers metrics in the Amazon GameLift Servers console or w -If your queue includes Spot fleets, set up a resilient queue. This takes advantage of cost savings with Spot fleets while minimizing the effect of game session interruptions. For help with correctly building fleets and game session queues for use with Spot fleets, see [Tutorial: Create an Amazon GameLift Servers queue with Spot Instances](./tutorial-queues-spot.html). For more information about Spot instances, see [Design a queue for Spot Instances](./spot-tasks.html). +Use the following best practices when creating fleets and queues for Spot instances. + + * **Expand your queue's geographic coverage.** Even if your players are clustered in a single AWS Region, add adjacent locations to your Spot fleet. This approach improves the queue's ability to maintain capacity during regional slowdowns, outages, and Spot interruptions. Multi-location fleets work with both Spot and On-Demand instances. + + * **Diversify your queue's instance type coverage.** Amazon GameLift Servers evaluates Spot viability based on instance type, so having Spot fleets with a variety of instance types reduces the chance that multiple Spot fleets are nonviable at the same time. Include at least two Spot fleets with different instances types each location. + +###### Note + +Pricing is based on the instances you use, not the number of fleets. Running five fleets with 10 instances each is the same as running one fleet with 50 instances of similar cost. Pricing varies by instance type, size, and location. + +Tips for grouping Spot instance types: + + * Use instance types in the same family, such as `m6g.medium`, `m6g.large`, and `m6g.xlarge`. Larger instance types cost more, but can also host more game sessions at a time. + + * Select widely available instances types. Typically, older generation families (such as C5, M5, and R5) and common sizes (such as .large, .xlarge, and .2xlarge) have better availability. + + * Check the 30-90 day pricing history in the Amazon GameLift Servers console. Look for instance types with consistent availability patterns. + + * Use the Amazon GameLift Servers console, fleet creation tool, to explore location coverage for instance types. + + * **Add On-Demand fleets for backup capacity.** Game hosting can switch to On-Demand fleets whenever Spot fleets are unavailable. Put at least one On-Demand fleet in each location to maintain low player latency. Add auto-scaling to your backup On-Demand fleets, so you can keep them scaled down until they're needed. @@ -62 +78 @@ If your queue includes Spot fleets, set up a resilient queue. This takes advanta -In addition to the general best practices in the previous section, consider these Spot-specific best practices: + * **Assign aliases to all fleet destinations.** Create aliases for each of your queue's destinations. Aliases make it easier and more efficient whenever you need to replace fleets. @@ -64 +80 @@ In addition to the general best practices in the previous section, consider thes - * **Create at least one On-Demand fleet in each location.** On-Demand fleets provide backup game servers for your players. You can keep your backup fleets scaled down until they're needed, and use auto scaling to increase On-Demand capacity when Spot fleets are unavailable. + * **Apply a queue prioritization strategy.** You can customize how a queue prioritizes where to place game sessions (see [Prioritize game session placement](./queues-design-priority.html) for more details). For Spot-optimized queues, prioritizing by cost ensures that low-cost Spot fleets are used whenever possible. @@ -66 +82 @@ In addition to the general best practices in the previous section, consider thes - * **Select different instance types across multiple Spot fleets in a location.** If one Spot Instance type becomes temporarily unavailable, the interruption affects only one Spot fleet in the location. Best practice is to choose widely available instance types, and use instance types in the same family (for example, m5.large, m5.xlarge, m5.2xlarge). Use the [Amazon GameLift Servers console](https://console.aws.amazon.com/gamelift/) to view historical pricing data for instance types. +You can also prioritize certain fleets by specifying a destination order. For example, some users designate a set of primary fleets for regular use and also a set of secondary fleets as backup. In this scenario, set the queue's destination order to list the primary fleets first. Then configure the queue's priority order with destination followed by cost. @@ -77 +93 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Evaluate queue metrics +Create a player latency policy @@ -79 +95 @@ Evaluate queue metrics -Set up event notification +Hosting resources