AWS gameliftservers documentation change
Summary
Added migration guide from Node.js 10 to Node.js 24, updated Node.js version descriptions to indicate end-of-support dates and recommended versions
Security assessment
The changes document version migration and end-of-support timelines for Node.js 10, which is a routine maintenance update rather than addressing a specific security vulnerability. While migrating from unsupported software versions can have security implications, the documentation itself doesn't describe any security fixes, vulnerabilities, or security features - it focuses on migration procedures and compatibility.
Diff
diff --git a/gameliftservers/latest/realtimeguide/realtime-script.md b/gameliftservers/latest/realtimeguide/realtime-script.md index 4eab1e954..1f875b688 100644 --- a//gameliftservers/latest/realtimeguide/realtime-script.md +++ b//gameliftservers/latest/realtimeguide/realtime-script.md @@ -5 +5 @@ -Manage game session life-cycle (required)Add server-side game logic (optional)Node.js runtime versionsAmazon GameLift Servers Realtime script example +Manage game session life-cycle (required)Add server-side game logic (optional)Node.js runtime versionsMigrating from Node.js 10 to 24Amazon GameLift Servers Realtime script example @@ -42 +42 @@ Amazon GameLift Servers Realtime servers support multiple Node.js runtime versio - * **Node.js 10.x** (Default) - Runs on Amazon Linux 2. This version is nearing end of support as Amazon Linux 2 reaches end-of-life in June 2026. See [Amazon Linux 2 FAQs](https://aws.amazon.com/amazon-linux-2/faqs/) for more details. + * **Node.js 10** (Default) - Runs on Amazon Linux 2. Node.js 10 will reach end of support on September 30, 2026. See more details in the [Node.js 10 FAQs](https://aws.amazon.com/gamelift/faq/nodejs10/). For migration guidance, see [Migrating from Node.js 10 to 24](https://docs.aws.amazon.com/gamelift/latest/realtimeguide/realtime-script.html#realtime-script-nodejs-migration). @@ -44 +44 @@ Amazon GameLift Servers Realtime servers support multiple Node.js runtime versio - * **Node.js 24.x** \- Runs on Amazon Linux 2023 + * **Node.js 24** (Recommended) - Runs on Amazon Linux 2023. @@ -50,0 +51,35 @@ To specify the Node.js version and add optional customizations like install scri +## Migrating from Node.js 10 to 24 + +To migrate existing Amazon GameLift Servers Realtime servers from Node.js 10 to 24: + + 1. **Review your fleets** \- Check if you have existing fleets from scripts running on Node.js 10. You can identify affected fleets using several methods: + + * In the Amazon GameLift Servers console, navigate to the AWS Health Dashboard, look for the Node.js 10 end of support notification, and choose the **Affected resources** tab to see a list of your fleets using scripts with Node.js 10 runtime. + + * In the Amazon GameLift Servers console, navigate to **Managed EC2 fleets** and look for fleets created from scripts with Node.js 10 runtime. You can also check the Node.js version in the details page of each script resource, as well as identify fleets created with each script. + + 2. **Create a new script** \- Create and upload your existing script and choose the new target `NodeJsVersion` i.e., `24.x` for Node.js 24. If there are any errors uploading or starting your script, follow these steps: + + 1. Review the changes between Amazon Linux 2 and Amazon Linux 2023. For more information on Amazon Linux 2023 and the architectural differences with Amazon Linux 2, see [ Comparing AL2 and AL2023](https://docs.aws.amazon.com/linux/al2023/ug/compare-with-al2.html). + + 2. Review the changes between Node.js versions. For more information on Node.js version changes, see [Node.js release notes](https://nodejs.org/en/about/releases/). + + 3. Update your script. Make required changes to your scripts to work with the new target Node.js version and operating system. + + 4. Upload your new script. Upload your new script to Amazon GameLift Servers. For more information, see [Upload a script for Amazon GameLift Servers Realtime servers](./realtime-script-uploading.html). + + 3. **Create a test fleet with the new script** \- We recommend this step to ensure there are no errors in initializing your script and activating the fleet. For help with fleet creation issues, see [ Debug fleet creation issues](https://docs.aws.amazon.com/gameliftservers/latest/realtimeguide/fleets-creating-debug-realtime.html). + + 4. **Review fleet events for errors** \- If there are errors during fleet creation, you can look for the error messages on the **Events** tab on the Fleets view page. For more information about fleet events, see [ Event](https://docs.aws.amazon.com/gameliftservers/latest/apireference/API_Event.html) in the API Reference. + + 5. **(Optional) Update your script** \- If you encountered errors during script or fleet creation, fix and update your script until your fleet activates and the Amazon GameLift Servers Realtime server launches as expected. For troubleshooting guidance, see [Troubleshooting Amazon GameLift Servers issues](https://docs.aws.amazon.com/gameliftservers/latest/developerguide/gamelift-troubleshooting.html). + + 6. **(Optional) Create test game sessions** \- After your test fleet is active, set your game backend to target your new fleet. We recommend that you create test game sessions to verify game client connectivity. + + 7. **Migrate your player traffic to your new production fleet** \- If you have a game in production serving live player traffic, you can use Amazon GameLift Servers Queues and Aliases to migrate players to your new Node.js 24 runtime fleets. Use aliases to transfer players to a new fleet. When sending game session requests to Amazon GameLift Servers, specify a fleet alias instead of a fleet ID. For more information, see [ Create an alias](https://docs.aws.amazon.com/gameliftservers/latest/developerguide/aliases-creating.html). + + + + +For information about Node.js version support and end-of-life schedules, see the [Node.js releases](https://nodejs.org/en/about/releases/). +