This Guidance demonstrates how to implement a scalable video analysis as a service solution on AWS, providing you with powerful tools to manage and analyze video data from large IoT device fleets. It enables real-time event processing and intelligent video analysis, allowing you to derive actionable insights from video data quickly. The user-friendly interface provides administrators with a centralized dashboard for monitoring events, accessing video footage, and performing advanced searches across their entire fleet. With this Guidance, you can enhance security, improve operational visibility, and make data-driven decisions based on their video assets.

Note: [Disclaimer]

Architecture Diagram

[Architecture diagram description]

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.

  • API Gateway, Lambda, and Step Functions work together to provide comprehensive tracing and visualization of asynchronous API components, allowing you to analyze requests as they travel through the system. This integration helps in troubleshooting errors and monitoring latency issues effectively. By utilizing these services, you can gain valuable insights into your operations, automate changes, respond to events efficiently, and continuously improve processes and procedures.

    Read the Operational Excellence whitepaper 
  • AWS Identity and Access Management (IAM) policies are scoped down to minimal required permissions, enhancing access control. The edge process uses AWS IoT Core Credential Provider to obtain new temporary credentials every six hours, improving credential management. These services help you protect data confidentiality and integrity, manage user permissions effectively, and establish controls to detect security events.

    Read the Security whitepaper 
  • Lambda enhances system reliability through a robust serverless architecture, automatic scaling capabilities, built-in fault-tolerance mechanisms, and multi-Availability Zone redundancy for consistent system performance.  The serverless architecture of Lambda eliminates traditional infrastructure management concerns, helping ensure reliable performance across diverse workloads.

    Read the Reliability whitepaper 
  • Lambda provides dynamic scaling capabilities to eliminate idle capacity and optimize resource allocation. DynamoDB tables and Kinesis Data Streams operate in on-demand mode, automatically scaling to accommodate workloads without capacity planning.

    Read the Performance Efficiency whitepaper 
  • Data retention policies are set to 90 days for Kinesis Video Streams, 7 days for Kinesis Data Streams, and 30 days for OpenSearch Service (with data moving from hot to warm state after 30 minutes). This helps you avoid unnecessary costs associated with storing irrelevant data.

    Read the Cost Optimization whitepaper 
  • The serverless architecture of Lambda optimizes resource usage and reduces energy consumption through automatic scaling, while Kinesis Video Data Streams, OpenSearch Service, and Amazon S3 data retention policies reduce storage requirements. By optimizing infrastructure sharing, automating resource management, and enforcing data lifecycle policies, you can minimize overall resources required for your workload.

    Read the Sustainability whitepaper 
[Content Type]

[Title]

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

Disclaimer

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.

References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.

Was this page helpful?