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

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

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

Author: Manish Joshi

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

Content type: article

Language: en

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

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>)

Tags: [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-keyspaces-for-apache-cassandra](<https://devfeed.tech/tags/amazon-keyspaces-for-apache-cassandra.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>), [aws-well-architected-framework](<https://devfeed.tech/tags/aws-well-architected-framework.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [capacity-planning](<https://devfeed.tech/tags/capacity-planning.md>), [chaos-engineering](<https://devfeed.tech/tags/chaos-engineering.md>), [content](<https://devfeed.tech/tags/content.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [events](<https://devfeed.tech/tags/events.md>), [industries](<https://devfeed.tech/tags/industries.md>), [large](<https://devfeed.tech/tags/large.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>), [planning](<https://devfeed.tech/tags/planning.md>), [series](<https://devfeed.tech/tags/series.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [testing](<https://devfeed.tech/tags/testing.md>)

## AI overview

Large live streaming events can multiply baseline concurrency within minutes and also create separate surges in sign-ups, authentication, and payments; reactive auto scaling alone may lag. The article recommends treating readiness as a multimonth effort: review the full architecture across engineering, operations, and security; focus on scaling, identity, networking, and data bottlenecks; isolate critical viewer services and define graceful degradation. For capacity, combine instance diversification with On-Demand Capacity Reservations where assurance is needed, pre-provision EKS control plane capacity, keep warm compute, and reserve load balancer headroom based on load tests. Pre-scale databases and caches, check maintenance and quotas, and request network pre-warming when testing indicates limits may be approached. Business measures--early signup campaigns, pre-event programming, and loading secondary features after playback--can smooth demand. Part 1 covers strategy, architecture, and capacity planning; content delivery, testing, chaos engineering, and AWS support models are left to Part 2.

## Source excerpt

This post is part 1 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.