End of support notice: On November 13, 2025, AWS will discontinue support for Amazon Elastic Transcoder. After November 13, 2025, you will no longer be able to access the Elastic Transcoder console or Elastic Transcoder resources.
For more information about transitioning to AWS Elemental MediaConvert, visit this blog post
Delete Pipeline
Description
To delete a pipeline, send a DELETE request to the /2012-09-25/pipelines/
resource. You can only delete a pipeline that has never been used or that is not currently in use (doesn't
contain any active jobs). If the pipeline is currently in use, pipelineId
Delete Pipeline
returns an error.
Requests
Syntax
DELETE /2012-09-25/pipelines/pipelineId HTTP/1.1 Content-Type: charset=UTF-8 Accept: */* Host: elastictranscoder.
Elastic Transcoder endpoint
.amazonaws.com:443 x-amz-date: 20130114T174952Z Authorization: AWS4-HMAC-SHA256 Credential=AccessKeyID
/request-date
/Elastic Transcoder endpoint
/elastictranscoder/aws4_request, SignedHeaders=host;x-amz-date;x-amz-target, Signature=calculated-signature
Request Parameters
This operation takes the following request parameter.
- pipelineId
-
The identifier of the pipeline that you want to delete.
Request Headers
This operation uses only request headers that are common to all operations. For information about common request headers, see HTTP Header Contents.
Request Body
This operation does not have a request body.
Responses
Syntax
Status: 202 Accepted x-amzn-RequestId: c321ec43-378e-11e2-8e4c-4d5b971203e9 Content-Type: application/json Content-Length:
number of characters in the response
Date: Mon, 14 Jan 2013 06:01:47 GMT { "Success":"true" }
Response Headers
This operation uses only response headers that are common to most responses. For information about common response headers, see HTTP Responses.
Response Body
The response body contains the following JSON object.
- Success
-
If the pipeline is successfully deleted, the value of
Success
istrue
.
Errors
For information about Elastic Transcoder exceptions and error messages, see Handling Errors in Elastic Transcoder.
Example
The following example request deletes the pipeline 1111111111111-abcde1.
Sample Request
DELETE /2012-09-25/pipelines/1111111111111-abcde1 HTTP/1.1 Content-Type: charset=UTF-8 Accept: */* Host: elastictranscoder.
Elastic Transcoder endpoint
.amazonaws.com:443 x-amz-date: 20130114T174952Z Authorization: AWS4-HMAC-SHA256 Credential=AccessKeyID
/request-date
/Elastic Transcoder endpoint
/elastictranscoder/aws4_request, SignedHeaders=host;x-amz-date;x-amz-target, Signature=calculated-signature
Sample Response
Status: 202 Accepted x-amzn-RequestId: c321ec43-378e-11e2-8e4c-4d5b971203e9 Content-Type: application/json Content-Length:
number of characters in the response
Date: Mon, 14 Jan 2013 06:01:47 GMT { "Success":"true" }