Bind tags to a specified EMR cluster.
Debugging
Authorization information
There is currently no authorization information disclosed in the API.
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
RegionId | string | Yes | The ID of the region in which you want to create the instance. | cn-hangzhou |
ResourceType | string | Yes | The type of the resource to which the tag belongs. Valid values:
| cluster |
ResourceIds | array | Yes | The list of resource IDs. Valid values of N: 1 to 1. | |
String | string | Yes | The ID of a resource. If the ResourceType parameter is set to cluster, set the value to the ID of the cluster. | c-b933c5aac8fe**** |
Tags | array | Yes | The tags. | |
Tag | Tag | Yes | The tag. |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "A964BDB2-0FDA-1037-AF3F-2633D5C3F20F"
}
Error codes
HTTP status code | Error code | Error message |
---|---|---|
400 | ConflictParameters | Parameters that must not be used together. %s |
400 | IncompleteSignature | The request signature is invalid. |
400 | InvalidAction | The action %s requested is invalid. |
400 | InvalidParameter | The specified parameter %s is not valid. |
400 | InvalidParameterValue | The input parameter %s is invalid or out of range. |
400 | MissingAction | The action %s requested is missing. |
400 | MissingParameter | The input parameter %s that is mandatory for processing this request is not supplied. |
400 | NotAuthorized | You do not have permission to perform this action. %s |
400 | ThrottlingException | The request was denied due to request throttling. %s |
404 | ResourceNotFound | The resource not found by %s. |
500 | InternalError | The request processing has failed due to some unknown error, exception or failure. |
503 | ServiceFailure | The request has failed due to a temporary failure of %s service. |
503 | ServiceUnavailable | The request has failed due to a temporary failure of the server. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2023-10-23 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2021-10-12 | The Error code has changed | View Change Details |