Amazon GameLift

Name: Amazon GameLift API
Brand: Amazon GameLift
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeapiKey104 EndpointsREST

For Agents

Deploy multiplayer game servers, manage fleets and builds, run FlexMatch matchmaking, and place players into game sessions through Amazon GameLift.

Quickstart

Get started with Amazon GameLift in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a GameLift fleet from a build"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon GameLift API.

Upload custom game server builds and scripts and deploy them to GameLift fleets

Create and scale fleets across AWS regions with on-demand or Spot capacity

Place game sessions into queues and prioritise destinations by latency

Run FlexMatch matchmaking with custom rule sets to assemble balanced matches

GET STARTED

Start building with Amazon GameLift API

Explore with Jentic

View OpenAPI Document

Use for: I need to deploy a new build to a GameLift fleet, Create a fleet of game servers in eu-west-1 and us-east-1, Place a game session for four players via the queue, Start a FlexMatch matchmaking ticket for a player squad

Not supported: Does not handle in-game voice chat, player accounts, billing, or in-game economy — use for game server hosting, matchmaking, and session placement only.

Jentic publishes the only available OpenAPI document for Amazon GameLift, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon GameLift, keeping it validated and agent-ready. Amazon GameLift is AWS's managed service for hosting session-based multiplayer game servers in the cloud. The API covers fleets, builds, scripts, aliases, game sessions, player sessions, FlexMatch matchmaking, queues, and GameLift FleetIQ for cost-optimised Spot capacity. It is built for game studios that need to deploy custom server binaries to global AWS regions, scale match capacity dynamically, and route players into matches with low latency.

Use Cases

Patterns agents use Amazon GameLift API for, with concrete tasks.

★ Multi-Region Fleet Deployment

Game studios use Amazon GameLift to deploy custom server builds to fleets in multiple AWS regions, giving players low-latency match capacity worldwide. The API drives build upload, fleet creation, and scaling so studios can spin up regional capacity for launch windows or events without operating their own datacenters. Fleets support on-demand and Spot instances to balance reliability with cost.

Create a fleet named eu-prod from build build-abc with EC2 instance type c5.large and target 10 instances in region eu-west-1.

FlexMatch Matchmaking

Multiplayer titles use GameLift FlexMatch to assemble matches from queued players based on skill, latency, and party composition rules. The API creates matchmaking tickets, monitors their status, and accepts or rejects matches once players are assembled. FlexMatch evaluates rule sets server-side so studios do not need to operate their own matchmaking workers.

Start a FlexMatch ticket with configuration RankedSquad-1v1 and player attributes skill=1500 and region=eu-west.

Game Session Placement Queues

Operations teams use GameLift queues to place game sessions across multiple fleets and regions, prioritising destinations by player latency. The API submits placement requests and reports back a session endpoint once capacity is found, with fallback to other regions if the primary fleet is full. Queues smooth match flow during peak load.

Start a game session placement on queue prod-global for 4 players with latency policy that prefers region eu-west-1 under 50ms.

Agent-Driven Match Operations via Jentic

AI agents use the GameLift API through Jentic to handle live operations such as scaling fleets ahead of expected player demand, adjusting matchmaking rule sets, and rolling builds via aliases. Jentic exposes GameLift operations as discoverable tools so an agent can search by intent and execute the matching call. This compresses operator response time during launch and event spikes.

Search Jentic for create gamelift fleet, load the CreateFleet schema, and execute it for build build-abc, instance type c5.xlarge, and target 20 instances in us-east-1.

Key Endpoints

104 endpoints — jentic publishes the only available openapi specification for amazon gamelift, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=GameLift.CreateBuild

POST

/#X-Amz-Target=GameLift.CreateFleet

Create a fleet of game server instances

POST

/#X-Amz-Target=GameLift.CreateGameSession

Start a new game session

POST

/#X-Amz-Target=GameLift.CreateGameServerGroup

Create a FleetIQ game server group

POST

/#X-Amz-Target=GameLift.AcceptMatch

Accept or reject a FlexMatch proposal

POST

/#X-Amz-Target=GameLift.CreateAlias

Create an alias that routes to a fleet

POST

/#X-Amz-Target=GameLift.ClaimGameServer

Claim a FleetIQ game server for a player

POST

/#X-Amz-Target=GameLift.CreateBuild

POST

/#X-Amz-Target=GameLift.CreateFleet

Create a fleet of game server instances

POST

/#X-Amz-Target=GameLift.CreateGameSession

Start a new game session

POST

/#X-Amz-Target=GameLift.CreateGameServerGroup

Create a FleetIQ game server group

POST

/#X-Amz-Target=GameLift.AcceptMatch

Accept or reject a FlexMatch proposal

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys for GameLift are stored encrypted in the Jentic vault. Agents receive scoped, short-lived signing access — raw secret access keys never enter the agent context.

Intent-based discovery

Agents search by intent (for example create a game server fleet) and Jentic returns matching GameLift operations with their input schemas, so the agent can call the right endpoint without browsing AWS docs.

Time to first call

Direct GameLift integration: 2-4 days for SigV4 signing, fleet config, and matchmaking ticket polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amazon EC2

Provides the underlying instances that GameLift fleets run on

Choose EC2 when you need to inspect or modify the instance-level networking and security groups around a fleet.

Complementary

AWS Lambda

Runs custom logic in response to GameLift events

Choose Lambda when you need to react to fleet scaling or matchmaking events with custom code.

Complementary

Amazon EventBridge

Routes GameLift state-change events into downstream automation

Choose EventBridge when GameLift events should trigger workflows in other AWS services without polling.

FAQs

Specific to using Amazon GameLift API through Jentic.

Why is there no official OpenAPI spec for Amazon GameLift?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon GameLift via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Amazon GameLift API use?

GameLift uses AWS Signature Version 4 request signing. Through Jentic, AWS access keys are stored encrypted in the vault and signing happens server-side, so the agent never sees the raw secret access key.

Can I run FlexMatch matchmaking with this API?

Yes. StartMatchmaking submits a ticket against a matchmaking configuration with player attributes. AcceptMatch and DescribeMatchmaking complete the flow once FlexMatch proposes a match assembled from queued players.

What are the rate limits for the Amazon GameLift API?

AWS applies per-account, per-region throttling. Mutating fleet operations and DescribeGameSessions have separate throttling buckets. Use exponential backoff on ThrottlingException responses; AWS does not publish exact TPS numbers in the spec.

How do I create a game server fleet through Jentic?

Search Jentic for create gamelift fleet, load the CreateFleet schema, and execute it with build ID, EC2 instance type, runtime configuration, and target instance count. Jentic returns the new fleet ID and status.

Does this API host the game session network traffic itself?

No. This API manages fleets, sessions, and matchmaking. Actual gameplay packets flow directly between clients and game server processes running on the fleet's EC2 instances using the ports configured in the fleet.