- Newest
- Most votes
- Most comments
Based on the available information about AWS MediaConvert, the service does not provide direct configuration options to control the Content-Type metadata that gets set when output files are written to S3. MediaConvert focuses on the transcoding process itself - converting input media to the specified output formats with the codecs and containers you configure.
The Content-Type metadata issue you're experiencing appears to be related to how MediaConvert handles metadata when writing files to S3, rather than a configurable setting in the transcoding job itself. While you can specify the audio codec (Vorbis) and container format (OGG) in MediaConvert's settings, there isn't a documented way to explicitly set the S3 object's Content-Type header during the transcoding job creation.
Your current workaround of manually updating the S3 object metadata after transcoding is a valid approach. To automate this and avoid manual post-processing, you could consider implementing an automated solution using AWS Lambda. You could set up an S3 event notification that triggers a Lambda function whenever MediaConvert writes a new file to your output bucket. The Lambda function could then automatically update the Content-Type metadata to audio/ogg for files with the .ogg extension.
This would allow you to maintain the correct Content-Type without manual intervention while working within the current capabilities of MediaConvert's S3 integration.
Sources
Migrating workflows from Elastic Transcoder to Amazon Elemental MediaConvert | AWS for M&E Blog
Tutorial: Batch-transcoding videos with S3 Batch Operations - Amazon Simple Storage Service
What tool are you using to inspect resulted content? Mediainfo is showing: Internet media type : audio/vorbis
answered 7 months ago
Relevant content
asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
The issue is not with the file itself, the file itself is the way it's supposed to be - the issue is with it being saved in S3, it adds a Content Type of type video/webm although the file is audio/vorbis, content type which is system generated. As we have an event drived design, we have certain flows that are based on the Content Type, which lead to us needing to trigger a lambda to change it afterwards. It seems inaccurate that the MediaConvert job itself would produce an audio/vorbis file but label it as an video/webm.