Mike Haken

Your data can't leave the jurisdiction, but your workload still has to survive a Region degradation. This chalk talk explores architecture patterns that address both resilience and data residency together.

Gain hands-on experience building and testing resilient multi-AZ applications. Learn to use Amazon CloudWatch dashboards, insights rules, and composite alarms for comprehensive health monitoring.

Essential services that power global economies and critical infrastructure demand exceptional resilience. Through nearly two decades of focused innovation, AWS has developed core engineering practices and operational approaches that power critical workloads worldwide.

In this workshop, get hands-on experience building, operating, and testing a resilient Multi-AZ application. Use Amazon CloudWatch dashboards, insights rules, and composite alarms to observe the health of your application.

In this session, learn about a resilience analysis framework and how you can apply it to have a consistent and repeatable process for analyzing your workloads. Learn how to discover failure modes and how they could impact your workloads.

Many organizations run their workloads in highly available, Multi-AZ configurations. These architectures perform well during binary failure events but often encounter problems with gray failures.

Gray failures can escape quick and definitive detection while impacting workloads running in the cloud. Building resilient applications that can survive single instance and single Availability Zone gray failures requires you to implement specific observability and mitigation strategies.

Many organizations run their workloads in highly available multi-Availability Zone (AZ) configurations. These architectures perform well during binary failure events, but often encounter problems with “gray failures.” The manifestations of these types of failures can be subtle and defy quick and definitive detection.

In this session, discover how AWS uses predictable isolation boundaries to create zonal, regional, and global services. Then, dive deep into best practices for utilizing global services to prevent single points of failure.