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

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

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

   • For information about setting up permissions for yourself, see Overview of Identity Management: Users in the IAM User Guide.

   • For information about setting up permissions for the service to access your resources, see Set Up IAM Permissions in the MediaConvert User Guide.

2. In your client configuration, specify your authentication credentials and your AWS 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 AWS CLI or SDK guides:

   • AWS CLI

   • C++: credentials and Region

   • Go

   • Java

   • JavaScript

   • .NET

   • PHP

   • Python: credentials and Region

   • Ruby

   • Tools for PowerShell

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

   With most AWS 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 AWS 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 AWS Region and won't change.

   Don't use DescribeEndpoints to create your AWS 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 AWS CLI and AWS 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 AWS CLI, you must change those to "settings" and "timecodeConfig" for your call through the AWS SDK for JavaScript.