AWS

Amagi CLOUDPORT Architecture based on AWS for FAST for channel playout on AWS

CK CK 3788 
Created at
Updated at  
1,315 0 0

Amagi, a leading cloud broadcast and streaming TV technology provider with over 2,000 channels deployed globally, utilizes AWS to offer a range of playout service resiliency options through its CLOUDPORT SaaS platform. As an AWS Specialization Partner and Marketplace Seller, Amagi caters to diverse customer needs by leveraging multiple AWS Availability Zones and regions, offering solutions ranging from cost-effective single-AZ deployments to highly resilient multi-region setups. For clients demanding the ultimate in redundancy, Amagi provides a beyond multi-region option, incorporating on-premises automation and playout alongside its cloud-based infrastructure to ensure business continuity during unforeseen events.

 

CLOUDPORT's Disaster Recovery Configuration Modes

Amagi offers playout and automation deployments in hot, warm, and cold configurations to cater to varying business requirements for recovery time and cost. Hot configurations provide instant switching between active primary and secondary regions, ensuring high availability and serving as origins for CDNs. Warm configurations offer rapid recovery in minutes by keeping data in sync and activating playout processors only during failover, balancing cost and recovery speed. Cold configurations provide the lowest cost with minimal "rescue content" and recovery times of up to an hour, representing a degraded service continuity option. Amagi's distributed architecture guarantees instant control plane recovery with a sub-one-minute RTO in multi-AZ setups and a 10-minute RTO for regional failover, ensuring playout continuity.

 

Solution Architecture

Amagi CLOUDPORT is a versatile playout platform that supports most industry-standard audio, video, and subtitle formats. It provides an intuitive interface with asset management, analytics, and configurable rules.

Key features include automation for scheduling, quality control, and monitoring; multi-layered graphics support; and a wide range of input formats like MXF, MOV, MPG, TS, and output formats including MPEG-TS, HLS, SRT, Zixi, NDI, and RIST. The platform handles video codecs AVC and HEVC; audio codecs AAC, AC3, and EAC3; as well as captions in CC-608, CC-708, DVB subs, and DVB teletext.

Amagi CLOUDPORT Architecture based on AWS for FAST for channel playout on AWS

In the diagram above, the secondary region does not actively generate service 24×7. It remains in a warm (standby) state, prepared to take over transmission if issues arise in the primary region. If a switch from the primary to the secondary region is necessary, it is automatic through Amazon CloudFront, ensuring a seamless and swift transition and allowing uninterrupted service availability.

 

Design Aspects

Amagi's CLOUDPORT SaaS platform leverages a robust AWS infrastructure for video transport and business functionalities. It utilizes AWS Elemental Media Services for resilient video processing and a microservices architecture on Amazon EKS for dynamic scaling. The platform depends on managed services like Amazon Aurora, ElastiCache, and S3 for database, caching, and storage, ensuring reliability. Multi-region networking through VPC peering and Amazon EKS's CNI enables communication between pods across regions. Amazon Route 53 facilitates DNS-based service discovery and implements readiness checks for fast failover and failback, ensuring business continuity and disaster recovery.

 

Seamless Cloud-Based Media Asset Management

CLOUDPORT leverages AWS services to provide playout services for customers, ingesting live feeds via AWS Elemental MediaConnect over AWS Direct Connect and integrating on-premises content and schedules by uploading them to Amazon S3. S3 acts as the central repository for petabytes of video assets, with S3 Multi-Region Access Point ensuring regional redundancy for input files. Automated playout services retrieve and process data from S3, including transcoding and verification, using Amazon SNS for issue notifications, and ultimately storing transmission-ready assets back in S3.

 

High Availability and Data Redundancy

Amazon Aurora Global Database and Amazon ElastiCache Global Datastore both provide disaster recovery and high availability solutions by replicating data across regions and enabling automatic failover. Aurora Global Database replicates data at the storage layer for database failover, while ElastiCache Global Datastore offers an in-memory caching solution with region failover. Both services ensure minimal application disruption during outages by automatically promoting a secondary region to primary, employing DNS switchovers, and allowing for reversion to the original architecture once the primary region recovers.

 

Multi-Region Redundancy with CLOUDPORT Switcher and Amagi LIVE

The CLOUDPORT Switcher microservice allows for seamless, frame-accurate video switching to AWS Elemental MediaLive, which writes content to MediaStore or S3. These services originate content for Amazon CloudFront, providing primary and failover CDN paths for continuous video delivery across regions.

Amagi LIVE utilizes redundant contribution streams through separate MediaConnect direct connects to ensure network fault tolerance. MediaConnect streams are sent to multiple receive locations over separate direct connects, enhancing redundancy. This architecture withstands regional failures, ensuring reliable video delivery.

 

Dual-Region Redundancy

After integrating all components, pods interconnect with storage services in the primary us-east-1 region. To ensure redundancy, these storage services are duplicated across the secondary us-west-1 region.

