Create a storage configuration resource in IVS Real-Time that references an S3 bucket ARN; the bucket must have an appropriate bucket policy granting IVS permission to write objects.
When calling CreateStage or UpdateStage, attach the storage configuration ARN to enable automatic recording of stage participants to S3.
Participant recordings are individual per-participant MP4 or HLS files written to the configured S3 bucket; the path structure follows IVS conventions (check current docs for the exact prefix format).
To start or stop recording mid-session, call UpdateStage to add or remove the storage configuration; changes take effect for new segments, not retroactively.
After the stage session ends, retrieve recording metadata using the GetComposition or ListStorageConfigurations APIs to locate the output files in S3.
Apply S3 lifecycle policies to automatically expire or archive recordings after your required retention period.
Known gotchas
The S3 bucket policy must explicitly allow the IVS service principal to put objects; a missing or incorrect policy causes recording to silently fail without stream interruption.
Individual participant recordings are not automatically merged into a composite; post-processing with MediaConvert or FFmpeg is required to produce a mixed-down recording.
Recording for real-time stages (ivs-realtime) uses a different API and configuration model than recording for low-latency channels (ivs); do not mix up the two service namespaces.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp