To create a channel in AWS Elemental MediaLive, first create an input for your source, then create and configure the channel, attach the input, set up an output group for your destination, save, and start when both the source and destination are ready. The exact input and output settings depend on the protocols and delivery systems you choose; this guide walks through the decisions and gives separate RTMP-push and HLS-pull examples.
Plan the source and delivery path first
MediaLive channels sit between an upstream source and a downstream destination. Before opening channel creation, decide how the source will reach MediaLive, what pipeline arrangement you need, and where the resulting stream should go. AWS describes input delivery as either a push from the upstream system or a pull by MediaLive; the source operator may need to configure their system before you can connect it. AWS input setup documentation
- Source and protocol: identify the existing source and the input protocol it supports. Input requirements, source-side configuration, and credentials vary by protocol.
- Push or pull: with a push, the upstream system sends content to MediaLive; with a pull, MediaLive connects to a source address to retrieve it.
- Pipeline arrangement: choose standard or single-pipeline in line with the source endpoints and redundancy arrangement you intend to use. Do not assume every source provides the same redundancy.
- Destination: decide whether your downstream workflow needs HLS, RTMP, or another supported output arrangement, and prepare its destination details and any credentials.
- Output needs: determine the video and audio streams you need, plus any caption, manifest, DRM, or ad-marker requirements that apply to your workflow.
Do not begin by assuming you need a camera or capture card: the upstream source may already be another system that can deliver a supported input.
Create the input before the channel
Create an input suited to the source protocol before creating the channel. The addresses, security configuration, and number of source endpoints depend on the input type and channel class. AWS’s input setup guide covers protocol-specific requirements.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Compact but Powerful Design: ZowieBox is smaller than a phone, featuring a tally light and LCD screen for streaming status. Capture console gameplay in up to 4K with zero-lag HDMI passthrough, while the built-in video encoder converts video for IP streaming. The IP stream can also be decoded back to a 4K HDMI signal.
- Standalone Game Streaming: Just plug and play—ZowieBox enables PC-free live gaming without affecting gameplay. As an RTMP hardware encoder and HDMI streamer, it delivers stable streaming directly from your source, making it ideal for gaming, live events, and professional broadcasting.
- NDI|HX3 Converter Technology: ZowieBox converts HDMI signals to NDI|HX3/HX2/HX, functioning as an NDI video encoder, or NDI Video Decoder for flexible IP workflows. Certified NDI technology enables low-latency gameplay streaming through OBS/vMix. Note: Encoder and decoder modes cannot run simultaneously; full NDI signals are not supported.
- UVC to HDMI Conversion: Supporting up to 4K@30fps and 1080p@60fps decoding, ZowieBox enables flexible conversion for webcam and video workflows. As a video decoder and HDMI to IP converter, it expands connectivity options for professional video devices. Note: USB capture card functionality is not currently supported.
- All-around Configuration Options: Control ZowieBox through its web UI on a PC, phone, or tablet. Manage connected PTZ cameras, tally light, video/audio, OSD, work mode, streams, network, and system settings. Support for VISCA over IP encoder workflows enables flexible PTZ control, while the dashboard provides video preview and system status.
Example: public RTMP push
For a public RTMP push, coordinate the application and stream names with the upstream operator, and obtain the public IP addresses the source will use. Configure an input security group to allow those source IPs; do not leave source access controls unplanned. Create the RTMP input and pass the AWS-generated destination details to the upstream system so it can send the feed.
Match the input class and endpoints to the planned channel arrangement. AWS documents two destinations for a standard arrangement and one for a single-pipeline arrangement. The upstream source must be configured to use the destinations appropriate to that arrangement. AWS RTMP input instructions
Rank #2
- 【Innovative Product with Leading Technology】- Equipped with an advanced H.265 /H.264 dual encoding chip, supports 4K UHD (3840x2160) video input and output, with a maximum frame rate of 30fps at 4K resolution and up to 120fps at 2K and lower resolutions, delivering a smooth and detailed visual experience. It also supports HDCP 1.4 decryption, easily decoding various HDMI ultra HD video sources, delivering a cinematic visual experience for both professional live streaming and 4K ultra HD content transmission.
- 【Multi-protocol and Multi-platform Compatibility】- Fully compatible with streaming protocols such as HTTP, RTSP, RTMP(S), SRT, HLS(M3U8), MP4, Multicast(UDP, RTP, PTL), FLV, WebRTC, TRTC, ICECAST, it can simultaneously output 4 video streams with different protocols and push them to live streaming platforms such as YouTube, Facebook, Twitch, and Vimeo with one click. Simultaneous live streaming across multiple platforms can be achieved without additional equipment.
- 【Highly Customizable Settings to Meet Individual Needs】- It supports adding static text, scrolling captions, brand logos, and timestamps. Users can freely adjust core parameters such as video resolution, frame rate, and bitrate, and also perform personalized editing functions such as video cropping, rotation, flipping, and mirroring. It supports dual input of HDMI embedded audio and line-in audio, with adjustable sound quality, making your live stream content more distinctive and allowing you to create a unique brand live stream style.
- 【Stable and Efficient Transmission, Easy Operation】- Employing HDMI to Ethernet core connection technology, it ensures stable and reliable network transmission with low latency and no lag, adapting to various network environments. Equipped with an intuitive user interface and detailed instruction manual, no professional technical background is required; setup can be completed quickly after connecting the device. It is also compatible with multiple terminals such as computers and mobile phones for management, and the video stream status can be viewed in real time via a URL.
- 【Lifetime Free Warranty and Technical Supports】- All URayCoder video codecs come with a lifetime free warranty and technical supports, supporting secondary development and feature customization to meet enterprise-level personalized needs. Meanwhile, we providing many kinds of customization services such as shell pattern printing, logo addition, hardware and function development, ensuring reliable quality and worry-free after-sales service.
Example: HLS pull
For HLS, gather the source URL or URLs and any credentials the source requires. MediaLive pulls from the HLS source when the channel starts, rather than receiving the same kind of RTMP push described above. AWS specifies two source URL fields for a standard HLS input and one for a single-class input. AWS input setup documentation
These are distinct workflows: do not reuse the RTMP security-group and destination assumptions for an HLS pull.
Rank #3
- 【Hardware H.265/H.264 Encoding at 1080P60】Dedicated hardware encoder delivers broadcast-quality 1080P60 streams with H.265/H.264 compression. Reduces bandwidth usage by up to 50% compared to legacy H.264-only solutions, while maintaining crisp, crystal-clear video output.
- 【Broad Protocol Support for IP Distribution】 Supports SRT, RTMP(S), RTSP, UDP, HTTP, HLS, WebRTC, TRTC, Icecast and SHOUTcast — integrate seamlessly with CDNs, surveillance NVRs, IPTV systems and browser-based monitoring dashboards. One device replaces multiple single-purpose streaming boxes.
- 【Browser-Based Setup in Minutes】 Set up in minutes through any browser — no software, drivers or OS compatibility issues. DHCP is enabled by default to prevent IP address conflicts on your network. Note: basic networking knowledge (IP address, RTSP/RTMP configuration) is recommended for advanced streaming setups.
- 【Compact Design with Flexible Deployment】Palm-sized form factor (approx. 90×54×29mm) fits easily behind monitors, on shelves, or in equipment racks. Low power consumption ensures reliable 24/7 operation for live events, remote monitoring, and digital signage.
- 【Professional Audio & OSD Overlay + 1-Year Warranty】 Supports HDMI embedded audio plus external 3.5mm input. Built-in OSD generator adds scrolling text, logos, or timestamps directly to the video stream — ideal for branding, event info, or security labeling. Backed by a 1-year warranty and 24/7 online technical support.
Create the channel and choose its class
Once the input exists, use the MediaLive console’s channel creation workflow. Set the channel name, select the IAM role, choose the channel class, and match the input specification to the source. AWS’s channel details instructions describe the channel configuration decisions.
| Choice | What to align | Documented source-endpoint detail |
|---|---|---|
| Standard | Use when the intended source and pipeline arrangement call for the standard class; verify the input type and source can provide the matching arrangement. | Two destinations for the public RTMP push example; two source URLs for a standard HLS input. |
| Single-pipeline | Use when the planned source and pipeline arrangement call for a single pipeline; do not treat it as interchangeable with standard without checking source requirements. | One destination for the public RTMP push example; one source URL for a single-class HLS input. |
The endpoint counts above describe the cited RTMP and HLS input examples, not a universal rule for every MediaLive protocol or source. For AWS Elemental MediaLive Anywhere channels, the cited channel-details instructions specify additional placement settings and require single-pipeline and public-internet delivery. Do not choose a cluster or placement group arbitrarily; confirm the applicable Anywhere configuration in AWS’s channel details guide.
Rank #4
- 4K & HD STREAMING IN H.264 AND H.265 – Self-contained processor supporting H.264 and H.265 encoding in HD or Ultra HD (up to 2160p60) via SRT or RTMP, streaming directly to YouTube, Facebook, X, Twitch, Zoom, Microsoft Teams, OBS, Wowza, and many more — no encoding PC needed.
- 12G-SDI INPUT WITH STANDARDS CONVERSION – Supports input resolutions up to DCI 4K60 with an SDI input and SDI loop output, plus Teranex-powered automatic standards conversion so any HD or Ultra HD source streams cleanly at any target resolution.
- DUAL MONITOR OUTPUTS – Features both SDI and HDMI monitor outputs with a user-configurable standards converter on both the 12G-SDI Out and 4K HDMI Out, so you can feed a confidence monitor or downstream device at any required format independent of your streaming standard.
- ETHERNET + 5G/4G MOBILE WITH AUTO-FAILOVER – Connect via Gigabit Ethernet (10/100/1000BASE-T) or tether a smartphone via USB-C for mobile data, with automatic switchover between connections — ensuring your stream stays on air even if the primary internet connection drops.
- CLOSED CAPTIONS, TIMECODE & REST API – Supports embedding CEA-608 and CEA-708 closed captions in live RTMP streams, source timecode over RTMP and SRT, and offers a REST API over Ethernet for external HTTP control — ideal for broadcast automation and accessibility-compliant workflows.
Attach the input and configure an output group
In the channel configuration, attach the input you created, then add an output group that matches the downstream system. HLS and RTMP output groups have different destination and stream settings, so select the group based on the destination workflow rather than treating them as interchangeable.
HLS output group
Configure the HLS destination, the outputs and stream settings needed by the downstream workflow. HLS configuration can also include manifest options, DRM, captions, and ad markers where required. AWS documents HLS destinations including Amazon S3, AWS Elemental MediaStore, AWS Elemental MediaPackage, and HTTP servers; MediaPackage is one option, not the only HLS destination. See the AWS HLS output group guide and its destination configuration documentation.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsBest Value
- ⭐【Innovative Product with Leading Technology】- Equipped with an advanced H.265 /H.264 dual encoding chip, supports 4K UHD (3840x2160) video input and output, with a maximum frame rate of 30fps at 4K resolution and up to 120fps at 2K and lower resolutions, delivering a smooth and detailed visual experience. It also supports HDCP 1.4 decryption, easily decoding various HDMI ultra HD video sources, delivering a cinematic visual experience for both professional live streaming and 4K ultra HD content transmission.
- ⭐【Multi-protocol and Multi-platform Compatibility】- Fully compatible with streaming protocols such as HTTP, RTSP, RTMP(S), SRT, HLS(M3U8), MP4, Multicast(UDP, RTP, PTL), ONVIF, FLV, WebRTC, TRTC, ICECAST, it can simultaneously output 4 video streams with different protocols and push them to live streaming platforms such as YouTube, Facebook, Twitch, and Vimeo with one click. Simultaneous live streaming across multiple platforms can be achieved without additional equipment.
- ⭐【Highly Customizable Settings to Meet Individual Needs】- It supports adding static text, scrolling captions, brand logos, and timestamps. Users can freely adjust core parameters such as video resolution, frame rate, and bitrate, and also perform personalized editing functions such as video cropping, rotation, flipping, and mirroring. It supports dual input of HDMI embedded audio and line-in audio, with adjustable sound quality, making your live stream content more distinctive and allowing you to create a unique brand live stream style.
- ⭐【Stable and Efficient Transmission, Easy Operation】- Employing HDMI to Ethernet core connection technology, it ensures stable and reliable network transmission with low latency and no lag, adapting to various network environments. Equipped with an intuitive user interface and detailed instruction manual, no professional technical background is required; setup can be completed quickly after connecting the device. It is also compatible with multiple terminals such as computers and mobile phones for management, and the video stream status can be viewed in real time via a URL.
- ⭐【Lifetime Free Warranty and Technical Supports】- All URayCoder video codecs come with a lifetime free warranty and technical supports, supporting secondary development and feature customization to meet enterprise-level personalized needs. Meanwhile, we providing many kinds of customization services such as shell pattern printing, logo addition, hardware and function development, ensuring reliable quality and worry-free after-sales service.
RTMP output group
For an RTMP destination, configure the destination and connection settings, then configure the stream settings for its single output. Use the channel configuration guidance to navigate the channel workflow and consult the relevant AWS output-group instructions for the destination you selected.
If the destination is MediaPackage
AWS’s getting-started example uses MediaPackage destination URLs and credentials in the HLS group. Treat credentials as secrets: enter them through the supported configuration method and do not publish them in documentation, screenshots, or shared examples. AWS’s example stores passwords in Systems Manager Parameter Store. Follow the AWS HLS output instructions for the destination-specific setup.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Save, start, and validate the workflow
- Review the channel configuration: confirm the selected IAM role, channel class, input specification, attached input, output group, destination, and stream settings agree with the source and downstream plan.
- Save the channel in the MediaLive console after the required configuration is complete.
- Make the source and destination ready: confirm the upstream system is configured to push to the generated destinations, or that the HLS source URLs and any needed credentials are accessible; make sure the downstream destination is configured to receive the output.
- Start the channel when both ends are ready. For an HLS input, MediaLive begins pulling when the channel starts. AWS input setup documentation
- Check the relevant AWS monitoring guidance for your specific input protocol and destination to validate operation. Status checks and troubleshooting depend on the configured workflow; the setup instructions alone do not define one universal validation checklist. AWS’s HLS output documentation and input-specific documentation are the starting points.
Common setup problems and what to check
- Channel creation starts before an input exists: create the protocol-appropriate input first, then select it in the channel configuration.
- The source cannot reach a public RTMP input: check that the input security group allows the source’s public IPs and that the upstream system is using the generated destination details for the chosen class.
- The endpoint count does not match the class: verify standard versus single-pipeline against the input arrangement. The documented RTMP and HLS examples use different endpoint counts by class.
- An HLS pull does not begin as expected: confirm the source URLs and any required credentials, and remember MediaLive pulls when the channel starts.
- The channel has no usable output: verify that an output group is configured for the actual downstream destination and that its destination and stream settings match that workflow.
- MediaPackage credentials are exposed: remove them from shared material and use the appropriate secret-handling approach, such as the Systems Manager Parameter Store approach in AWS’s example.
Cost and configuration scope
The setup documentation cited here does not establish current MediaLive rates, quotas, or account prerequisites. Check AWS’s current service and account guidance for your region and intended configuration before estimating operating costs. Input protocol, channel class, output destination, and account-specific configuration can all affect what needs to be set up; the workflow above is not a universal configuration template.
Or let it run in the cloud
If your goal is specifically to keep a YouTube channel live by looping uploaded recordings or a playlist, rather than to process a live source through MediaLive, StreamNeo is a simpler fit. Upload a recording or build a playlist, add your YouTube stream key once, and go live. StreamNeo runs the loop in the cloud, so nothing has to stay on at home; it streams the uploaded video as made, up to 4K 60fps, at one flat price per slot, with automatic recovery if YouTube drops the stream. The first day is free with no card. Monthly: $9.99 per month. It is for uploaded video sent to YouTube, not a camera-based live feed or a replacement for MediaLive’s configurable source-to-destination workflow. Start your free StreamNeo day.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
