AWS gamelift documentation change
Summary
Updated service name references from 'Amazon GameLift' to 'Amazon GameLift Servers' throughout the document. Changed 'Developer Guide' to 'Hosting Guide' in breadcrumb. Updated console references and tutorial links to reflect new service naming.
Security assessment
Changes are branding/terminology updates rather than security-related content. No security vulnerabilities, mitigations, or new security features are mentioned. The existing content about Spot Instance termination handling remains unchanged except for service name references.
Diff
diff --git a/gamelift/latest/developerguide/spot-tasks.md index dba7f2d2c..9f4086c76 100644 --- a/gamelift/latest/developerguide/spot-tasks.md +++ b/gamelift/latest/developerguide/spot-tasks.md @@ -3 +3 @@ -[Documentation](/index.html)[Amazon GameLift](/gamelift/index.html)[Developer Guide](gamelift-intro.html) +[Documentation](/index.html)[Amazon GameLift](/gamelift/index.html)[Hosting Guide](gamelift-intro.html) @@ -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 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 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. @@ -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 queue with Spot Instances](./tutorial-queues-spot.html). For Spot design best practices, see [Best practices for Amazon GameLift game session queues](./queues-design.html#queues-best-practices). +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). @@ -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 managed EC2 fleet](./fleets-creating.html) for help creating and configuring new fleets. +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. @@ -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 passes the notification to all affected server processes by invoking the Amazon GameLift 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()`. +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()`. @@ -47 +47 @@ AWS makes every effort to provide the notification before it reclaims an instanc -View Amazon GameLift metrics in the Amazon GameLift console or with Amazon CloudWatch to review performance. For more information about Amazon GameLift metrics, see [Monitor Amazon GameLift with Amazon CloudWatch](./monitoring-cloudwatch.html). Key metrics include: +View Amazon GameLift Servers metrics in the Amazon GameLift Servers console or with Amazon CloudWatch to review performance. For more information about Amazon GameLift Servers metrics, see [Monitor Amazon GameLift Servers with Amazon CloudWatch](./monitoring-cloudwatch.html). Key metrics include: @@ -60 +60 @@ View Amazon GameLift metrics in the Amazon GameLift console or with Amazon Cloud -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 queue with Spot Instances](./tutorial-queues-spot.html). For more information about Spot instances, see [Design a queue for Spot Instances](./spot-tasks.html). +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). @@ -66 +66 @@ 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 console](https://console.aws.amazon.com/gamelift/) to view historical pricing data for instance types. + * **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.