openapi: 3.0.0
info:
version: 2015-10-01
x-release: v4
title: Amazon GameLift
description: <p>Amazon GameLift provides solutions for hosting session-based multiplayer game servers in the cloud, including tools for deploying, operating, and scaling game servers. Built on
Amazon Web Services global computing infrastructure, GameLift helps you deliver high-performance, high-reliability, low-cost game servers while dynamically scaling your resource usage to meet
player demand. </p> <p> <b>About Amazon GameLift solutions</b> </p> <p>Get more information on these Amazon GameLift solutions in the <a
href="https://docs.aws.amazon.com/gamelift/latest/developerguide/">Amazon GameLift Developer Guide</a>.</p> <ul> <li> <p>Amazon GameLift managed hosting -- Amazon GameLift offers a fully managed
service to set up and maintain computing machines for hosting, manage game session and player session life cycle, and handle security, storage, and performance tracking. You can use automatic
scaling tools to balance player demand and hosting costs, configure your game session management to minimize player latency, and add FlexMatch for matchmaking.</p> </li> <li> <p>Managed hosting
with Realtime Servers -- With Amazon GameLift Realtime Servers, you can quickly configure and set up ready-to-go game servers for your game. Realtime Servers provides a game server framework with
core Amazon GameLift infrastructure already built in. Then use the full range of Amazon GameLift managed hosting features, including FlexMatch, for your game.</p> </li> <li> <p>Amazon GameLift
FleetIQ -- Use Amazon GameLift FleetIQ as a standalone service while hosting your games using EC2 instances and Auto Scaling groups. Amazon GameLift FleetIQ provides optimizations for game
hosting, including boosting the viability of low-cost Spot Instances gaming. For a complete solution, pair the Amazon GameLift FleetIQ and FlexMatch standalone services.</p> </li> <li> <p>Amazon
GameLift FlexMatch -- Add matchmaking to your game hosting solution. FlexMatch is a customizable matchmaking service for multiplayer games. Use FlexMatch as integrated with Amazon GameLift managed
hosting or incorporate FlexMatch as a standalone service into your own hosting solution.</p> </li> </ul> <p> <b>About this API Reference</b> </p> <p>This reference guide describes the low-level
service API for Amazon GameLift. With each topic in this guide, you can find links to language-specific SDK guides and the Amazon Web Services CLI reference. Useful links:</p> <ul> <li> <p> <a
href="https://docs.aws.amazon.com/gamelift/latest/developerguide/reference-awssdk.html">Amazon GameLift API operations listed by tasks</a> </p> </li> <li> <p> <a
href="https://docs.aws.amazon.com/gamelift/latest/developerguide/gamelift-components.html"> Amazon GameLift tools and resources</a> </p> </li> </ul>
x-logo:
url: https://api.apis.guru/v2/cache/logo/https_twitter.com_awscloud_profile_image.png
backgroundColor: "#FFFFFF"
termsOfService: https://aws.amazon.com/service-terms/
contact:
name: Mike Ralphson
email: mike.ralphson@gmail.com
url: https://github.com/mermade/aws2openapi
x-twitter: PermittedSoc
license:
name: Apache 2.0 License
url: http://www.apache.org/licenses/
x-providerName: amazonaws.com
x-serviceName: gamelift
x-origin:
- contentType: application/json
url: https://raw.githubusercontent.com/aws/aws-sdk-js/master/apis/gamelift-2015-10-01.normal.json
converter:
url: https://github.com/mermade/aws2openapi
version: 1.0.0
x-apisguru-driver: external
x-apiClientRegistration:
url: https://portal.aws.amazon.com/gp/aws/developer/registration/index.html?nc2=h_ct
x-apisguru-categories:
- cloud
x-preferred: true
externalDocs:
description: Amazon Web Services documentation
url: https://docs.aws.amazon.com/gamelift/
servers:
- url: http://gamelift.{region}.amazonaws.com
variables:
region:
description: The AWS region
enum:
- us-east-1
- us-east-2
- us-west-1
- us-west-2
- us-gov-west-1
- us-gov-east-1
- ca-central-1
- eu-north-1
- eu-west-1
- eu-west-2
- eu-west-3
- eu-central-1
- eu-south-1
- af-south-1
- ap-northeast-1
- ap-northeast-2
- ap-northeast-3
- ap-southeast-1
- ap-southeast-2
- ap-east-1
- ap-south-1
- sa-east-1
- me-south-1
default: us-east-1
description: The Amazon GameLift multi-region endpoint
- url: https://gamelift.{region}.amazonaws.com
variables:
region:
description: The AWS region
enum:
- us-east-1
- us-east-2
- us-west-1
- us-west-2
- us-gov-west-1
- us-gov-east-1
- ca-central-1
- eu-north-1
- eu-west-1
- eu-west-2
- eu-west-3
- eu-central-1
- eu-south-1
- af-south-1
- ap-northeast-1
- ap-northeast-2
- ap-northeast-3
- ap-southeast-1
- ap-southeast-2
- ap-east-1
- ap-south-1
- sa-east-1
- me-south-1
default: us-east-1
description: The Amazon GameLift multi-region endpoint
- url: http://gamelift.{region}.amazonaws.com.cn
variables:
region:
description: The AWS region
enum:
- cn-north-1
- cn-northwest-1
default: cn-north-1
description: The Amazon GameLift endpoint for China (Beijing) and China (Ningxia)
- url: https://gamelift.{region}.amazonaws.com.cn
variables:
region:
description: The AWS region
enum:
- cn-north-1
- cn-northwest-1
default: cn-north-1
description: The Amazon GameLift endpoint for China (Beijing) and China (Ningxia)
x-hasEquivalentPaths: true
paths:
/#X-Amz-Target=GameLift.AcceptMatch:
post:
operationId: AcceptMatch
description: "<p>Registers a player's acceptance or rejection of a proposed FlexMatch match. A matchmaking configuration may require player acceptance; if so, then matches built with that configuration
cannot be completed unless all players accept the proposed match within a specified time limit. </p> <p>When FlexMatch builds a match, all the matchmaking tickets involved in the proposed match
are placed into status <code>REQUIRES_ACCEPTANCE</code>. This is a trigger for your game to get acceptance from all players in the ticket. Acceptances are only valid for tickets when they are in
this status; all other acceptances result in an error.</p> <p>To register acceptance, specify the ticket ID, a response, and one or more players. Once all players have registered acceptance, the
matchmaking tickets advance to status <code>PLACING</code>, where a new game session is created for the match. </p> <p>If any player rejects the match, or if acceptances are not received before
a specified timeout, the proposed match is dropped. The matchmaking tickets are then handled in one of two ways: For tickets where one or more players rejected the match or failed to respond, the
ticket status is set to <code>CANCELLED</code>, and processing is terminated. For tickets where players have accepted or not yet responded, the ticket status is returned to <code>SEARCHING</code>
to find a new match. A new matchmaking request for these players can be submitted as needed. </p> <p> <b>Learn more</b> </p> <p> <a href=\"https://docs.aws.amazon.com/gamelift/latest/flexmatchguide/match-client.html\"\
> Add FlexMatch to a game client</a> </p> <p> <a href=\"https://docs.aws.amazon.com/gamelift/latest/flexmatchguide/match-events.html\"> FlexMatch events</a> (reference)</p>"
responses:
"200":
description: Success
content:
application/json:
schema:
$ref: "#/components/schemas/AcceptMatchOutput"
examples:
AcceptMatch200Example:
summary: Default AcceptMatch 200 response
x-microcks-default: true
value: {}
"480":
description: InvalidRequestException
content:
application/json:
schema:
$ref: "#/components/schemas/InvalidRequestException"
examples:
AcceptMatch480Example:
summary: Default AcceptMatch 480 response
x-microcks-default: true
value: example-value
"481":
description: NotFoundException
content:
application/json:
schema:
$ref: "#/components/schemas/NotFoundException"
examples:
AcceptMatch481Example:
summary: Default AcceptMatch 481 response
x-microcks-default: true
value: example-value
"482":
description: InternalServiceException
content:
application/json:
schema:
$ref: "#/components/schemas/InternalServiceException"
examples:
AcceptMatch482Example:
summary: Default AcceptMatch 482 response
x-microcks-default: true
value: example-value
"483":
description: UnsupportedRegionException
content:
application/json:
schema:
$ref: "#/components/schemas/UnsupportedRegionException"
examples:
AcceptMatch483Example:
summary: Default AcceptMatch 483 response
x-microcks-default: true
value: example-value
requestBody:
required: true
content:
application/json:
schema:
$ref: "#/components/schemas/AcceptMatchInput"
parameters:
- name: X-Amz-Target
in: header
required: true
schema:
type: string
enum:
- GameLift.AcceptMatch
summary: Amazon GameLift Accept Match
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
parameters:
- $ref: "#/components/parameters/X-Amz-Content-Sha256"
- $ref: "#/components/parameters/X-Amz-Date"
- $ref: "#/components/parameters/X-Amz-Algorithm"
- $ref: "#/components/parameters/X-Amz-Credential"
- $ref: "#/components/parameters/X-Amz-Security-Token"
- $ref: "#/components/parameters/X-Amz-Signature"
- $ref: "#/components/parameters/X-Amz-SignedHeaders"
/#X-Amz-Target=GameLift.ClaimGameServer:
post:
operationId: ClaimGameServer
description: <p> <b>This operation is used with the Amazon GameLift FleetIQ solution and game server groups.</b> </p> <p>Locates an available game server and temporarily reserves it to host
gameplay and players. This operation is called from a game client or client service (such as a matchmaker) to request hosting resources for a new game session. In response, Amazon GameLift
FleetIQ locates an available game server, places it in <code>CLAIMED</code> status for 60 seconds, and returns connection information that players can use to connect to the game server. </p>
<p>To claim a game server, identify a game server group. You can also specify a game server ID, although this approach bypasses Amazon GameLift FleetIQ placement optimization. Optionally,
include game data to pass to the game server at the start of a game session, such as a game map or player information. </p> <p>When a game server is successfully claimed, connection
information is returned. A claimed game server's utilization status remains <code>AVAILABLE</code> while the claim status is set to <code>CLAIMED</code> for up to 60 seconds. This time period
gives the game server time to update its status to <code>UTILIZED</code> after players join. If the game server's status is not updated within 60 seconds, the game server reverts to unclaimed
status and is available to be claimed by another request. The claim time period is a fixed value and is not configurable.</p> <p>If you try to claim a specific game server, this request will
fail in the following cases:</p> <ul> <li> <p>If the game server utilization status is <code>UTILIZED</code>.</p> </li> <li> <p>If the game server claim status is <code>CLAIMED</code>.</p>
</li> </ul> <note> <p>When claiming a specific game server, this request will succeed even if the game server is running on an instance in <code>DRAINING</code> status. To avoid this, first
check the instance status by calling <a href="https://docs.aws.amazon.com/gamelift/latest/apireference/API_DescribeGameServerInstances.html">DescribeGameServerInstances</a> .</p> </note> <p>
<b>Learn more</b> </p> <p> <a href="https://docs.aws.amazon.com/gamelift/latest/fleetiqguide/gsg-intro.html">Amazon GameLift FleetIQ Guide</a> </p>
responses:
"200":
description: Success
content:
application/json:
schema:
$ref: "#/components/schemas/ClaimGameServerOutput"
examples:
ClaimGameServer200Example:
summary: Default ClaimGameServer 200 response
x-microcks-default: true
value:
GameServer: example-value
"480":
description: InvalidRequestException
content:
application/json:
schema:
$ref: "#/components/schemas/InvalidRequestException"
examples:
ClaimGameServer480Example:
summary: Default ClaimGameServer 480 response
x-microcks-default: true
value: example-value
"481":
description: NotFoundException
content:
application/json:
schema:
$ref: "#/components/schemas/NotFoundException"
examples:
ClaimGameServer481Example:
summary: Default ClaimGameServer 481 response
x-microcks-default: true
value: example-value
"482":
description: ConflictException
content:
application/json:
schema:
$ref: "#/components/schemas/ConflictException"
examples:
ClaimGameServer482Example:
summary: Default ClaimGameServer 482 response
x-microcks-default: true
value: example-value
"483":
description: OutOfCapacityException
content:
application/json:
schema:
$ref: "#/components/schemas/OutOfCapacityException"
examples:
ClaimGameServer483Example:
summary: Default ClaimGameServer 483 response
x-microcks-default: true
value: example-value
"484":
description: UnauthorizedException
content:
application/json:
schema:
$ref: "#/components/schemas/UnauthorizedException"
examples:
ClaimGameServer484Example:
summary: Default ClaimGameServer 484 response
x-microcks-default: true
value: example-value
"485":
description: InternalServiceException
content:
application/json:
schema:
$ref: "#/components/schemas/InternalServiceException"
examples:
ClaimGameServer485Example:
summary: Default ClaimGameServer 485 response
x-microcks-default: true
value: example-value
requestBody:
required: true
content:
application/json:
schema:
$ref: "#/components/schemas/ClaimGameServerInput"
parameters:
- name: X-Amz-Target
in: header
required: true
schema:
type: string
enum:
- GameLift.ClaimGameServer
summary: Amazon GameLift Claim Game Server
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
parameters:
- $ref: "#/components/parameters/X-Amz-Content-Sha256"
- $ref: "#/components/parameters/X-Amz-Date"
- $ref: "#/components/parameters/X-Amz-Algorithm"
- $ref: "#/components/parameters/X-Amz-Credential"
- $ref: "#/components/parameters/X-Amz-Security-Token"
- $ref: "#/components/parameters/X-Amz-Signature"
- $ref: "#/components/parameters/X-Amz-SignedHeaders"
/#X-Amz-Target=GameLift.CreateAlias:
post:
operationId: CreateAlias
description: '<p>Creates an alias for a fleet. In most situations, you can use an alias ID in place of a fleet ID. An alias provides a level of abstraction for a fleet that is useful when redirecting
player traffic from one fleet to another, such as when updating your game build. </p> <p>Amazon GameLift supports two types of routing strategies for aliases: simple and terminal. A simple alias
points to an active fleet. A terminal alias is used to display messaging or link to a URL instead of routing players to an active fleet. For example, you might use a terminal alias when a game version
is no longer supported and you want to direct players to an upgrade site. </p> <p>To create a fleet alias, specify an alias name, routing strategy, and optional description. Each simple alias can
point to only one fleet, but a fleet can have multiple aliases. If successful, a new alias record is returned, including an alias ID and an ARN. You can reassign an alias to another fleet by calling
<code>UpdateAlias</code>.</p> <p> <b>Related actions</b> </p> <p> <a href="https://docs.aws.amazon.com/gamelift/latest/developerguide/reference-awssdk.html#reference-awssdk-resources-fleets">All
APIs by task</a> </p>'
responses:
"200":
description: Success
content:
application/json:
schema:
$ref: "#/components/schemas/CreateAliasOutput"
examples:
CreateAlias200Example:
summary: Default CreateAlias 200 response
x-microcks-default: true
value:
Alias: example-value
"480":
description: UnauthorizedException
content:
application/json:
schema:
$ref: "#/components/schemas/UnauthorizedException"
examples:
CreateAlias480Example:
summary: Default CreateAlias 480 response
x-microcks-default: true
value: example-value
"481":
description: InvalidRequestException
content:
application/json:
schema:
$ref: "#/components/schemas/InvalidRequestException"
examples:
CreateAlias481Example:
summary: Default CreateAlias 481 response
x-microcks-default: true
value: example-value
"482":
description: ConflictException
content:
application/json:
schema:
$ref: "#/components/schemas/ConflictException"
examples:
CreateAlias482Example:
summary: Default CreateAlias 482 response
x-microcks-default: true
value: example-value
"483":
description: InternalServiceException
content:
application/json:
schema:
$ref: "#/components/schemas/InternalServiceException"
examples:
CreateAlias483Example:
summary: Default CreateAlias 483 response
x-microcks-default: true
value: example-value
"484":
description: LimitExceededException
content:
application/json:
schema:
$ref: "#/components/schemas/LimitExceededException"
examples:
CreateAlias484Example:
summary: Default CreateAlias 484 response
x-microcks-default: true
value: example-value
"485":
description: TaggingFailedException
content:
application/json:
schema:
$ref: "#/components/schemas/TaggingFailedException"
examples:
CreateAlias485Example:
summary: Default CreateAlias 485 response
x-microcks-default: true
value: example-value
requestBody:
required: true
content:
application/json:
schema:
$ref: "#/components/schemas/CreateAliasInput"
parameters:
- name: X-Amz-Target
in: header
required: true
schema:
type: string
enum:
- GameLift.CreateAlias
summary: Amazon GameLift Create Alias
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
parameters:
- $ref: "#/components/parameters/X-Amz-Content-Sha256"
- $ref: "#/components/parameters/X-Amz-Date"
- $ref: "#/components/parameters/X-Amz-Algorithm"
- $ref: "#/components/parameters/X-Amz-Credential"
- $ref: "#/components/parameters/X-Amz-Security-Token"
- $ref: "#/components/parameters/X-Amz-Signature"
- $ref: "#/components/parameters/X-Amz-SignedHeaders"
/#X-Amz-Target=GameLift.CreateBuild:
post:
operationId: CreateBuild
description: "<p>Creates a new Amazon GameLift build resource for your game server binary files. Combine game server binaries into a zip file for use with Amazon GameLift. </p> <important> <p>When
setting up a new game build for Amazon GameLift, we recommend using the CLI command <b> <a href=\"https://docs.aws.amazon.com/cli/latest/reference/gamelift/upload-build.html\">upload-build</a> </b>.
This helper command combines two tasks: (1) it uploads your build files from a file directory to a Amazon GameLift Amazon S3 location, and (2) it creates a new build resource.</p> </important> <p>You
can use the operation in the following scenarios:</p> <ul> <li> <p>To create a new game build with build files that are in an Amazon S3 location under an Amazon Web Services account that you control.
To use this option, you give Amazon GameLift access to the Amazon S3 bucket. With permissions in place, specify a build name, operating system, and the Amazon S3 storage location of your game build.</p>
</li> <li> <p>To directly upload your build files to a Amazon GameLift Amazon S3 location. To use this option, specify a build name and operating system. This operation creates a new build resource
and also returns an Amazon S3 location with temporary access credentials. Use the credentials to manually upload your build files to the specified Amazon S3 location. For more information, see <a
href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UploadingObjects.html\">Uploading Objects</a> in the <i>Amazon S3 Developer Guide</i>. After you upload build files to the Amazon GameLift
Amazon S3 location, you can't update them. </p> </li> </ul> <p>If successful, this operation creates a new build resource with a unique build ID and places it in <code>INITIALIZED</code> status.
A build must be in <code>READY</code> status before you can create fleets with it.</p> <p> <b>Learn more</b> </p> <p> <a href=\"https://docs.aws.amazon.com/gamelift/latest/developerguide/gamelift-build-intro.html\"\
>Uploading Your Game</a> </p> <p> <a href=\"https://docs.aws.amazon.com/gamelift/latest/developerguide/gamelift-build-cli-uploading.html#gamelift-build-cli-uploading-create-build\"> Create a Build
with Files in Amazon S3</a> </p> <p> <a href=\"https://docs.aws.amazon.com/gamelift/latest/developerguide/reference-awssdk.html#reference-awssdk-resources-fleets\">All APIs by task</a> </p>"
responses:
"200":
description: Success
content:
application/json:
schema:
$ref: "#/components/schemas/CreateBuildOutput"
examples:
CreateBuild200Example:
summary: Default CreateBuild 200 response
x-microcks-default: true
value:
Build: example-value
UploadCredentials: example-value
StorageLocation: example-value
"480":
description: UnauthorizedException
content:
application/json:
schema:
$ref: "#/components/schemas/UnauthorizedException"
examples:
CreateBuild480Example:
summary: Default CreateBuild 480 response
x-microcks-default: true
value: example-value
"481":
description: InvalidRequestException
content:
application/json:
schema:
$ref: "#/components/schemas/InvalidRequestException"
examples:
CreateBuild481Example:
summary: Default CreateBuild 481 response
x-microcks-default: true
value: example-value
"482":
description: ConflictException
content:
application/json:
schema:
$ref: "#/components/schemas/ConflictException"
examples:
CreateBuild482Example:
summary: Default CreateBuild 482 response
x-microcks-default: true
value: example-value
"483":
description: TaggingFailedException
content:
application/json:
schema:
$ref: "#/components/schemas/TaggingFailedException"
examples:
CreateBuild483Example:
summary: Default CreateBuild 483 response
x-microcks-default: true
value: example-value
"484":
description: InternalServiceException
content:
application/json:
schema:
$ref: "#/components/schemas/InternalServiceException"
examples:
CreateBuild484Example:
summary: Default CreateBuild 484 response
x-microcks-default: true
value: example-value
requestBody:
required: true
content:
application/json:
schema:
$ref: "#/components/schemas/CreateBuildInput"
parameters:
- name: X-Amz-Target
in: header
required: true
schema:
type: string
enum:
- GameLift.CreateBuild
summary: Amazon GameLift Create Build
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
parameters:
- $ref: "#/components/parameters/X-Amz-Content-Sha256"
- $ref: "#/components/parameters/X-Amz-Date"
- $ref: "#/components/parameters/X-Amz-Algorithm"
- $ref: "#/components/parameters/X-Amz-Credential"
- $ref: "#/components/parameters/X-Amz-Security-Token"
- $ref: "#/components/parameters/X-Amz-Signature"
- $ref: "#/components/parameters/X-Amz-SignedHeaders"
/#X-Amz-Target=GameLift.CreateFleet:
post:
operationId: CreateFleet
description: "<p>Creates a fleet of Amazon Elastic Compute Cloud (Amazon EC2) instances to host your custom game server or Realtime Servers. Use this operation to configure the computing resources
for your fleet and provide instructions for running game servers on each instance.</p> <p>Most Amazon GameLift fleets can deploy instances to multiple locations, including the home Region (where
the fleet is created) and an optional set of remote locations. Fleets that are created in the following Amazon Web Services Regions support multiple locations: us-east-1 (N. Virginia), us-west-2
(Oregon), eu-central-1 (Frankfurt), eu-west-1 (Ireland), ap-southeast-2 (Sydney), ap-northeast-1 (Tokyo), and ap-northeast-2 (Seoul). Fleets that are created in other Amazon GameLift Regions can
deploy instances in the fleet's home Region only. All fleet instances use the same configuration regardless of location; however, you can adjust capacity settings and turn auto-scaling on/off for
each location.</p> <p>To create a fleet, choose the hardware for your instances, specify a game server build or Realtime script to deploy, and provide a runtime configuration to direct Amazon GameLift
how to start and run game servers on each instance in the fleet. Set permissions for inbound traffic to your game servers, and enable optional features as needed. When creating a multi-location
fleet, provide a list of additional remote locations.</p> <p>If you need to debug your fleet, fetch logs, view performance metrics or other actions on the fleet, create the development fleet with
port 22/3389 open. As a best practice, we recommend opening ports for remote access only when you need them and closing them when you're finished. </p> <p>If successful, this operation creates a
new Fleet resource and places it in <code>NEW</code> status, which prompts Amazon GameLift to initiate the <a href=\"https://docs.aws.amazon.com/gamelift/latest/developerguide/fleets-creating-all.html#fleets-creation-workflow\"\
>fleet creation workflow</a>.</p> <p> <b>Learn more</b> </p> <p> <a href=\"https://docs.aws.amazon.com/gamelift/latest/developerguide/fleets-intro.html\">Setting up fleets</a> </p> <p> <a href=\"\
https://docs.aws.amazon.com/gamelift/latest/developerguide/fleets-creating-debug.html#fleets-creating-debug-creation\">Debug fleet creation issues</a> </p> <p> <a href=\"https://docs.aws.amazon.com/gamelift/latest/developerguide/fleets-intro.html\"\
>Multi-location fleets</a> </p>"
responses:
"200":
description: Success
content:
application/json:
schema:
$ref: "#/components/schemas/CreateFleetOutput"
examples:
CreateFleet200Example:
summary: Default CreateFleet 200 response
x-microcks-default: true
value:
FleetAttributes: example-value
LocationStates: example-value
"480":
description: InternalServiceException
content:
application/json:
schema:
$ref: "#/components/schemas/InternalServiceException"
examples:
CreateFleet480Example:
summary: Default CreateFleet 480 response
x-microcks-default: true
value: example-value
"481":
description: NotFoundException
content:
application/json:
schema:
$ref: "#/components/schemas/NotFoundException"
examples:
CreateFleet481Example:
summary: Default CreateFleet 481 response
x-microcks-default: true
value: example-value
"482":
description: ConflictException
content:
application/json:
schema:
$ref: "#/components/schemas/ConflictException"
examples:
CreateFleet482Example:
summary: Default CreateFleet 482 response
x-microcks-default: true
value: example-value
"483":
description: LimitExceededException
content:
application/json:
schema:
$ref: "#/components/schemas/LimitExceededException"
examples:
CreateFleet483Example:
summary: Default CreateFleet 483 response
x-microcks-default: true
value: example-value
"484":
description: InvalidRequestException
content:
application/json:
schema:
# --- truncated at 32 KB (836 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/amazon-gamelift/refs/heads/main/openapi/amazon-gamelift-openapi.yaml