Amazon Web Services (AWS) provides a platform that is ideally suited for building highly available systems, enabling you to build reliable, affordable, fault-tolerant systems that operate with a minimal amount of human interaction. This session covers many of the high-availability and fault-tolerance concepts and features of the various services that you can use to build highly reliable and highly available applications in the AWS Cloud: architectures involving multiple Availability Zones, including EC2 best practices and RDS Multi-AZ deployments; loosely coupled and self-healing systems involving SQS and Auto Scaling; networking best practices for high availability, including Elastic IP addresses, load balancing, and DNS; leveraging services that inherently are built with high-availability and fault tolerance in mind, including S3, Elastic Beanstalk and more.

2. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

3. LET’S BUILD A SYSTEM

4. LET’S BUILD A
HIGHLY AVAILABLE
SYSTEM

5. AWS BUILDING BLOCKS
Inherently Highly Available and Highly Available with
Fault Tolerant Services the right architecture
 Amazon S3  Amazon SQS  Amazon EC2
 Amazon DynamoDB  Amazon SNS  Amazon EBS
 Amazon CloudFront  Amazon SES  Amazon RDS
 Amazon Route53  Amazon SWF  Amazon VPC
 Elastic Load Balancing  …

6. AWS BUILDING BLOCKS
Inherently Highly Available and Highly Available with
Fault Tolerant Services the right architecture
 Amazon S3  Amazon SQS  Amazon EC2
 Amazon DynamoDB  Amazon SNS  Amazon EBS
 Amazon CloudFront  Amazon SES  Amazon RDS
 Amazon Route53  Amazon SWF  Amazon VPC
 Elastic Load Balancing  …

11. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

12. # 1
DESIGN FOR FAILURE
●○○○○

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

14. AVOID SINGLE POINTS OF FAILURE

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

16. YOUR GOAL
Applications should continue to function

20. AMAZON EBS
ELASTIC BLOCK STORE

25. AMAZON ELB
ELASTIC LOAD BALANCING

28. HEALTH CHECKS

34. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

35. # 2
MULTIPLE
AVAILABILITY ZONES
●●○○○

36. AVAILABILITY ZONES

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

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

39. AMAZON RDS
MULTI-AZ

44. AMAZON ELB AND
MULTIPLE AZs

47. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

48. # 3
SCALING
●●●○○

51. AUTO SCALING
SCALE UP/DOWN EC2 CAPACITY

61. UNEXPECTED
SPIKES

62. EXPECTED
SPIKES

63. DATA TIER

64. AWS BUILDING BLOCKS
Inherently Highly Available and Highly Available with
Fault Tolerant Services the right architecture
 Amazon S3  Amazon SQS  Amazon EC2
 Amazon DynamoDB  Amazon SNS  Amazon EBS
 Amazon CloudFront  Amazon SES  Amazon RDS
 Amazon Route53  Amazon SWF  Amazon VPC
 Elastic Load Balancing  …

65. AWS BUILDING BLOCKS
Inherently Highly Available and Highly Available with
Fault Tolerant Services the right architecture
 Amazon S3  Amazon SQS  Amazon EC2
 Amazon DynamoDB  Amazon SNS  Amazon EBS
 Amazon CloudFront  Amazon SES  Amazon RDS
 Amazon Route53  Amazon SWF  Amazon VPC
 Elastic Load Balancing  …

66. AWS BUILDING BLOCKS
Inherently Highly Available and Highly Available with
Fault Tolerant Services the right architecture
 Amazon S3  Amazon SQS  Amazon EC2
 Amazon DynamoDB  Amazon SNS  Amazon EBS
 Amazon CloudFront  Amazon SES  Amazon RDS
 Amazon Route53  Amazon SWF  Amazon VPC
 Elastic Load Balancing  …

67. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

68. # 4
SELF-HEALING
●●●●○

69. HEALTH CHECKS
+
AUTO SCALING

74. HEALTH CHECKS
+
AUTO SCALING
=
SELF-HEALING

75. DEGRADED MODE

76. AMAZON S3
STATIC WEBSITE
+
AMAZON ROUTE53
WEIGHTED RESOLUTION

80. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

81. # 5
LOOSE
COUPLING
●●●●●

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

83. AMAZON SQS
SIMPLE QUEUE SERVICE

84. PUBLISH&
RECEIVE TRANSCODE
NOTIFY

85. PUBLISH&
RECEIVE TRANSCODE
NOTIFY

92. VISIBILITY TIMEOUT

100. BUFFERING

107. CLOUDWATCH METRICS
FOR AMAZON SQS
+
AUTO SCALING

114. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

115. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

116. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

117. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

118. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

119. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

120. 1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING

121. YOUR GOAL
Applications should continue to function

122. IT’S ALL ABOUT
CHOICE
BALANCE COST & HIGH AVAILABILITY

123. 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

124. 4:05PM ARC301: Intro to Chaos Monkey & the Simian Army
4:05PM MBL303: Scalable Mobile and Web Apps
Lab 4 Scaling
Lab 12 Loose Coupling

125. We are sincerely eager to
hear your feedback on this
presentation and on re:Invent.
Please fill out an evaluation
form when you have a
chance.