AWS Elemental MediaConvert

Introduction

AWS Elemental MediaConvert is a powerful cloud-based video transcoding service provided by Amazon Web Services (AWS). It simplifies the process of converting media files into various formats, making them compatible with a wide range of devices and streaming platforms. With MediaConvert, users can effortlessly transcode video and audio files, optimize them for different resolutions and bitrates, and apply custom settings to meet specific requirements.

You can find more details as well as a list of supported operations on AWS Elemental MediaConvert | qibb Catalog.

How to get started with AWS Elemental MediaConvert integration

Before using AWS Elemental MediaConvert integration, make sure you have the necessary permissions for the operations.

1. You need an Access key, Secret access key, and Region information of your AWS account for authentication.

2. To list the access keys for an IAM user (console), sign in to the AWS Management Console, and open the IAM console. In the navigation pane, choose Users, select the user you want, and then choose the Security credentials tab.

   

3. If you don't have an Access key and Secret access key, create a new access key. Click the Create access key button, select Application running outside AWS, and click Next.

4. You can set an optional description tag in the next page. Click the Create access key button to continue.

5. Copy your Access key and Secret access key and save it for later use. Note that you can only copy the Secret access key on this page.

   

6. In the qibb Workflow Editor, open the Node Catalog in the right sidebar and install the AWS Elemental MediaConvert node by clicking the + button.

7. Drag and drop the AWS Elemental MediaConvert node from the left sidebar to your workflow.

8. Enter your Region, Access key, Secret access key credentials to Advanced/Security fields.

   

9. Retrive AWS Elemental MediaConvert FIPS Endpoints.
   If you don't have the FIPS endpoint URL yet, you can use this AWS Elemental MediaConvert example flow. This will retrieve the URL and store it in the flow context data under the path flow.mediaconvert_endpoint.

   

   According to AWS Elemental MediaConvert documentation, developers should avoid making frequent requests to the public endpoint.

If you request your endpoint programmatically, do so only once in your application. Don't make a request to the public endpoint each time that you make a request to MediaConvert. Otherwise, you will reach the throttle maximum on the public API endpoint.

10. Inject FIPS endpoint URL to API node

    

11. Once you complete these steps you can select any of the operations of the AWS Elemental MediaConvert node and start using the integration!

If you're not familiar with AWS or the qibb Workflow Editor, we recommend consulting additional resources or seeking guidance from a technical expert to ensure that you set up the integration correctly.

Importing flow examples of a node

Once you've successfully installed a node from the qibb catalog, you can easily import example flows that showcase how the nodes can be used. These example flows are directly accessible within the Flow Editor and are designed to guide users with helpful hints, including how to configure mandatory parameters and credentials.

Here's how to import examples:

1. In the top right corner of the Flow Editor, click on the menu icon.

2. Select Import to open the Import Dialog.

3. Click on the Examples tab.

4. Choose an example from the list.

5. Confirm your selection by clicking on the Import button.

By following these steps, you are now ready to make basic API calls using the provided examples. For further exploration of what’s possible, you can find more complex examples in the Flow Catalog.