The intention of this documentation is to provide the building blocks to create critical CloudWatch alarms which are fit for onboarding to Incident Detection and Response. It contains specific alarm best practices for AWS Services commonly used in the Games Industry.
Games
Introduction
Game developers are embracing industry-wide transformation, with studios pushing the latest technology boundaries and delivering continuously updated gaming experiences that scale to tens of millions of players. AWS for Games aligns purpose-built game development capabilities including AWS services, AWS solutions, and AWS Partners to help developers build, run, and grow their games.
Common Games Workloads:
Geolocation Systems for Betting & Gaming
Geolocation verification systems are often legally required to ensure that players are located within proper gaming jurisdictions when they place bets. The architecture below is designed to help enterprises build their own geolocation service that comes with low cost per check, flexible integration options, and high availability. In addition, service providers can access high-quality geospatial data from trusted data providers to better serve their customers.
Multiplayer Session-Based Game Hosting
The below architecture helps game developers get started with multiplayer game development by using Amazon GameLift for low-latency global game server hosting and matchmaking. It supports Unity, Unreal, and Godot game engines on the client side and provides sample integrations with Amazon GameLift for multiple game server implementation options, including C++, Go, Unity, and Unreal. This architecture also implements best practices for integrating your game backend with Amazon GameLift in addition to observability with Amazon CloudWatch through near real-time game server logs, process-level game server metrics, and distributed tracing for backend APIs.
Recommended Metrics to Monitor
We recommend using the below metrics to create and configure alarms based on the above sample architectures and advise to follow the Practices for Observability from the AWS Well-Architected, Operational Excellence Pillar located here.