Streaming HTTP Push to AWS S3

As AWS has retired Amazon MediaStore on November 13, 2025, many workflows that rely on HTTP Push will require an updated destination for live segment delivery. Videon devices now support HTTP Push directly to Amazon S3, allowing you to continue using familiar HLS/DASH Push workflows with a highly reliable, S3-compatible storage backend.

This guide walks you through how HTTP Push to S3 works, what you need to prepare in AWS, and how to configure your Videon device.

This workflow is ideal for:

• Transitioning from MediaStore after deprecation.

• Clipping and analysis pipelines that rely on direct access to TS media segments.

• Simple HLS clip storage and retrieval for downstream automation tools.

Table of Contents

1. Prerequisites

2. Configuring HTTP Push to S3 on Your Videon Device

3. Playback Through CloudFront (Recommended)

4. Notes & Behavior to Expect

Prerequisites

Before configuring your Videon device, you’ll need:

1. An S3 Bucket

Create or use an existing bucket where your stream segments and manifest will be uploaded.

Example format:

2. IAM Credentials

You’ll need an IAM user with permission to:

• PutObject

• GetObject

• DeleteObject (optional, but recommended if you disable Save Segment Window)

Required credentials:

• Access Key ID

• Secret Access Key

• (Optional) Session Token, if using temporary credentials or role-based access

3. Optional: CloudFront Distribution

If you plan to play back the stream publicly or from a player:

• Set your S3 bucket as the origin.

• Ensure your distribution allows access to the target folder.

Configuring HTTP Push to S3 on Your Videon Device

1. Add HTTP Push Output

Go to your device’s Cloud UI, click CONFIGURATION - CREATE OUTPUT on the top right corner, then select “HTTP Push Output” in Output Type. Name your output and check “Output Enabled”.

 

2. Select Encoders

On the same window, choose your desired:

• Video Encoder (e.g., HLS – Input 1)

• Audio Encoder (optional if pushing video-only workflows)

3. Choose the Streaming Provider

Set Streaming Provider = AWS S3

4. Enter the S3 Push URL

This URL points to the folder inside your bucket where segments will be written.

Format:

Example:

This location will contain:

• HLS: .m3u8 manifest + .ts segments

5. Add AWS Credentials

Enter your Access Key, Secret Key, and optional Session Token.

These fields in the UI automatically hide sensitive data.

6. Configure Manifest Type

Choose:

• Generate HLS Manifest

7. Set Output Configuration

Most customers use:

• Media Type: Transport Stream (.ts) for HLS

• Segment Length: 2–6 seconds

• Number of Segments (window): The number of segments to retain in rotation

Note:

• Ultra Low Latency (ULL) is not supported with S3 destinations.

• Your device will automatically disable ULL when S3 is selected.

8. Save and Start Streaming

Once configured, start your workflow. You should begin seeing segment files appear in your S3 bucket.

Playback Through CloudFront (Recommended)

Because S3 does not serve HLS/DASH with optimal caching headers, CloudFront is strongly recommended for playback.

Steps:

1. Create a CloudFront distribution.

2. Set the S3 bucket (or a specific folder) as the origin.

3. Copy the CloudFront URL for your manifest, such as:

4. Load into any HLS or DASH test player.

Notes & Behavior to Expect

• Segment Deletion
  If “Save Segment Window” is disabled, segments are automatically deleted from S3.

• Memory Usage
  S3 does not support HTTP chunked uploads for live segments.
  Videon devices buffer each segment fully before uploading—this is normal behavior.

• HLS Playback
  Tested and confirmed to work with standard test players once delivered via CloudFront.

Congratulations on streaming a HTTP Push output to Amazon S3! If you need help, feel free to submit a request. Our engineering team will get to you as soon as possible.