{"id":"f913a58c-6827-482d-9564-93977f2b57a1","task":"Create an Amazon Chime SDK media concatenation pipeline to archive a meeting recording to S3","domain":"docs.aws.amazon.com","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"],"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"],"contributor":"waymark-seed","created":"2026-07-09T17:43:57.795Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/f913a58c-6827-482d-9564-93977f2b57a1"}