All posts
Retail & E-commerce

Black Friday 2026 Readiness on AWS: Load Testing, Quotas and the Things That Fall Over

By

October 26, 2026

6 min read

Black Friday is November 27 and Cyber Monday November 30. Most peak-day outages are not raw capacity: they are a quota nobody raised, a database connection limit, a third-party API that throttles, or a cache that was never warm. A four-week plan, the AWS limits worth checking, and what to freeze.

E-commerce
Load Testing
Scaling
Reliability
Peak Traffic

Peak traffic finds the weakest link, and it is rarely the one the team scaled. Four weeks is enough to find it first if you test the whole path, including the parts you do not run.

Limits worth checking now

Limit

Default

Action

Lambda concurrency per account and Region

1,000 concurrent executions

Request an increase well ahead; set reserved concurrency for checkout so other functions cannot starve it

API Gateway account throttle

10,000 requests per second with burst capacity, per Region

Check against expected peak; raise through Service Quotas

Database connections

Set by instance memory on RDS and Aurora

Use a pooler; test at peak concurrency, not average

Third-party APIs (payments, tax, shipping, search)

Each provider's rate limits

Ask providers for their limits and peak guidance; add timeouts and fallbacks

Load balancer capacity for sudden spikes

Scales automatically

For a known spike, reserve capacity with load balancer capacity unit reservation

DynamoDB on-demand tables

Scale automatically from previous peaks

Pre-warm with warm throughput if launch-day traffic exceeds anything the table has seen

Want a second opinion on this for your system?

Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.

Four weeks

  1. Week 1: set the target (last year's peak times your growth, times a safety factor), map the full checkout path including third parties, and file quota increases.

  2. Week 2: load test production-like environments with realistic flows (browse, search, cart, checkout), using AWS's Distributed Load Testing solution or your own tool. Find the first thing that breaks.

  3. Week 3: fix it, retest, find the next one. Warm caches and CDNs for top products. Rehearse the incident process.

  4. Week 4: change freeze on checkout, payments and infrastructure, dashboards and alerts on the business metric (orders per minute), and people on call with clear owners.

Degrade on purpose

  • Decide in advance what to turn off under load: recommendations, reviews, personalization.

  • Put a queue in front of anything slow that does not need to happen during the request, such as confirmation email and ERP updates.

  • Have a waiting room ready for flash sales, so overload produces a queue rather than errors.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of October 26, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.