When Elastic Transcoder encounters an error while processing your job, it reports the error in two ways:
• Job Status and Output Status: Elastic Transcoder sets the Job:Status object and the
Outputs:Status object for the failed output to Error. In addition, Elastic Transcoder sets the Outputs:StatusDetail JSON object for the failed output to a value that explains the failure.
• SNS Notification: If you configured the pipeline to send an SNS notification when Elastic Transcoder encounters an error during processing, Elastic Transcoder includes a JSON object in the notification in the following format:
{
"state" : "PROGRESSING|COMPLETED|WARNING|ERROR", "errorCode" : "the code of any error that occurred",
"messageDetails" : "the notification message you created in Amazon SNS", "version" : "API version that you used to create the job",
"jobId" : "value of Job:Id object that Elastic Transcoder returns in the response to a Create Job request", "pipelineId" : "value of PipelineId object
in the Create Job request", "input" : {
job Input settings },
"outputKeyPrefix" : "prefix for file names in Amazon S3 bucket", "outputs": [
{
applicable job Outputs settings,
"status" : "Progressing|Complete|Warning|Error"
},
],
"userMetadata": {
"metadata key": "metadata value"
}
1000 Validation Error While processing the job, Elastic Transcoder determined that one or more values in the request were invalid.
1001 Dependency Error Elastic Transcoder could not generate the playlist because it encountered an error with one or more of the playlists dependencies.
2000 Cannot Assume Role Elastic Transcoder cannot assume the AWS Identity and Access Management role that is specified in the Role object in the pipeline for this job.
3000 Unclassified Storage
Error
3001 Input Does Not Exist No file exists with the name that you specified in the Input:Key object for this job. The file must exist in the Amazon S3 bucket that is specified in the InputBucket object in the pipeline for this job.
3002 Output Already Exists A file already exists with the name that you specified in the Outputs:Key (or Output:Key) object for this job. The file cannot exist in the Amazon S3 bucket that is specified in the OutputBucket object in the pipeline for this job.
3003 Does Not Have Read
Permission The IAM role specified in the Role object in the pipeline that you used for this job doesn't have permission to read from the Amazon S3 bucket that contains the file you want to transcode.
3004 Does Not Have Write
Permission The IAM role specified in the Role object in the pipeline that you used for this job doesn't have permission to write to the Amazon S3 bucket in which you want to save either transcoded files or thumbnail files.
3005 Bucket Does Not Exist The specified S3 bucket does not exist: bucket={1}.
3006 Does Not Have Write
Permission Elastic Transcoder was unable to write the key={1} to
bucket={2}, as the key is not in the same region as the bucket 4000 Bad Input File The file that you specified in the Input:Key object for this
job is in a format that is currently not supported by Elastic Transcoder.
4001 Bad Input File The width x height of the file that you specified in the Input:Key object for this job exceeds the maximum allowed width x height.
4002 Bad Input File The file size of the file that you specified in the Input:Key object for this job exceeds the maximum allowed size.
Value of errorCode
Value of
messageDetails
Cause
4003 Bad Input File Elastic Transcoder couldn't interpret the file that you specified in one of the Outputs:Watermarks:InputKey objects for this job.
4004 Bad Input File The width x height of a file that you specified in one of the Outputs:Watermarks:InputKey objects for this job exceeds the maximum allowed width x height.
4005 Bad Input File The size of a file that you specified for one of the {1} objects exceeds the maximum allowed size: bucket={2}, key={3}, size{4}, max size={5}.
4006 Bad Input File Elastic Transcoder could not transcode the input file because the format is not supported.
4007 Unhandled Input File Elastic Transcoder encountered a file type that is generally supported, but was unable to process the file correctly. This error automatically opened a support case, and we have started to research the cause of the problem.
4008 Bad Input File The underlying cause of this is a mismatch between the preset and the input file. Examples include:
• The preset includes audio settings, but the input file lacks audio.
• The preset includes video settings, but the input file lacks video.
4009 Bad Input File Elastic Transcoder was unable to insert all of your album art into the output file because you exceeded the maximum number of artwork streams.
4010 Bad Input File Elastic Transcoder could not interpret the graphic file you specified for AlbumArt:Artwork:InputKey.
4011 Bad Input File Elastic Transcoder detected an embedded artwork stream, but could not interpret it.
4012 Bad Input File The image that you specified for AlbumArt:Artwork exceeds the maximum allowed width x height: 4096 x 3072.
4013 Bad Input File The width x height of the embedded artwork exceeds the maximum allowed width x height: 4096 x 3072.
4014 Bad Input The value that you specified for starting time of a clip is after the end of the input file. Elastic Transcoder could not create an output file.
4015 Bad Input Elastic Transcoder could not generate a manifest file because the generated segments did not match.
4016 Bad Input Elastic Transcoder could not decrypt the input file from {1}
using {2}.
Value of errorCode
Value of
messageDetails
Cause
4017 Bad Input The AES key was encrypted with a {2}-bit encryption key.
AES supports only 128-, 192-, and 256-bit encryption keys.
MD5={1}.
4018 Bad Input Elastic Transcoder was unable to decrypt the ciphered key with MD5={1}
4019 Bad Input Elastic Transcoder was unable to generate a data key using the KMS key ARN {0}.
4020 Bad Input Your key must be 128 bits for AES-128 encryption. MD5={1}, {2} bits.
4021 Bad Input Your key must be 128 bits for PlayReady DRM. MD5={1}, strength={2} bits.
4022 Bad Input The combined size of the {1} specified media files exceeds the maximum allowed size: bucket={2}, size={3}.
4023 Bad Input The {1} input files specified for concatenation will not create an output with a consistent resolution with the specified preset.
Use a preset with different PaddingPolicy, SizingPolicy, MaxWidth, and MaxHeight settings.
4024 Bad Input The {1} input files specified for concatenation will not create thumbnails with a consistent resolution with the specified preset. Use a preset with different thumbnail PaddingPolicy, SizingPolicy, MaxWidth, and MaxHeight settings.
4025 Bad Input At least one media file (input #{1}) doesn't match the others.
All media files must have either video or no video.
4026 Bad Input At least one media file (input #{1}) doesn't match the others.
All media files must have either audio or no audio.
4100 Bad Input File Elastic Transcoder detected an embedded caption track but could not interpret it.
4101 Bad Input File Elastic Transcoder could not interpret the specified caption file for Amazon S3 bucket={1}, key={2}.
4102 Bad Input File Elastic Transcoder could not interpret the specified caption file since it was not UTF-8 encoded: Amazon S3 bucket={1}, key={2}.
4103 Bad Input File Elastic Transcoder was unable to process all of your caption tracks because you exceeded {1}, the maximum number of caption tracks.
4104 Bad Input File Elastic Transcoder could not generate a master playlist because the desired output contains {1} embedded captions, when the maximum is 4.
4105 Bad Input File Elastic Transcoder cannot embed your caption tracks because frame rate {1} is not supported for CEA-708 - only frame rates [29.97, 30] are supported.
Value of errorCode
Value of
messageDetails
Cause
4106 Bad Input File Elastic Transcoder cannot embed your caption tracks because format {1} supports only {2} caption track(s).
9000 Internal Service Error 9001 Internal Service Error 9999 Internal Service Error