In a regional failure event, the secondary storage services promote taking over so the control and video path continue without interruption despite the outage. This demonstrates failback reverting changes, returning the system to its initial state after regional failure. This swift recovery design maintains full operational capability, safeguarding service continuity and minimizing downtime.

 

Failover Strategies: Flexibility and Customization

In the event of a failover, the specific actions required by CLOUDPORT depend on the chosen failover solution. In a hot configuration with no traffic option, the connection to the headend will be established. In warm or cold modes, missing instances start automatically, and when the configuration completes, the service resumes.

Users can also initiate a manual failover using the WebUI module. This triggers the CLOUDPORT reconfiguration process and activates the instances. Alternatively, the CLOUDPORT API can trigger failover after an integration with the customer’s end-to-end monitoring and control systems. This offers flexibility in implementing failover strategies that best suit the specific requirements and preferences of the customer.

 

Tuning and Testing for Disaster Recovery

CLOUDPORT rigorously tunes and tests its playout solution, encompassing configuration verification in realistic scenarios, optimization of infrastructure for channel types, and comprehensive testing of failover options, content handling, and schedule amendments, including end-to-end functionality and video quality. A key aspect of its disaster recovery strategy involves regular, predefined DR drills utilizing separate test endpoints and Lambda functions to validate the failover mechanism, identify weaknesses, and continuously improve DR preparedness, especially crucial with on-premises architecture modifications. This data then informs per-channel customization of failover options (hot, warm, or cold) based on channel criticality and business impact, ensuring alignment and compatibility with source systems and communication endpoints for a successful recovery.

 

Conclusion

This post outlines a robust cloud-based disaster recovery solution for channel playout on AWS using Amagi's CLOUDPORT SaaS product and an integration system, enabling hybrid operations and flexible configurations to meet specific RTO/RPO and cost requirements. The solution's efficacy is further enhanced through the emphasis on well-defined operational procedures and regular failover testing to guarantee its readiness and performance during actual disaster scenarios.

 

Original source: https://aws.amazon.com/blogs/apn/achieving-resilient-cloud-broadcasting-with-amagi-cloudport-on-aws/ 
 

Tags AWS Architecture Amagi Amagi CLOUDPORT CDN CLOUDPORT DR Disaster Recovery FAST Multi-AZ RPO RTO payout Facebook X
Comments 0
Similar posts
  1. AWS System Design Example - Instagram Architecture
    1,916
  2. Media sharing service architecture in AWS
    10,364
  3. Enterprise Data Lake Architecture based on AWS
    10,403
  4. Ad Tech Multi-Tenancy: A Spectrum of Isolation Architectures on AWS
    328
  5. Measuring Ad Viewability: AWS Architectures for Programmatic Accountability
    473
  6. AWS Ad Exchange Disaster Recovery: Active-Active, Active-Passive, and Cell Strategies - Disaster Recovery
    1,354
  7. Predictable Ad Spend: Architecting Pacing at Hyperscale
    419
  8. How Netflix Ensures Smooth Streaming with Open Connect CDN
    2,126
  9. Product Marketing & Recommendation Architecture in AWS for e-commerce website
    10,733
  10. Teraform from the scratch
    1,352
  11. Web front-end architecture in AWS for e-commerce website
    364
  12. Web Application Hosting provides the reliable, scalable, secure, and high-performance infrastructure
    10,614
  13. Time series processing architecture in AWS
    10,557
  14. Synchronous online gaming architecutre in AWS - Highly Available, Scalable & Elastic to support Millions of Players
    10,414
  15. Secure and Scalable LAMP Service Architecture in AWS
    10,658
  16. Live streaming / Static Content & Media Service based on AWS
    10,651
  17. Large scale messenger service architecture in AWS - Slack case study
    11,673
  18. Large scale computing based on huge data sets in AWS
    10,607
  19. Image Moderation Chatbot - a serverless chatbot on AWS that monitors chat channels and removes images suggestive or explicit image
    10,423
  20. Financial services grid computing in AWS
    10,354
  21. File synchronization service architecture in AWS
    10,375
  22. Fault Tolerance & High Availability based on multi Availability zones in AWS
    10,800
  23. Disaster recovery solution in AWS for local applications
    11,176
  24. Content Distribution for VOD streaming services in AWS
    10,354
  25. Checkout service architecture in AWS for e-commerce website
    11,007
  26. Batch processing composed of job manager, job store and worker based on AWS
    10,446
  27. AWS Architecture for collecting Click-Through Events on Advertisement serving
    10,372
  28. Is AWS API Gateway Disaster-Proof? DR, Benefits, and Multi-AZ Architecture Explained
    139
  29. Designing Resilient Infrastructure to Prevent Order Data Loss During Kafka Failures
    151
  30. Enterprise-Scale 100k+ TPS Order Tracking System Architecture
    198
  1. Architectural Diagram Gallery for Amazon MSK
    497
  2. Architectural Diagram Gallary for Amazon Kinesis
    517
  3. Real-time Data Streaming Solutions - Kafka vs. Kinesis Comparison
    847
  4. Building a Video Content Recommendation System with Amazon SageMaker
    521
  5. The Immense Scale and Management of Exabyte Data with AWS
    504
  6. How to change your AWS Credential Region in CLI?
    748
  7. Default Timeout for Amazon Bedrock invoke_model
    732
  8. When you face 504 Timeout Errors by Amazon ALB
    1,466
  9. When you face 504 Gateway Timeout while you wait a response from Bedrock in Fast API
    532
  10. How to overcome the prompt size limit when you use Claude via Bedrock - Chunking / Splitting the Input
    494
  11. Integrating VectorDB stored in S3 with Amazon Bedrock
    421
  12. When you need AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY for Amazon Bedrock
    532
  13. How Netflix Runs Recommendations for Hundreds of Millions of Users Using Amazon SageMaker & Metaflow
    171
  14. Why Amazon VPC satisfies with PCI-DSS and SOC 2 Type on Fintech Industry?
    641
  15. You shouldn't use Amazon CloudFront distribution as an origin
    630
  16. Creating a serverless Apache Kafka publisher using AWS Lambda
    561
  17. AWS System Design Example - Instagram Architecture
    1,916
  18. A Python script to create an EC2 Spot instance using boto3
    1,598
  19. A Python/PHP code to deregister anormalous instaces in Amazon ECS
    1,855
  20. Where to get AWS API Key at AWS Management Console?
    1,062
  21. Understanding Amazon Bedrock Agent for AI-based ChatBot
    642
  22. Media sharing service architecture in AWS
    10,364
  23. Enterprise Data Lake Architecture based on AWS
    10,403
  24. "502 Bad Gateway" Error easy to happen at the combination of nginx and node.js in AWS Elastic Beanstalk
    10,485
  25. How to Set Up and Deploy Containerized Applications with AWS ECS
    10,672
  26. Power of Containerized Deployment with AWS ECS
    10,594
  27. FAISS Already Does ANN... So Why Do Top Teams Still Pay for SageMaker?
    307
  28. Recommended Vector DB Structure for Amazon Bedrock Integration
    388
  29. Product Marketing & Recommendation Architecture in AWS for e-commerce website
    10,733
  30. What cause a 502 bad gateway error in AWS environment?
    443
Recently updated
  1. Why 100% SEO Guarantees Better User Engagement and How to Achieve It in Your Service
    27
  2. Why SPF and DKIM Are Essential for Linux Email Servers?
    24
  3. How do I create animated background for Google Meet?
    19,711
  4. MaxMind GeoLite2 vs. DB-IP Lite vs. ip-api.com: Choosing the Right Free IP Geolocation Solution
    217
  5. Meet Valkey: Why Redis Changed Its License, Why Valkey is Better, and How to Use It as a Drop-in Replacement
    85
  6. How Rogue Web Scrapers Are Stealing My Content and Destroying My Server
    153
  7. Array of arguments passed to script in PHP
    85
  8. Invalid Auction Storms in Ad Tech
    93
  9. Building MRC-Compliant Instrumentation in Ad Tech: Implementation Steps and Key Challenges
    198
  10. The Two Clocks of Ad Server Architecture
    63
  11. Frequency Cap Architecture Overview
    509
  12. Collecting Proof-of-Play from 100,000 Screens
    141
  13. Vector Search in Relational Databases (RDBs): Trends & Usage Environments
    280
  14. What is RedisVL?
    105
  15. Designing a Skill Registry Architecture: Minimize Token Usage and Maximize AI Performance
    224
  16. TPU & GPU Cluster Management Tools
    232
  17. The Concept of Scaffolding in AI Agents
    221
  18. Beyond Static Pipelines: Architecting LLM Multi-Agent Systems for Autonomous Workflow Orchestration
    576
  19. AI-DLC vs. AI-SDLC: Model-Centric vs. System-Centric AI Development
    253
  20. Fine-Tuning Open-Weight LLMs: Training, Licensing, and Deploying Custom Models with Ollama
    327
  21. Inside the Next-Generation Streaming Architecture: Ultra-Low Latency, SGAI, and AI Codecs
    197
  22. Machine Learning: Training vs. Ranking
    213
  23. The Continuous Learning Machine: Designing a Loop That Actually Turns
    217
  24. The Next-Gen Low-Latency Standards: LL-HLS & MoQ
    189
  25. Designing a Data Curation System Around a Vector Database
    215
  26. Extracting Context from Live Video: The Architecture Got Simpler When We Stopped Building Features
    229
  27. The New Ad Stack Behind Live Sports Streaming: Inside SGAI, EABN, and the Standards Race to Fix Live Monetization
    649
  28. Designing MLOps Architectures to Handle Seasonal Data Drift in EV Fleet Models
    185
  29. From 15 to 40+ FPS: Accelerating PyTorch Object Detection on Automotive ECUs
    207
  30. Understanding Data Lineage
    252