Getting Started with AWS Elemental MediaConvert Using the Amazon SDKs or the Amazon CLI - AWS Elemental MediaConvert API Reference
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Getting Started with AWS Elemental MediaConvert Using the Amazon SDKs or the Amazon CLI

To get started with AWS Elemental MediaConvert using one of the Amazon SDKS or the Amazon Command Line Interface (Amazon CLI), follow this general procedure.

  1. Set up Amazon Identity and Access Management (IAM) permissions for both yourself and for the MediaConvert service to access your resources on your behalf:

  2. In your client configuration, specify your authentication credentials and your Amazon Region. For instructions that are specific to the programming language that you use, choose from this list of links to open the relevant topics in the Amazon CLI or SDK guides:

  3. Get your Region-specific endpoint and send your MediaConvert requests to it.

    With most Amazon services, you send your service request to a public endpoint. But with MediaConvert, you request an endpoint that is specific to your Region, and then you send your service requests to that.

    This endpoint is specific to your Amazon Region and won't change. Request this endpoint once, and then hardcode or cache it.

    For information about MediaConvert FIPS endpoints, see FIPS Endpoints.

    Important

    Make the DescribeEndpoints call only once, then hardcode or cache your endpoint. This endpoint is specific to your Amazon Region and won't change.

    Don't use DescribeEndpoints to create your Amazon client each time that you make a request to MediaConvert. Otherwise, you will reach the throttle maximum on the public API endpoint.

  4. To prevent duplicate jobs from being created, use client request tokens. For more information see Preventing duplicate jobs.

Choosing the correct case for requests

When you send requests, use camelCase or PascalCase as appropriate for the language you are using. All examples in this guide use PascalCase, which is the correct casing for the Amazon CLI and Amazon SDK for Python (Boto3). The MediaConvert console JSON export function also generates JSON job specifications in PascalCase.

When you use a language that specifies camelCase, such as JavaScript, you must convert the casing of your properties before you submit your requests. For example, if you use the properties "Settings" and "TimecodeConfig" in your call through the Amazon CLI, you must change those to "settings" and "timecodeConfig" for your call through the Amazon SDK for JavaScript.