As the deactivation of AWS MediaStore is planned for November 2025, Videon now supports HTTP Push streaming to AWS MediaPackage. This guide walks you through how to set up an HTTP Push output to MediaPackage directly from your Videon device’s Web UI.

 

Table of Contents

• Prerequisites
  • Create a new MediaPackage Channel Group, Channel, and Endpoint
  • Gather your MediaPackage Channel ingest endpoints
  • Collect your Access Keys
    • Understand AWS Access Keys
    • Temporary Security Credentials
    • Long-Term Access Keys
• Step 1: Create an HTTP Push Output
• Step 2: Select AWS MediaPackage as the Provider
• Step 3: Enter Your MediaPackage Ingest Endpoint and Credentials
• Step 4: Save and Start the Stream
• Step 5: Verify Stream Playback
• Best Practices for Streaming to AWS MediaPackage
• Troubleshooting
• FAQs

 

Prerequisites

Before configuring HTTP Push to MediaPackage, ensure the following:

• Your device’s software version is 11.1.0 or later.
• You have an AWS MediaPackage channel with an ingest endpoint.
  • If you need to create a new MediaPackage channel, follow the instructions to Create a new MediaPackage Channel Group, Channel, and Endpoint.
  • To gather your ingest endpoints from an existing MediaPackage channel, review the instructions to Gather your MediaPackage Channel ingest endpoint.
• You have temporary AWS credentials (Access Key, Secret Key, and Session Token).

Create a new MediaPackage Channel Group, Channel, and Endpoint

1. To create a new MediaPackage channel for streaming, first navigate to the AWS Console and log in with your account.

2. In the AWS Console, either select MediaPackage from your Recently visited list or search for “MediaPackage”.

3. Click on the selector (hamburger on lefthand side of screen) and then under Live v2, select Channel groups.
   

4. Click Create channel group.

   • Give your channel group a Channel group name and Description (optional)

   • Scroll down and click Create

5. From the next window, click Create channel

6. Give your new channel a Name, Description (optional), and select an Input type of “HLS”.

7. Under Channel policy, select Attach a custom policy and enter the following contents. Replace {ChannelARN} in line 11 with your Channel ARN displayed directly above in the AWS Console:

   {
     "Version": "2012-10-17",
     "Statement": [
       {
         "Sid": "AllowPUTtoChannel",
         "Effect": "Allow",
         "Principal": {
           "AWS": "*"
         },
         "Action": "mediapackagev2:PutObject",
         "Resource": "{ChannelARN}",
         "Condition": {
           "IpAddress": {
             "aws:SourceIp": "0.0.0.0/0"
           }
         }
       }
     ]
   }

   
8. Select "Create" (orange button at bottom right, below the custom policy window).

9. From the next window (within your newly created channel), click Create endpoint

10. Give your new endpoint a Name, Description (optional), a Container type of TS, and a Segment name

    • Scroll down to Endpoint policy and select Attach a public policy

    • Scroll down to Manifest definitions and select to Add HLS manifest

    • Give your HLS manifest a Manifest name, Child manifest name (optional, but recommended), and set a Manifest window (sec.) of 60

    • Scroll down and click Create

11. Congratulations, you have now created a new MediaPackage channel group, channel, and endpoint!

Gather your MediaPackage Channel ingest endpoints

1. Navigate to the AWS Console and log in with your account.

2. In the AWS Console, either select MediaPackage from your Recently visited list or search for “MediaPackage”.

3. Click on the selector (hamburger on lefthand side of screen) and then under Live v2, select Channel groups.
   

4. Choose an existing channel group.

5. Under Channels, click on the name of an existing channel.

6. Within the channel window that opens up, select Settings.

7. Under Input type: HLS, you should see two Ingest endpoints listed. Copy these and note them for entry into your Videon configurations.
   

Collect your Access Keys

Understand AWS Access Keys

AWS provides two primary types of access keys for programmatic access:

1. Temporary Security Credentials: These are short-lived credentials generated dynamically via the AWS Security Token Service (STS).
2. Long-Term Access Keys: These are permanent credentials associated with an IAM user.

If you enter long-term AWS access keys, Videon devices will automatically refresh temporary access tokens in the background so you can keep streaming without interruptions.

However, if you use short-term credentials, you'll need to manually update them in the device’s UI once they expire. This can cause a brief pause in your stream.

For more supporting documentation on temporary vs. long-term access keys, please refer to AWS's documentation for temporary security credentials in IAM.

Temporary Security Credentials

Key Features/Notes:

• Short-Lived: Valid for a limited duration (from a few minutes up to several hours).
• Dynamically Generated: Not stored with the user; generated upon request.
• Enhanced Security: Reduce the risk associated with long-term credentials.
• You will need to manually update them in the Videon device’s UI once they expire. This can cause a brief pause in your stream when the updated token is saved.

How to Obtain Temporary Credentials:

• Users can acquire temporary credentials by assuming a role using AWS STS. This can be done through:
  • AWS CLI: Using commands like

    assume-role

  • AWS SDKs: Programmatically requesting credentials in various programming languages.

