Configure an AWS Elemental MediaLive channel with input and output groups for live streaming
domain: docs.aws.amazon.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an input (e.g., RTMP push, RTP push, or MediaConnect) and note its attachment name.
Create a channel referencing the input, selecting an input specification for codec, resolution, and bitrate class.
Add one or more output groups to the channel, such as an HLS output group targeting S3 or a MediaPackage output group.
Configure video and audio encode settings for each output within the group, including bitrate and GOP structure.
Start the channel and confirm it transitions to the RUNNING state before sending input traffic.
Known gotchas
A channel cannot be created with zero output groups; at least one is required.
Input and output settings are validated at creation and start time; mismatched codec/container combinations fail the start rather than warn beforehand.
Standard channel class runs two pipelines for redundancy and bills accordingly, while Single-pipeline channels cost less but have no automatic failover.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?