Getting Started with MediaConvert Using the API
This section shows you how to get started with the MediaConvert API to transcode media files using API calls.
To get set up to use the AWS Elemental MediaConvert API
-
Set up permissions:
-
Permissions that the AWS Elemental MediaConvert service can assume on your behalf. These allow access to your Amazon S3 buckets and to Amazon API Gateway. For instructions, see Set Up IAM Permissions
in the AWS Elemental MediaConvert User Guide. -
Your Signature Version 4
authentication for the requests that you send to Amazon. When you use the Amazon Command Line Interface (Amazon CLI) or one of the Amazon SDKs, these tools automatically sign the requests for you with the access key and secret key that you specify in your client configuration.
-
-
Set up S3 file locations.
The service reads your input files from and saves your output files to Amazon S3 buckets. For instructions on creating these buckets, see Create Storage for Files
in the AWS Elemental MediaConvert User Guide. -
Send your transcoding requests.
Send your requests to manage transcoding jobs, queues, job templates, and presets. For more information, see the following:
-
For information about setting up your transcoding job, see the Creating Your Job Specification topic of this guide.
-
For general information about how the MediaConvert resources (jobs, queues, job templates, and output presets) work, see the AWS Elemental MediaConvert User Guide.
-
For information about interacting programmatically with each resource type, see the Resources topic of this guide.
-
For detailed information about each transcoding setting, see the Properties topic of the Jobs resource chapter of this guide. You might find it easiest to navigate to a particular setting in the Properties topic by following the links in the Schemas section.
-
To prevent duplicate jobs from being created, use client request tokens. For more information see Preventing duplicate jobs.
-