AWS for Games Blog

Amazon GameLift Streams now supports using a dedicated AWS Identity and Access Management (IAM) role that can grant your streaming game sessions access to AWS resources in your account. In this blog post, we show you how to use that role with a lightweight launcher script to persist game saves from your player’s streaming sessions to Amazon Simple Storage Service (Amazon S3) without needing to make any changes to your game code.

In this post, we show you the key considerations for building a dedicated mobile frontend that solves these challenges while reusing the existing backend infrastructure and AWS Cloud Development Kit (AWS CDK) deployment pattern of Part 1.

Learn how for one games studio, their operations team spend 60% of their time context-switching between AWS Console interfaces and troubleshooting capacity issues during launch events. During one major content release, manual scaling decisions led to a 2-hour queue time spike that resulted in 12% player churn.

Cheating in online games erodes player trust, damages competitive integrity, and can drive players away. Game studios need a scalable analytics pipeline to detect anomalous player behavior. In this post, we show how to build a game integrity proof of concept (POC) using the Guidance for Game Analytics Pipeline on AWS, Amazon Athena, and Amazon […]

In this post, we walk through how we built an autonomous QA agent on Amazon Bedrock that connects to a running Unity game and executes test scenarios without human intervention. We cover connecting to a game’s internal object hierarchy, a perception and reasoning loop inspired by recent research on autonomous testing agents, and game-agnostic tools that extend as complexity increases. The approach was validated against a turn-based mobile strategy game built in Unity.

This is the first post in a series that will discuss the foundational data workloads: player profiles, inventory, session management, and content configuration. Part 2 addresses live operations and social features: leaderboards, matchmaking, chat, social graph, and game analytics.

In this blog, we explain how Lore—an open-source version control system created by Epic Games—rethinks binary asset storage by splitting files into content-addressed fragments that eliminate redundancy and make branching effectively free. We also share the reference architecture developed with Epic for deploying Lore on AWS using services like Amazon EC2, Amazon ECS, Amazon S3, and Amazon DynamoDB.

Learn how network bandwidth is now included at no additional charge for all Amazon GameLift Servers instances, generation 6 or newer (c6, m6, c7, m7 etc. instance families).

The purpose of this post is to highlight how to convert 2D art and game assets into 3D assets using open source models on the lowest level of the tech stack possible: Amazon Elastic Compute Cloud (Amazon EC2) instances.

In this post, we continue with the real-time, social, and analytical workloads: leaderboards, matchmaking, chat, social graph, and game analytics. Each of these has distinct access patterns that require different database choices. This post assumes familiarity with AWS database services and basic game backend architecture.