For detailed methods, refer to AWS's guide on requesting temporary security credentials.

1. Assume an IAM Role: Users should assume a role that has the necessary permissions to access MediaPackage.
2. These can be found by signing into your AWS Console here.
3. Click the dropdown for the appropriate AWS account environment where your MediaPackage channel exists, and select Access keys.
   
4. Scroll to the bottom under Option 3: Use individual values in your AWS service client and you can find your AWS access key ID, AWS secret access key, and AWS session token. Copy these and note them for entry into your Videon configurations.
   

Long-Term Access Keys

Key Features/Notes:

• Persistent: Remain valid until manually revoked.
• Higher Risk: If compromised, can lead to unauthorized access.
• With long-term AWS access keys, Videon devices will automatically refresh temporary access tokens in the background so you can keep streaming without interruptions.
• Best Practices:
  • Avoid using root account credentials.
  • Regularly rotate access keys.
  • Monitor usage with AWS CloudTrail and set up alerts with CloudWatch.

For comprehensive management practices, consult AWS's documentation on managing access keys for IAM users.

Step 1: Create an HTTP Push Output

1. Go to your Videon device’s Web UI, or sign on to LiveEdge Cloud and find your device under Devices > All devices on the left.

2. If on Web UI, go to the Outputs tab under Encoder Control and click Add Output. If on Cloud, go to Configuration and click Outputs > Create Output.

3. Select HTTP Push as the output type.

Step 2: Select AWS MediaPackage as the Provider

1. If on Web UI, open the dropdown menu under HTTP Streaming Provider. If on Cloud, open the dropdown menu under Output Target > Streaming Provider.

2. Choose AWS MediaPackage from the list.

3. Under Manifest Type, ensure to select ONLY to Generate HLS Manifest or simply HLS on the local UI. Make sure Generate DASH Manifest or DASH is NOT selected.
4. Under Media Type, ensure that Transport Stream (.ts) or TS is selected.

Step 3: Enter Your MediaPackage Ingest Endpoint and Credentials

1. In the HTTP Push URL (and Secondary HTTP Push URL) field(s) of the Videon local web UI or Cloud UI, enter the MediaPackage ingest endpoint URL(s) from Gather your MediaPackage Channel ingest endpoints.

2. In the Access Key, enter your AWS access key ID.
3. In the Secret Key, enter your AWS secret access key.
4. In the Session Token: 

   • If you are using temporary credentials, you MUST enter your AWS session token. You will need to manually update them in the Videon device’s UI once they expire. This can cause a brief pause in your stream when the updated token is saved.

   • If you are using long-term credentials, you must leave the Session Token entry of the Videon UI empty. Videon devices will automatically refresh temporary access tokens in the background so you can keep streaming without interruptions

Step 4: Save and Start the Stream

1. Enable the HTTP Push output.

2. Click Save.

3. Your HLS stream will now be pushed to AWS MediaPackage.

Step 5: Verify Stream Playback

1. Navigate to the AWS Console and log in with your account.

2. In the AWS Console, either select MediaPackage from your Recently visited list or search for “MediaPackage”.

3. Click on the selector (hamburger on lefthand side of screen) and then under Live v2, select Channel groups.
   

4. Choose the appropriate channel group you are streaming to.

5. Under Channels, click on the name of the channel you're streaming to.

6. Under Origin endpoints, click the radio button to the left of the endpoint you are streaming with.
   
7. Under Manifests, click the radio button to the left of the Manifest name.
   
8. Then click Preview and a preview of your stream can be found.
9. To find a playback URL, click the Name of your Origin endpoint.
10. Click Manifest preview and you will be able to Copy URL for playback.
    

Best Practices for Streaming to AWS MediaPackage

• MediaPackage supports both HLS and DASH, but the current implementation released in LiveEdge  V11.1.0 supports HLS only via HTTP Push on Videon.

Troubleshooting

If your stream fails to appear in the player:

• Double-check your ingest URL and credentials. If using temporary/short-term credentials, try entering new temporary credentials to ensure they haven’t expired. If using long-term credentials, ensure that no Session Token is entered on the Videon device's local web UI or Cloud UI.
• Ensure your IAM role has permissions for MediaPackage ingest. If not, you will need to reach out to an admin of your AWS account.
• In your Videon configurations, double-check:
  • Under Manifest Type, ensure to select ONLY to Generate HLS Manifest or simply HLS on the local UI. Make sure Generate DASH Manifest or DASH is NOT selected.
  • Under Media Type, ensure that Transport Stream (.ts) or TS is selected.

FAQs

Q: Do I need to provide a Session Token?
A: Yes, if you're using temporary credentials generated via AWS STS.
A: No, the Session Token is not required when using long-term credentials.

Q: Can I use MediaPackage for DASH streaming?
A: No. Currently, HTTP Push to MediaPackage via LiveEdge supports HLS manifests only.

Q: What happens after AWS MediaStore is deprecated?
A: MediaStore will no longer be available after November 13, 2025. This new workflow ensures uninterrupted streaming to AWS infrastructure via MediaPackage.