Skip to main content

Ad-Flow: Output to MediaLive's RTP Input

This guide explains how to create an RTP input in AWS MediaLive and configure the Ad-Flow container to stream to it.

Creating the MediaLive Input​

Security Group Setup​

  1. Navigate to MediaLive in AWS Console
  2. Go to Network Input Security Groups
  3. Click Create Input Security Group
  4. Set the following:
    • For Type, select RTP
    • Input CIDR range: Add the CIDR range that includes your Ad-Flow container's IP
    • Give your security group a meaningful name
  5. Note down the Security Group ID for later use

Creating RTP Input​

  1. In MediaLive, go to Inputs
  2. Click Create Input
  3. Configure the following settings:
    • Input Type: Select RTP
    • Input network location: Select AWS
    • Input Security Group: Choose the security group created above
    • Name: Give your input a descriptive name (e.g., "channel1-rtp-input")
    • Network Input Settings:
      • For each destination (Primary and Secondary):
        • Select Local IP: Choose "Auto"
        • Local Port: Enter desired port (e.g., 5000)
    • Buffer Size: Set to at least 120ms (matches Ad-Flow delay)
  4. Click Create
  5. Note down the following from the input details:
    • Primary Destination IP
    • Primary Destination Port
    • Secondary Destination IP (if using redundancy)
    • Secondary Destination Port (if using redundancy)

Configuring Ad-Flow Container​

Update your container configuration to match the MediaLive input settings:

Basic Configuration​

ParameterValueNotes
OUTPUT_IP<Primary Destination IP>From MediaLive input
OUTPUT_PORT<Primary Destination Port>From MediaLive input
STREAM_PROTOCOLrtpMust be RTP for MediaLive

Example Configuration​

OUTPUT_IP: "10.100.20.30"        # MediaLive Primary Destination
OUTPUT_PORT: "5000"              # MediaLive Primary Port
STREAM_PROTOCOL: "rtp"
DELAY_SECONDS: "120"             # Match with MediaLive buffer

Configuration Notes​

Single vs. Dual Pipeline​

  • For single pipeline:

    • Configure only primary destination
    • MediaLive input will have one endpoint

  • For dual pipeline (redundant):

    • Stream from Ad-Flow to the primary destination
    • Stream from Delay-Flow to the secondary destination
    • Configure each container with respective MediaLive endpoint
    • Set identical DELAY_SECONDS on both containers

Network Considerations​

  1. Security Groups
    • Ad-Flow container must be able to reach MediaLive input
    • MediaLive security group must allow Ad-Flow container IP