Errors

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

ClientException

These errors are usually caused by a client action, such as using an action or
resource on behalf of a user that doesn't have permissions to use the action or
resource, or specifying an identifier that is not valid.

HTTP Status Code: 400

ClusterNotFoundException

The specified cluster could not be found. You can view your available clusters with
ListClusters. Amazon ECS clusters are region-specific.

HTTP Status Code: 400

InvalidParameterException

The specified parameter is invalid. Review the available parameters for the API
request.

HTTP Status Code: 400

ServerException

These errors are usually caused by a server issue.

HTTP Status Code: 500

Example

In the following example or examples, the Authorization header contents
(AUTHPARAMS) must be replaced with an AWS Signature Version 4
signature. For more information, see Signature
Version 4 Signing Process in the AWS General
Reference.

You only need to learn how to sign HTTP requests if you intend to
create them manually. When you use the AWS Command Line
Interface (AWS CLI) or one of the AWS SDKs to make requests to AWS, these tools automatically sign the
requests for you, with the access key that you specify when you configure the tools.
When you use these tools, you don't have to sign requests
yourself.

Example

This example request provides descriptive information about a task with an
ID of 1dc5c17a-422b-4dc4-b493-371970c6c4d6 in the default
cluster.