Skip to main content
Skip table of contents

AWS Elemental MediaConnect

Introduction

AWS Elemental MediaConnect is a service that makes it easy for broadcasters and other premium video providers to reliably ingest live video into the AWS Cloud and distribute it to multiple destinations inside or outside the AWS Cloud. MediaConnect provides the reliability, security, and visibility that you are used to with existing distribution methods, combined with the flexibility and cost-effectiveness that internet-based transmission provides.

For ingest, you send content to AWS Elemental MediaConnect from an on-premises contribution encoder, which encodes your video into a single, high-quality mezzanine file for contribution into the cloud. After the video is in the AWS Cloud, MediaConnect sends it to outputs that you specify, such as a cloud encoder, another MediaConnect flow, or an on-premises destination.

With AWS Elemental MediaConnect, you can do the following:

  • Ingest live video into the AWS Cloud.

  • Distribute live video to multiple destinations inside or outside the AWS Cloud.

  • Subscribe to a live video stream that is supplied by another AWS account. (This requires permission from the content originator through an entitlement.)

  • Send content from one AWS Region to another.

You can find more details and the supported operation on AWS Elemental MediaConnect | qibb Catalog.

How to get started with AWS Elemental MediaConnect integration

Before integrating AWS Elemental MediaConnect into your application, make sure that you have the necessary permissions to perform the required operations.

To get started, you will need your Access key, Secret access key, and Region information for authentication. If you do not already have an Access key and Secret access key, you can create them by following these steps:

  1. Sign in to the AWS Management Console and open the IAM console.

  2. In the navigation pane, choose Users, select the name of the intended user, and then choose the Security credentials tab.

  3. Click the Create access key button, select Application running outside AWS, and then click Next.

  4. (Optional) Set a description tag, and then click Create access key to continue.

  5. Copy your Access key and Secret access key and save them for later use.

In addition to the Access key and Secret access key, you have to assign to the newly created user proper access to the AWS Elemental MediaConnect functionality. To give full access to the MediaConnect functionality, you need to create a new policy, following these steps:

  1. In the navigation pane, choose Users, and select the name of the intended user. As part of the new view, make sure you are on the Permissions tab, click on the Add permissions dropdown, and choose Create inline policy.

  2. Define your permission by creating a new policy. For that choose the JSON view and use the following policy, granting full access to the AWS Elemental MediaConnect functionality, as well as limited IAM write access, limited CloudWatch read access, and limited EC2 list access. To add more or fewer rights to the policy you can always edit based on your needs.

    JSON
    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Action": [
                    "mediaconnect:*"
                ],
                "Effect": "Allow",
                "Resource": "*"
            },
            {
                "Action": [
                    "ec2:DescribeAvailabilityZones"
                ],
                "Effect": "Allow",
                "Resource": "*"
            },
             {
                "Action": [
                    "cloudwatch:GetMetricData"
                ],
                "Effect": "Allow",
                "Resource": "*"
            },
            {
                "Action": [
                    "iam:PassRole"
                ],
                "Effect": "Allow",
               "Resource": "*",
                "Condition": {
                    "StringLike": {
                        "iam:PassedToService": "mediaconnect.amazonaws.com"
                    }
                }
            }
        ]
    }  
  3. On the Review policy page for Name, enter MediaConnectAllAccess, and then choose Create policy. You can find all defined permissions for the policy as a part of the provided table Permissions defined in this policy.

Once you have your Access key and Secret access key, and you assure that your user has proper access to the AWS Elemental MediaConnect functionality, you can integrate AWS Elemental MediaConnect into your application by following these steps:

  1. Go to the qibb Workflow Editor and open the Node Catalog in the right sidebar.

  2. Install the AWS Elemental MediaConnect node by clicking the + button.

  3. Drag and drop the AWS Elemental MediaConnect node from the left sidebar into your workflow.

  4. Enter your Region, Access key, and Secret access key credentials into the Advanced/Security fields.

  5. Select the desired operation from the AWS Elemental MediaConnect node.

  6. Start using the integration!

If you are not familiar with AWS or the qibb Workflow Editor, additional resources or technical expertise may be necessary to ensure proper integration setup.

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.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.