Aws Re:invent 2025 - Global Resilient Apps: Guide To...

🦄 Making great presentations more accessible. This project aims to enhances multilingual accessibility and discoverability while maintaining the integrity of original content. Detailed transcriptions and keyframes preserve the nuances and technical insights that make each session compelling.

📖 AWS re:Invent 2025 - Global Resilient Apps: Guide to Multi-AZ/Region Architecture with ELB (NET311)

In this video, Jon Zobrist and Felipe da Silva from the ELB team explain multi-AZ and multi-region resiliency strategies using AWS Elastic Load Balancing. They cover how ELB uses DNS-based failover with 60-second TTLs, Route 53 health checks, and target health checks to route traffic away from unhealthy zones. Key topics include cross-zone load balancing trade-offs, static stability through pre-provisioning capacity for at least one AZ failure, configurable target group health thresholds to trigger failover before 100% failure, and Route 53 Application Recovery Controller for zonal shifts. For multi-region resilience, they discuss using Route 53 failover and weighted records, DNS load shedding to prevent congestive collapse, deployment pipelines with zonal rollouts, graceful degradation strategies, and the importance of client-side best practices like honoring DNS TTLs and implementing connection pooling. They emphasize that configuration and deployment changes cause most outages, making testing and change management critical.

; This article is entirely auto-generated while preserving the original presentation content as much as possible. Please note that there may be typos or inaccuracies.

Welcome to Global Resilient Apps, a guide to multi-AZ and multi-region resiliency using ELB. I'm Jon Zobrist, Head of Customer Success for the ELB team, and with me is Felipe da Silva, Principal Solutions Architect on my team. Thank you all so much for coming out so early and during a keynote. We really appreciate it, and for those of you who are here from Felipe's talk the other day, good to see you. We're going to go over some guiding principles, then we're going to talk about multi-AZ resiliency and then multi-region resiliency, and then we'll wrap up with some Q&A. If we run out of time, which we probably will, we will be outside in the hall afterwards when we have free time. If you have any other questions, we're happy to chat about your specific architecture.

Let's jump right in with everyone's favorite quote from AWS of all time: "Everything fails, all the time." Our

Source: Dev.to