AWS Panorama
[Ended May 31, 2026] Appliance-based service that analyzed existing IP camera streams at the edge. Devices no longer work; AWS points to SageMaker with Jetson hardware and Greengrass instead
Overview
[Discontinued] AWS Panorama reached end of support on May 31, 2026, and Panorama Appliances, which depended on the cloud service, no longer function. The following describes the service as it worked at the time. AWS Panorama is a service that runs computer vision inference in real time on edge devices against video streams from existing network cameras (IP cameras). A dedicated hardware appliance called the Panorama Appliance is installed on-premises, performing analysis such as object detection, people counting, and safety monitoring locally without sending camera footage to the cloud. Custom models trained with SageMaker or pre-built models from AWS Marketplace can be deployed as applications, with a single appliance simultaneously processing video from multiple cameras. Since only analysis results are sent to the cloud, it achieves both bandwidth savings and privacy protection.
End of Support and Migration Paths
AWS Panorama reached its end of support on May 31, 2026, and had stopped accepting new customers on May 20, 2025. Because the Panorama Appliance and its applications depended on connectivity to the Panorama cloud service, the devices themselves no longer function after the shutdown. AWS officially points to two alternatives: adopt an off-the-shelf solution from AWS Partners, or build your own with Amazon SageMaker (including the computer vision algorithms in SageMaker JumpStart), run it on off-the-shelf NVIDIA Jetson-based devices or edge servers, and manage the edge fleet with AWS IoT Greengrass, AWS Systems Manager, or Amazon EKS / ECS Anywhere. This page remains available as a historical reference and migration guide.
Appliance Architecture and Video Pipeline
The Panorama Appliance is a dedicated edge device equipped with an NVIDIA GPU, capable of simultaneously processing RTSP streams from up to 16 IP cameras. The video pipeline consists of frame acquisition from cameras, preprocessing (resize, normalization), model inference, post-processing (NMS, tracking), and result output. Applications are developed using the Python SDK, with inference logic written in per-frame callback functions. Models are delivered in ONNX format or compiled with SageMaker Neo, with TensorRT optimization minimizing inference latency. Both serial execution of multiple models (e.g., person detection followed by pose estimation) and parallel execution (e.g., vehicle detection and pedestrian detection simultaneously) are possible, with flexible pipeline configuration within GPU memory limits. Cameras can be dynamically added or removed from the console without redeploying applications.
Use Cases and Model Development Best Practices
Representative Panorama use cases include manufacturing line quality inspection, retail store visitor analytics, construction site safety monitoring, and logistics warehouse inventory management. On manufacturing lines, it performs defect visual inspection in seconds, dramatically improving detection accuracy and processing speed compared to traditional visual inspection. For model development, the standard approach is building a pipeline that annotates datasets with SageMaker Ground Truth, trains with SageMaker Training, and compiles for edge with Neo. In production, a continuous training mechanism is important to handle lighting condition changes, camera angle shifts, and seasonal appearance variations. Sending inference results to CloudWatch Metrics as custom metrics and monitoring detection accuracy changes over time enables early detection of model drift.
Operational Design and Cost Structure
In Panorama operations, appliance health monitoring is critical. Device CPU/GPU utilization, memory consumption, and temperature are viewable from the console, with CloudWatch Alarms configured for threshold alerts. Application logs are sent to CloudWatch Logs for investigating inference errors and frame drops. The cost structure consists of appliance hardware purchase cost (initial expense) and monthly device management fees, with no per-camera or per-frame-rate usage charges. This means more cameras yield lower per-camera costs, providing scale benefits. For network design, ensuring bandwidth between cameras and the appliance (approximately 4Mbps per camera at 1080p 30fps) and VLAN segmentation are recommended for security.
References (Official AWS Resources)
The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.
- Amazon SageMaker official page
- Amazon Rekognition official page
- AWS IoT Core official page
- AWS Documentation (official)
If this page and the official documentation disagree, treat the official documentation as authoritative.