Call CreateMediaCapturePipeline (chime-sdk-media-pipelines regional endpoint) with SourceType=ChimeSdkMeeting, SourceArn pointing to your meeting, and SinkType=S3Bucket with your bucket ARN and prefix.
The pipeline writes 5-second MP4 segment files to S3 for both audio (all-attendee mixed audio and active-speaker video in AudioWithActiveSpeakerVideo mode) and individual video streams — file names carry a timestamp in the format yyyy-MM-dd-HH-mm-ss-SSS.mp4.
To end capture, call DeleteMediaCapturePipeline with the pipeline ID; the pipeline status transitions to Deleting and then the final segments are flushed to S3.
Create a Media Concatenation Pipeline (CreateMediaConcatenationPipeline) pointing at the same S3 prefix to merge the 5-second MP4 chunks into a single MP4 output file.
Monitor the concatenation pipeline status via GetMediaPipeline until it reaches Stopped, then retrieve the concatenated MP4 from the output S3 location.
Known gotchas
Chime SDK media capture produces MP4 segment files — not Opus, OGG, or raw PCM; downstream tools expecting those formats need a transcode step.
The S3 bucket must have a bucket policy granting the Chime SDK service principal (mediapipelines.chime.amazonaws.com) PutObject access — missing permissions silently fail to write segments.
Capture and concatenation are separate pipeline operations billed independently; always delete the capture pipeline after recording stops to avoid ongoing charges.
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