This document discusses architecting for high availability on AWS. It identifies four key principles: 1) design for failure by avoiding single points of failure, 2) use multiple availability zones, 3) implement scaling to scale resources up or down automatically, and 4) build loosely coupled systems using services like SQS. The goal is to design applications that can continue functioning even when failures occur.

1. Architecting For High Availability
Guy Ernest
Solutions Architect

4. AWS BUILDING BLOCKS
Inherently Fault-Tolerant
Services
Fault-Tolerant with the
right architecture
Amazon S3
Amazon DynamoDB
Amazon CloudFront
Amazon SWF
Amazon SQS
Amazon SNS
Amazon SES
Amazon Route53
Elastic Load Balancing
AWS IAM
AWS Elastic Beanstalk
Amazon
ElastiCache
Amazon EMR
Amazon Redshift
Amazon CloudSearch
 Amazon EC2
 Amazon EBS
 Amazon RDS
 Amazon VPC

9. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY
ZONES
3. SCALING
4. LOOSE COUPLING

10. #1
DESIGN FOR FAILURE
●○○○

11. « Everything fails
all the time »
Werner Vogels
CTO of Amazon

12. AVOID SINGLE POINTS OF FAILURE

13. AVOID SINGLE POINTS OF FAILURE
ASSUME EVERYTHING FAILS,
AND WORK BACKWARDS

14. YOUR GOAL
Applications should continue to function

20. HEALTH CHECKS

26. #2
MULTIPLE
AVAILABILITY ZONES
●●○○

27. AVAILABILITY ZONES

28. US-WEST (N. California)
EU-WEST (Ireland)
ASIA PAC (Tokyo)
ASIA PAC
(Singapore)
US-WEST (Oregon)
SOUTH AMERICA (Sao Paulo)
US-EAST (Virginia)
GOV CLOUD
ASIA PAC (Sidney)

30. AMAZON RDS
MULTI-AZ

37. AMAZON ELB AND
MULTIPLE AZs

40. #3
SCALING
●●●○

42. AMAZON CLOUDWATCH
MONITORING FOR AWS RESOURCES

44. AUTO SCALING
SCALE UP/DOWN EC2 CAPACITY

54. AUTO SCALING
SCALE UP/DOWN EC2 CAPACITY

63. HEALTH CHECKS
+
AUTO SCALING

68. HEALTH CHECKS
+
AUTO SCALING
=
SELF-HEALING

70. #4
LOOSE
COUPLING
●●●●

71. BUILD LOOSELY
COUPLED SYSTEMS
The looser they are coupled,
the bigger they scale,
the more fault tolerant they get…

74. PUBLISH
& NOTIFY
RECEIVE TRANSCODE

75. AMAZON SQS
SIMPLE QUEUE SERVICE

76. PUBLISH
& NOTIFY
RECEIVE TRANSCODE

83. VISIBILITY TIMEOUT

91. BUFFERING

98. CLOUDWATCH METRICS
FOR AMAZON SQS
+
AUTO SCALING

103. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. LOOSE COUPLING

104. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. LOOSE COUPLING

105. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. LOOSE COUPLING

106. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. LOOSE COUPLING

107. YOUR GOAL
Applications should continue to function

108. IT’S ALL ABOUT
CHOICE
BALANCE COST & FAULT-TOLERANCE

109. AWS ARCHITECTURE CENTER
http://aws.amazon.com/architecture
AWS TECHNICAL ARTICLES
http://aws.amazon.com/articles
AWS BLOG
http://aws.typepad.com
AWS PODCAST
http://aws.amazon.com/podcast