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. 

1. Architec(ng for High Availability
Ran Tessler, AWS Solu0ons Architecture Manager

2. 1. DESIGN FOR FAILURE
2. USE MULTI-AZ
3. SCALING
4. LOOSE COUPLING

3. LET’S BUILD A SYSTEM

4. LET’S BUILD A
HIGHLY AVAILABLE
SYSTEM

5. AWS BUILDING BLOCKS
Inherently Highly Available and
Fault Tolerant Services
Highly Available
with the right
architecture! Amazon S3
! Amazon DynamoDB
! Amazon CloudFront
! Amazon SWF
! Amazon SQS
! Amazon SNS
! Amazon SES
! Amazon Route53
" Amazon EC2
" Amazon EBS
" Amazon RDS
" Amazon VPC
! Elastic Load Balancing
! AWS IAM
! AWS Elastic Beanstalk
! Amazon Kinesis
! Amazon CloudWatch
! Amazon EC2 Container
Service
! Amazon Lambda
! …

10. 1. DESIGN FOR FAILURE
2. USE MULTI-AZ
3. SCALING
4. LOOSE COUPLING

11. #1
DESIGN FOR
FAILURE
●○○○

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

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

14. AVOID SINGLE POINTS OF
FAILURE.
ASSUME EVERYTHING FAILS,
AND DESIGN BACKWARDS.

15. YOUR GOAL:
Applications should continue to function even if
the underlying physical hardware fails or is
removed or replaced

19. AMAZON ELB
ELASTIC LOAD BALANCING

22. AMAZON ELB
HEALTH CHECKS

28. 1. DESIGN FOR FAILURE
2. USE MULTI-AZ
3. SCALING
4. LOOSE COUPLING

29. #2
USE MULTIPLE
AVAILABILITY ZONES

31. AMAZON RDS
MULTI-AZ

36. AMAZON ELB AND
MULTIPLE AZs

39. 1. DESIGN FOR FAILURE
2. USE MULTI-AZ
3. SCALING
4. LOOSE COUPLING

40. #3
SCALING

43. AUTO SCALING
SCALE UP/DOWN EC2 CAPACITY

52. HEALTH CHECKS
+
AUTO SCALING

57. HEALTH CHECKS
+
AUTO SCALING
=
SELF-HEALING

58. DATA TIER

59. AWS BUILDING BLOCKS
Inherently Highly Available and
Fault Tolerant Services
Highly Available
with the right
architecture! Amazon S3
! Amazon DynamoDB
! Amazon CloudFront
! Amazon SWF
! Amazon SQS
! Amazon SNS
! Amazon SES
! Amazon Route53
" Amazon EC2
" Amazon EBS
" Amazon RDS
" Amazon VPC
! Elastic Load Balancing
! AWS IAM
! AWS Elastic Beanstalk
! Amazon Kinesis
! Amazon CloudWatch
! Amazon EC2 Container
Service
! Amazon Lambda
! …

60. 1. DESIGN FOR FAILURE
2. USE MULTI-AZ
3. SCALING
4. LOOSE COUPLING

61. #4
LOOSE COUPLING

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

63. AMAZON SQS
SIMPLE QUEUE SERVICE

64. PUBLISH
& NOTIFY
RECEIVE TRANSCODE

65. PUBLISH
& NOTIFY
RECEIVE TRANSCODESQS SQS

72. VISIBILITY
TIMEOUT

78. BUFFERING

84. CLOUDWATCH METRICS
FOR AMAZON SQS
+
AUTO SCALING

91. 1. DESIGN FOR FAILURE
2. USE MULTI-AZ
3. SCALING
4. LOOSE COUPLING

92. YOUR GOAL:
Applications should continue to function even if
the underlying physical hardware fails or is
removed or replaced

93. WHAT’S NEXT…
13:45 – How Viber uses Amazon SQS for high scale and decoupling
14:45 – How Beamr uses Amazon SWF for video optimization
16:00 – How Glide uses AWS Lambda for increased simplicity and scale

94. Ran Tessler
AWS Solu0ons Architecture Manager
tesslerr@amazon.com