AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Deletes all resources and information related a fleet. Any current fleet instances,
including those in remote locations, are shut down. You don't need to call
If the fleet being deleted has a VPC peering connection, you first need to get a valid
authorization (good for 24 hours) by calling CreateVpcPeeringAuthorization.
You do not need to explicitly delete the VPC peering connection.
If the fleet being deleted has a VPC peering connection, you first need to get a valid authorization (good for 24 hours) by calling CreateVpcPeeringAuthorization. You do not need to explicitly delete the VPC peering connection.
To delete a fleet, specify the fleet ID to be terminated. During the deletion process
the fleet status is changed to
DELETING. When completed, the status switches
TERMINATED and the fleet event
FLEET_DELETED is sent.
For .NET Core this operation is only available in asynchronous form. Please refer to DeleteFleetAsync.
public abstract DeleteFleetResponse DeleteFleet( String fleetId )
A unique identifier for the fleet to be deleted. You can use either the fleet ID or ARN value.
|InternalServiceException||The service encountered an unrecoverable internal failure while processing the request. Clients can retry such requests immediately or after a waiting period.|
|InvalidFleetStatusException||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.|
|InvalidRequestException||One or more parameter values in the request are invalid. Correct the invalid parameter values before retrying.|
|NotFoundException||THe requested resources was not found. The resource was either not created yet or deleted.|
|TaggingFailedException||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.|
|UnauthorizedException||The client failed authentication. Clients should not retry such requests.|
Supported in: 4.5, 4.0, 3.5