Skip to content

Rapid game server iteration on Amazon GameLift Servers with Multi-build Container Fleets

3 minute read
Content level: Intermediate
0

A new solution for the Amazon GameLift Servers toolkit enables running multiple game server build versions on a single container fleet, with builds stored in S3 and synced automatically, eliminating the need to rebuild containers for each version update.

Hello Amazon GameLift Servers developers,

We're excited to share a new solution for the Amazon GameLift Servers toolkit that brings greater flexibility to container-based deployments: Multi-build Container Fleets. This solution enables you to run multiple game server build versions simultaneously on a single fleet, with game server binaries stored in Amazon S3 and synced automatically to instances—eliminating the need to bake builds into container images or rebuild containers for version updates.

The solution uses a two-container architecture: a game server container that runs the Amazon GameLift Server SDK wrapper and your game server process, and a per-instance S3 sync container that continuously syncs builds from S3 to a shared volume. When a game session request arrives, you simply specify the build version in the GameProperties, and the wrapper automatically loads and launches the correct version. This approach enables zero-downtime updates, as you can deploy new builds by uploading them to S3 without touching your fleet infrastructure.

Key features include dynamic build loading from S3, support for multiple build versions on the same fleet, version selection per game session request, build integrity verification with completion markers, and an interactive CLI tool for easy build management. The solution comes with automated deployment using AWS CloudFormation and AWS CodeBuild, handling all infrastructure setup and container builds for you. Game server binaries don't need to integrate with the Amazon GameLift Server SDK directly, as the wrapper process manages all SDK interactions.

The solution works best for development, test, and alpha/beta environments where rapid iteration is valuable. For production deployments, consider the resource utilization of the S3 sync container (0.125vCPU/512MB) and evaluate whether the flexibility benefits outweigh having more static fleet configurations. The solution is configured by default for c6i.xlarge instances running three concurrent game sessions, with all resources and parameters fully customizable through CloudFormation.

To learn more about Amazon GameLift Servers Multi-build Container Fleets, see the following resources:

Amazon GameLift Toolkit

AWS for Games Blog

We'd love to hear your feedback on this solution and how it helps streamline your game server deployment workflows. Feel free to share your experiences or questions in the comments below.

Best regards, The Amazon GameLift Servers Team

AWS
EXPERT
published a month ago61 views