View a markdown version of this page

Camera as a Service - Camera as a Service
Camera as a service diagramFurther readingDiagram history

Camera as a Service

Publication date: January 25, 2023 (Diagram history)

With this architecture, you can use Internet of Things (IoT)-enabled cameras to generate live video feed and machine learning (ML) inference that you can consume in near real-time. The solution uses Amazon Kinesis Video Streams, Amazon Rekognition, Amazon Elastic Kubernetes Service (Amazon EKS), and Amazon API Gateway.

Camera as a service diagram

Reference architecture diagram for generating live video feed and machine learning inference from IoT-enabled cameras by using Kinesis Video Streams, Amazon Rekognition, Amazon EKS, API Gateway, and DynamoDB.

The following steps describe the architecture:

  1. Generate video feed by using Amazon Kinesis Video Streams Producer libraries.

  2. Ingest live video feed to Amazon Kinesis Video Streams.

  3. Convert the live feed into images through an on-demand or automated feature and send the images to Amazon Simple Storage Service (Amazon S3).

  4. An Amazon S3 write event invokes a AWS Lambda function. The function sends the image to Amazon Rekognition to generate inference.

  5. Store the inference and metadata in Amazon DynamoDB.

  6. Use APIs to fetch the inference from DynamoDB.

  7. The user app consumes live feed from Kinesis Video Streams, fetches inference from DynamoDB, and exposes the live feed by using a REST API. The user app runs on Amazon EKS.

  8. API Gateway exposes the API for video feed and inference.

  9. The end user consumes two APIs from API Gateway. The first provides video feed by using HTTP Live Streaming (HLS), MPEG-DASH, or GetMedia streaming. The second provides the ML inference.

  10. The admin app on Amazon EKS handles governance, administrative APIs, user APIs, camera onboarding, metrics, and insights.

  11. Use Amazon CloudWatch to store logs and metrics from the complete stack. Use Amazon Cognito to secure the API feed generated by API Gateway.

Further reading

For additional information, see the following resources:

Diagram history

To receive updates about this reference architecture diagram, subscribe to the RSS feed.

ChangeDescriptionDate

Initial publication

Reference architecture diagram first published.

January 25, 2023

RSS subscription requirement

To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.