Service icon

Amazon Kinesis Video Streams Connector

Stable version 2.0.0 (Compatible with OutSystems 11)
Uploaded on 03 June 2022 by 
 (6 ratings)

Amazon Kinesis Video Streams Connector

Securely stream media from connected devices to AWS with the Amazon Kinesis Video Streams connector.
Read more

With this managed service integrated into your OutSystems app, you can, for example, build media streams for camera-enabled IoT devices and for building real-time computer vision-enabled machine learning (ML) apps. Amazon Kinesis Video Streams enables secure WebRTC connections for peer-to-peer media streaming and real-time video streaming from a connected device to AWS for storage, analytics, machine learning (ML), playback, and other processing. 

The connector uses the AWS SDK (check the documentation on how to set up the connector). Once connected, you can easily include the Amazon Kinesis Video Streams capabilities in your apps. The following picture shows the Amazon Kinesis Video Streams connector in Service Studio:

How to “Try Now” this component

You might notice that this component doesn't have a “Try Now” option,  that’s because the best way to see  this  component in action is by checking Video Call validation.  It’s an Accelerator using Amazon Kinesis Video Streams.

In Video Call validation, you can try this component  and also learn how to integrate it in an OutSystems application to do a video call.


By downloading this component you acknowledge and agree to the collection of usage data (which may include, but is not limited to, method name, type of WebRTC protocol, or region) by OutSystems and Amazon Web Services. Usage data does not include personal data. If you do not  agree with such collection, please do not download this component.

Release notes (2.0.0)

In this version:

  • we have created the following static entities

    • KinesisChannelStatus

    • KinesisProtocol

    • KinesisRole

    • KinesisICETransportPolicy

  • renamed the static entity ChannelType to KinesisChannelType

  • <breaking change> Updated the following structures to use static entity id instead text as result:

    • Protocol structure to use KinesisProtocol Identifier

    • StartCallResponseConfiguration structure to use KinesisICETransportPolicy Identifier

    • ChannelInfoKeyValue structure to use KinesisICETransportPolicy Identifier

    • StartCallResponseConfiguration structure to use KinesisChannelStatus Identifier

  • <breaking change> Deleted Constants_Protocols and Constants_Roles actions since now we have static entities to retrieve the same values

  • <breaking change> The site properties containing AWS authentication information were deprecated and it is now the responsibility of the consumer application to manage where the credentials are stored. For now, we kept the site properties in the module to prevent loss of data. In future versions they will be removed from the module

Reviews (0)