This Guidance demonstrates how to use the Internet of Things (IoT) and Amazon Kinesis Video Streams with Web Real-Time Communication (WebRTC) to monitor videos from a vehicle. Original equipment manufacturers (OEMs) can give their customers the ability to monitor low-latency videos from a vehicle for security purposes, and the video can be accessed from a variety of in-vehicle platforms and viewed on any web browser. This Guidance can help OEMs increase direct revenue and improve engagement with OEM applications and web services. 

Architecture Diagram

Download the architecture diagram PDF 

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

  • WebRTC session count and minutes are counted and logged through the KVS WebRTC service. Each channel is set up on demand, so it can readily match to users. This allows for analysis of overall fleet and individual usage. Visibility into this usage can support billing or credit limits. Sessions can also be anonymized or tokenized to prevent matching to users if required by local regulation.

    Read the Operational Excellence whitepaper 
  • CloudFront secures web application delivery by HTTPS. Amazon Cognito handles user authorization, and an Amazon Cognito token secures access to API Gateway. This architecture secures IoT device access by X.509 certification over mutual transport layer security (mTLS). These devices are granted temporary credentials to access KVS only when there is user demand. 

    Read the Security whitepaper 
  • All cloud resources are serverless and scale with demand, helping prevent system downtime even if demand increases.

    Read the Reliability whitepaper 
  • This Guidance uses serverless systems to allow for both scalability and minimum configuration and maintenance. AWS IoT Core is purpose-built to manage permissions and configuration of a large fleet of devices, such as vehicles. KVS is built to facilitate peer-to-peer WebRTC with common signaling and support services (such as a TURN server), without infrastructure provisioning or additional configuration.

    Read the Performance Efficiency whitepaper 
  • To help minimize data transfer charges, data transferred in and out of the AWS Region is limited to the owner by using CloudFront to distribute an active application and API Gateway for queries. Data transferred to and from the vehicle is limited to small JSON messages with changes in shadow state and temporary credentials.  

    Read the Cost Optimization whitepaper 
  • The services in this Guidance are serverless and scale with demand, so you do not need to provision and maintain “standing” infrastructure. 

    Read the Sustainability whitepaper 

Implementation Resources

The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.

[Content Type]


This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].


The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

Was this page helpful?