DeleteFleet - Amazon GameLift Service
AWS services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with AWS services in China.


Deletes everything related to a fleet. Before deleting a fleet, you must set the fleet's desired capacity to zero. See UpdateFleetCapacity.

If the fleet being deleted has a VPC peering connection, you first need to get a valid authorization (valid for 24 hours) by calling CreateVpcPeeringAuthorization. You do not need to explicitly delete the VPC peering connection--this is done as part of the delete fleet process.

This action removes the fleet and its resources. Once a fleet is deleted, you can no longer use any of the resources in that fleet.

Learn more

Setting up GameLift Fleets

Related operations

Request Syntax

{ "FleetId": "string" }

Request Parameters

For information about the parameters that are common to all actions, see Common Parameters.

The request accepts the following data in JSON format.


In the following list, the required parameters are described first.


A unique identifier for a fleet to be deleted. You can use either the fleet ID or ARN value.

Type: String

Pattern: ^fleet-\S+|^arn:.*:fleet\/fleet-\S+

Required: Yes

Response Elements

If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.


For information about the errors that are common to all actions, see Common Errors.


The service encountered an unrecoverable internal failure while processing the request. Clients can retry such requests immediately or after a waiting period.

HTTP Status Code: 500


The requested operation would cause a conflict with the current state of a resource associated with the request and/or the fleet. Resolve the conflict before retrying.

HTTP Status Code: 400


One or more parameter values in the request are invalid. Correct the invalid parameter values before retrying.

HTTP Status Code: 400


A service resource associated with the request could not be found. Clients should not retry such requests.

HTTP Status Code: 400


The requested tagging operation did not succeed. This may be due to invalid tag format or the maximum tag limit may have been exceeded. Resolve the issue before retrying.

HTTP Status Code: 400


The client failed authentication. Clients should not retry such requests.

HTTP Status Code: 400


Delete a fleet that is no longer in use

This example attempts to delete a fleet that has been scaled down to zero instances. If the fleet capacity is not zero, the request fails with an HTTP 400 error.

HTTP requests are authenticated using an AWS Signature Version 4 signature in the Authorization header field.

Sample Request

{ "FleetId": "fleet-2222bbbb-33cc-44dd-55ee-6666ffff77aa" }

Sample Response

If delete is successful: HTTP/1.1 200 OK x-amzn-RequestId: b34f8665-EXAMPLE Date: Thu, 06 Apr 2017 00:48:07 GMT If delete is not successful: Status: 400 Bad Request RequestId: 99764159-4a57-11e7-af99-e5821c0e52da Time: 177ms {"__type": "com.amazonaws.gameliftapi.v20151001#InvalidRequestException", "Message": "Unable to terminate fleet-8e5a52a6-3261-4217-9a21-938b247c3db6: Max instance count must be 0."}

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: