# Preparing for large-scale live streaming events on AWS -- Part 2

DevFeed: [Preparing for large-scale live streaming events on AWS -- Part 2](<https://devfeed.tech/articles/preparing-for-large-scale-live-streaming-events-on-aws-part-2-107158.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/media/preparing-for-large-scale-live-streaming-events-on-aws-part-2/>)

Author: Manish Joshi

Published: 2026-10-29T14:36:46Z

Content type: article

Language: en

Sources: [AWS for M&E Blog](<https://devfeed.tech/sources/aws-for-m-e-blog.md>)

Topics: [Streaming](<https://devfeed.tech/topics/streaming.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>), [AWS Fault Injection Service (FIS)](<https://devfeed.tech/topics/aws-fault-injection-service-fis.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [amazon-cloudfront](<https://devfeed.tech/tags/amazon-cloudfront.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-support](<https://devfeed.tech/tags/aws-support.md>), [blog](<https://devfeed.tech/tags/blog.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [capacity-planning](<https://devfeed.tech/tags/capacity-planning.md>), [chaos](<https://devfeed.tech/tags/chaos.md>), [chaos-engineering](<https://devfeed.tech/tags/chaos-engineering.md>), [content](<https://devfeed.tech/tags/content.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [events](<https://devfeed.tech/tags/events.md>), [industries](<https://devfeed.tech/tags/industries.md>), [live](<https://devfeed.tech/tags/live.md>), [live-streaming](<https://devfeed.tech/tags/live-streaming.md>), [media-entertainment](<https://devfeed.tech/tags/media-entertainment.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [testing](<https://devfeed.tech/tags/testing.md>)

## AI overview

The post recommends proving live-event readiness with realistic full-scale rehearsals, controlled failure injection, and edge delivery tuning. For CloudFront, it describes Origin Shield as a way to consolidate cache misses and protect origin capacity, alongside consistent origins, normalized cache keys, and short-segment cache efficiency. It distinguishes Lambda@Edge for compute-intensive Node.js or Python media customization from lower-cost CloudFront Functions for lightweight request-path operations. Testing proceeds from isolated components at twice expected peak, through integration at expected peak, to production rehearsal at 1.3-1.5 times peak and spike/failure tests; realistic profiles include a 60-minute ramp, sustained load, periodic spikes, and failover. The post also calls for separate signup/payment and ad-decisioning tests, viewer-based chaos thresholds with AWS Fault Injection Service, and early AWS support engagement: Unified Operations for Media or Countdown Premium, onboarded weeks before the event.

## Source excerpt

This post is part 2 in a two-part blog post series. Part 1 covers strategy, architecture evaluation, and capacity planning. Part 2 covers content delivery, nonfunctional testing, chaos engineering, and Amazon Web Services (AWS) support models.