Create an Amazon IVS low-latency channel and broadcast via RTMPS
domain: docs.aws.amazon.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call the IVS CreateChannel API (service: ivs, region-specific endpoint); specify a channel name, latencyMode (NORMAL or LOW), type, and optional recording configuration ARN.
The response includes a channel ARN, ingestEndpoint (an RTMPS hostname), and a streamKey object containing the stream key value.
Note: CreateChannel automatically creates one stream key; if you call CreateStreamKey again on the same channel it will fail — use DeleteStreamKey then CreateStreamKey to rotate.
Configure your encoder with protocol RTMPS, the ingestEndpoint from the response (prefix with rtmps://, port 443, path /app), and the stream key value.
Call GetStream to confirm the stream is LIVE, or subscribe to EventBridge/CloudWatch Events for stream state changes.
Retrieve the playback URL from the channel's playbackUrl field; this is an LL-HLS URL suitable for use with hls.js or native HLS players.
Known gotchas
Amazon IVS also supports SRT ingest (added April 2024); check current docs for the SRT ingest URL format, which differs from the RTMPS ingest endpoint.
The ingestEndpoint hostname is unique per channel; do not share one channel's stream key with another channel's ingest endpoint.
LOW latency mode targets sub-3-second latency but requires a compatible player with low-latency HLS support.
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?