Creating Amazon Chime SDK media pipelines - Amazon Chime SDK

Creating Amazon Chime SDK media pipelines

Important

You and your end users must understand that recording Amazon Chime SDK meetings may be subject to laws or regulations regarding the recording of electronic communications. It is your and your end users’ responsibility to comply with all applicable laws regarding the recordings, including properly notifying all participants in a recorded session that the session or communication is being recorded, and obtain their consent.

You and your end users are responsible for all content streaming using the media live connector service, and must ensure that such content does not violate the law, infringe or misappropriate the rights of any third party, or otherwise violate a material term of your agreement with Amazon.

To capture or stream an Amazon Chime SDK meeting, you create media pipelines. A media pipeline can consist of one of these pipelines:

  • Media capture – You use media capture pipelines to capture audio, video, and content share streams, plus meeting events and data messages. All media capture pipelines save their data to Amazon Simple Storage Service (S3) bucket that you create. You can create one media capture pipeline per Amazon Chime SDK meeting. For more information, refer to Understanding Amazon Chime SDK media capture pipeline creation, later in this section.

  • Media concatenation – You use media concatenation pipelines to concatenate the artifacts from a media capture pipeline. Concatenation pipelines work independently of media capture and live connector pipelines. For more information, refer to Creating media concatenation pipelines, later in this section.

  • Media live connector – You use media live connector pipelines to connect to services that enable you to stream Amazon Chime SDK meetings to an RTMP endpoint. You can create up to one media live connector pipeline per Amazon Chime SDK meeting. For more information, refer to Creating media live connector pipelines, later in this section.

  • Media stream – You use media stream pipelines to capture individual audio for all the attendees in a meeting, plus the mixed audio generated by a media concatenation pipeline. All media stream pipelines save their data to Amazon Kinesis Video Streams (KVS). For more information, refer to Creating media stream pipelines, later in this section.

The pipelines you create depend on the namespace you use. If you use the Chime namespace, you can only create media capture pipelines. If you use the ChimeSdkMediaPipelines namespace, you can also create media concatenation and media live connector pipelines, and use compositing features. If you want to migrate to the ChimeSdkMediaPipelines namespace, refer to Migrating to the ChimeSdkMediaPipelines namespace.

The following table lists the default limits for active media pipelines in each Region. Each type of pipeline counts toward the limit.

Region Default active pipeline limit

us-east-1

100

us-west-2

10

ap-northeast-1 10
ap-northeast-2 10
ap-south-1 10

ap-southeast-1

10

ap-southeast-2 10
ca-central-1 10

eu-central-1

10

eu-west-2 10
Note

If you exceed the limit for any Region, the CreateMediaCapturePipeline, CreateMediaConcatenationPipeline, and CreateMediaLiveConnectorPipeline APIs will throw Resource Limit Exceeded exceptions.

You can use the Service Quotas page in the AWS console to adjust your active pipeline limits, or you can contact your customer support representative. For more information about the Amazon Chime SDK meeting limits, see Quotas for the Amazon Chime SDK.

Before you begin, you must integrate your client application with the Amazon Chime SDK client library. For more information, see Learn about the Amazon Chime SDK client libraries. For more information about media pipelines, see Capture Amazon Chime SDK Meetings Using media pipelines.