- Newest
- Most votes
- Most comments
Thanks for the clarification!
Since it looks like media capture pipelines are limited to 10 concurrent sessions, it won't work for our use case—we need to support more than 10 concurrent meetings and get real-time transcription.
Is there any recommended alternative approach using the Amazon Chime SDK where we can still:
- Host video meetings,
- Access the audio stream in real time, and
- Send that audio to Amazon Kinesis Video Streams (KVS) for downstream transcription and processing?
We’d prefer to use managed services where possible and avoid browser hacks or local client audio routing if there's a supported method on the backend. Any architectural pointers or references would be greatly appreciated!
Please note that the default limits are per-region and us-east-1 allows 100 (not 10) concurrent media pipelines by default. The other regions are 10 each. https://docs.aws.amazon.com/chime-sdk/latest/dg/media-pipelines-limits.html
Also please note that these are just the default SOFT limits. These quotas can be adjusted to accommodate your business requirements. Please make a request through the Service Quotas page in the AWS Console.
For sending meeting audio to KVS, media capture pipelines are the appropriate solution and you should not let the default limit prevent you from proceeding with your application.
However, if you are only processing the audio for transcription, you will get better results using the native integration with Amazon Transcribe. The Amazon Chime SDK live transcription feature will manage this for you. (https://docs.aws.amazon.com/chime-sdk/latest/dg/meeting-transcription.html)
Based on the information provided in the AWS documentation, the limit of 10 concurrent media pipelines is indeed a constraint that applies to your entire AWS account, not per meeting. This means that if you have 11 or more concurrent meetings, you would only be able to create media pipelines for up to 10 of them at a time.
Each Amazon Chime SDK meeting requires its own dedicated media capture pipeline. You can create one media capture pipeline per Amazon Chime SDK meeting, and these pipelines cannot be shared across multiple meetings.
Therefore, with the default limit of 10 concurrent media pipelines, you would be limited to capturing content from a maximum of 10 meetings simultaneously. If you have more than 10 concurrent meetings, you would need to prioritize which meetings to capture, or consider requesting a quota increase from AWS if your use case requires capturing more than 10 meetings concurrently.
It's worth noting that this quota is adjustable, which means you may be able to request an increase from AWS if your use case requires capturing more than 10 concurrent meetings. You would need to contact AWS support to discuss the possibility of increasing this limit for your account.
Sources
Creating media capture pipelines for Amazon Chime SDK meetings - Amazon Chime SDK
Considerations for creating Amazon Chime SDK media pipelines - Amazon Chime SDK
Amazon Chime SDK endpoints and quotas - AWS General Reference
Relevant content
- asked 9 months ago
