Create an Amazon Chime SDK media concatenation pipeline to archive a meeting recording to S3
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
Ensure your app uses the ChimeSdkMediaPipelines namespace (not the legacy Chime namespace, which only supports capture pipelines) — migrate if needed
Start a media capture pipeline for the meeting first; concatenation pipelines consume that capture pipeline's output, not the live meeting audio directly
Call CreateMediaConcatenationPipeline (POST /sdk-media-concatenation-pipelines) with Sources as a single-item array of MediaCapturePipelineSourceConfiguration referencing the capture pipeline's MediaPipelineArn
Set Sinks to a single-item array with an S3BucketSinkConfiguration.Destination pointing at your target bucket/prefix
Pass a unique ClientRequestToken (2-64 chars) for idempotency
Grant the mediapipelines.chime.amazonaws.com service principal s3:PutObject/PutObjectAcl/GetObject at the object level and s3:ListBucket at the bucket level, and confirm the AWSServiceRoleForAmazonChimeSDKMediaPipelines service-linked role exists
Known gotchas
Concatenation pipelines require an existing capture pipeline as their Source — they cannot capture live meeting media directly
Requests are signed with AWS SigV4, not a Chime-specific token — use standard IAM credentials/SDK signing
The S3 bucket policy needs two separate grants (bucket-level ListBucket vs object-level Put/Get) — an overly-narrow policy is a common cause of silent pipeline failures
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?