Feature request for exposing Amazon Connect Kinesis Video Stream metadata from StartMediaStreaming

Question

Dear Amazon Connect team,

When using the Amazon Connect StartMediaStreaming block to stream audio to Amazon Kinesis Video Streams (KVS), there is currently no way to programmatically obtain the name or ARN of the created stream within the Contact Flow. Neither the stream name nor tags (such as ContactId) are accessible via SetContactAttributes, nor are they included in the CTR until after the contact ends.

This creates a critical limitation: downstream Lambda functions or integrations (such as Transcribe or AI assistants) cannot reliably determine which KVS stream corresponds to the active contact, making real-time processing unreliable—especially at scale.

Feature requests:

Allow custom suffixes or full stream names in StartMediaStreaming, such as ${ContactId}.

Automatically tag the created KVS stream with ContactId (and optionally InstanceId) to enable safe lookup.

Expose the generated stream name or ARN as a system attribute accessible in SetContactAttributes or Lambda input.

These capabilities would significantly improve real-time use cases like transcription, AI guidance, or compliance monitoring using Amazon Connect.

Thank you for considering this improvement.

Best regards,

re:Post Agent · Answer

Thank you for your feature request regarding Amazon Connect's integration with Kinesis Video Streams (KVS). I understand your need for better programmatic access to stream metadata within Contact Flows. While I can't comment on future product plans, I can provide some information on the current capabilities and potential workarounds.

Currently, when using the Start media streaming block in Amazon Connect, certain contact attributes related to media streaming are available. These include:

1. Customer audio stream ARN
2. Customer audio start timestamp
3. Customer audio stop timestamp
4. Customer audio start fragment number

These attributes are accessible when you select "Media streams" as the Type in flow blocks that support attributes, such as the Start media streaming block.

For real-time processing, you can use the customer audio stream ARN, which is available in the JSONPath format: $.MediaStreams.Customer.Audio.StreamARN. This ARN uniquely identifies the Kinesis video stream that includes the customer data.

While this doesn't provide all the functionality you're requesting, it does offer a way to identify the specific stream associated with a contact. You could potentially use this ARN in downstream Lambda functions or integrations to link the stream to the active contact.

Regarding tagging and custom naming, these features are not currently available as you described. However, your suggestion to allow custom suffixes or full stream names, and to automatically tag streams with ContactId and InstanceId, would indeed enhance the ability to manage and identify streams, especially in large-scale operations.

For now, you might consider using the available attributes, particularly the stream ARN, in combination with other contact attributes to create the associations you need for your use cases. While not as straightforward as your proposed solutions, it could serve as a temporary workaround.

Your feedback about exposing more metadata and allowing greater customization in stream naming and tagging is valuable. These kinds of insights help shape future improvements to the service. While I can't promise when or if these specific features will be implemented, Amazon continuously evaluates customer feedback to enhance their services.  
**Sources**  
[Contact attributes for live media streaming in Kinesis Video Streams - Amazon Connect](https://docs.aws.amazon.com/connect/latest/adminguide/media-streaming-attributes.html)

Feature request for exposing Amazon Connect Kinesis Video Stream metadata from StartMediaStreaming

Relevant content