This document discusses high availability website design. It recommends hosting static assets on Amazon S3 for high durability and redundancy. Content delivery can be improved with Amazon CloudFront. Dynamic applications can be built on Amazon EC2 across availability zones and auto-scaled for failure recovery. Databases can use Amazon RDS for management. Multi-tier designs with load balancing, caching, and auto-scaling provide tolerance to instance and availability zone failures.

1. High Availability
Websites
Matt Wood
T E C H N O L O G Y E VA N G E L I S T

2. AGENDA
High Performance Websites: Part 1
1. Availability
2. Static content
3. Multi-tier applications
4 . Per formance boost
5. Summar y

3. Spectrum of websites

4. Static Dynamic
Spectrum of websites

5. Static Dynamic
Simple Complex
Spectrum of websites

6. Static Dynamic
Simple Complex
Niche Mass market
Spectrum of websites

7. Availability is
important

8. Support your
customers

9. Support your
business

10. However...

11. “
Everything fails
all the time
”
Werner Vogels, Amazon CTO

12. Infrastructure
services can
save the day

13. Focus on your stuff

14. Patterns for
availability

15. 1. Static content

16. Images
Stylesheets
Streaming
content
Assets
Video Javascript

17. Templates
Images
Stylesheets
Streaming
content
Web
pages Assets
Blog posts
Video Javascript
PDFs

18. High High
redundancy availability
Amazon S3
High
durability

19. http://s3.amazonaws.com/bucketname/objectid
http://bucketname.s3.amazonaws.com/objectid

20. https://s3.amazonaws.com/bucketname/objectid
https://bucketname.s3.amazonaws.com/objectid

21. Perfect for asset
hosting

22. Perfect for website
hosting

23. Let’s see how...

24. aws.amazon.com/console

27. Make everything public

28. index.html Text
http://mza.s3.amazon.com/site/index.html

31. https://mza.s3.amazon.com/site/index.html

32. https://mza.s3.amazon.com/site/index.html

33. :(

35. Unfriendly, brittle URL:
http://mza.s3.amazonaws.com/s3/index.html

36. S3 websites

37. Root objects

38. Error pages

39. Let’s see how...

41. https://my-website.s3-website-eu-west-1.amazon.com

42. https://my-website.s3-website-eu-west-1.amazon.com

43. Content
distribution

44. Increased latency

45. CloudFront
Powerful content delivery network

46. Global edge caching
+
Friendly URLs

47. Let’s see how!

50. d19r58gd5nvk1.cloudfront.net

51. d19r58gd5nvk1.cloudfront.net/site/index.html

52. Update
DNS CNAME

53. friendly-example.com/index.html

54. Set CloudFront
Default Root Object

55. API or S3 client

56. CloudBerry Explorer
API or S3 client
Cyberduck

57. amazon_s3.html

58. friendly-example.com

59. friendly-example.com
Global DNS CNAME
Global Amazon CloudFront
Regional Amazon S3
Redundant storage

60. 2. Dynamic or
multi-tier content

61. Ruby on Rails
PHP
Django
Perl
Dynamic
Spring
Database
Java
Data store

62. Blogs
E-commerce Gaming
Dynamic
Productivity
Apps
Social networks

63. Elastic Multiple
capacity instance sizes
Amazon EC2
On-demand

64. Mastering Multiple
failure availability zones
High availability
Automation and
monitoring

65. H I G H AVA I L A B I L I T Y W I T H E C 2
Single server
fail over

66. Elastic IP
EC2 instance

67. Elastic IP
EC2 instance
EBS storage
EBS snapshot

68. Elastic IP
EC2 instance
EBS storage
EBS snapshot

69. Elastic IP
EC2 instance
EBS storage
EBS snapshot

70. Elastic IP
EC2 instance
EBS storage
EBS snapshot

71. Cheap, but not ideal

72. Requires monitoring
and automation
‘Hot swap’ possible

73. H I G H AVA I L A B I L I T Y W I T H E C 2
Horizontal
redundancy

74. Applications with
multiple tiers

75. Web servers
Application servers
Data store

76. Redundancy at
each tier

77. Web servers
Application servers
Data store

78. Tolerant to
instance failure

79. Web servers
Application servers
Data store

80. Tolerant to
AZ failure

81. eu-west-1 eu-west-2
Web servers
Application servers
Data store

82. Scale in and out
(if you need to)

83. Web servers
Application servers
Data store

84. Load balance

85. Elastic Load Balancer
Web servers
Application servers
Data store

86. Let’s take a look!

87. Spin up your stack
+
Prepare for battle!

89. MySQL server with
Amazon RDS

91. Endpoint

92. Configure app +
cut an AMI

93. Create Image

94. Spin up
horizontal
layer

96. 4

99. http://ec2-46-137-20-114.eu-west-1.compute.amazonaws.com

100. http://ec2-46-137-20-114.eu-west-1.compute.amazonaws.com

101. Load balance

102. Elastic Load Balancer
Web servers
Amazon RDS

109. Elastic Load Balancer
Web servers
Amazon RDS

110. Multiple AZ
deployment

111. Elastic Load Balancer
eu-west-1a eu-west-1b
Web servers
Amazon RDS

112. eu-west-1b

113. eu-west-1b

115. eu-west-1a

116. eu-west-1b

117. Elastic Load Balancer
eu-west-1a eu-west-1b
Web servers
Amazon RDS

118. Recovery from
failure

119. Autohealing &
autoscaling

120. ELB
CloudWatch Autoscaling

121. Elastic Load Balancer
Autoscaling group
Metrics
CloudWatch

122. Elastic Load Balancer
Autoscaling group
Metrics
CloudWatch

123. Elastic Load Balancer
Autoscaling group
Metrics
CloudWatch
Autoscaling service

124. Elastic Load Balancer
Autoscaling group
Metrics
CloudWatch
Autoscaling service

125. Elastic Load Balancer
Autoscaling group
Metrics
CloudWatch
Autoscaling service

126. as-create-launch-config
PHPLaunchConfig
--image-id ami-132216677
--instance-type m1.large
--key amazon-web
--group "Web and SSH"

127. as-create-auto-scaling-group
PHPScalingGroup
--launch-configuration PHPLaunchConfig
--availability-zones eu-west-1a, eu-west-1b
--min-size 10
--max-size 10
--load-balancers lamp-load-balancer

128. as-create-or-update-trigger
CPUUtlization
DiskReadBytes
DiskReadOps
DiskWriteBytes
DiskWriteOps
NetworkIn
NetworkOut
DatabaseConnections
FreeStorageSpace
ReadLatency
ReadThroughput
SwapUsage
WriteLatency

129. Automation

130. Custom AMIs

131. CloudFormation

132. Bootstrap

133. Configuration
management

134. Elastic Load Balancer
eu-west-1a eu-west-1b
Auto-scaling
web servers
Amazon RDS

135. Elastic Load Balancer
eu-west-1a eu-west-1b
Auto-scaling
web servers
MySQL Amazon RDS

136. Extra I G H A V A I L A B I L I T Y W I T H E C 2
H
credit!
Performance

137. Horizontal layers
are flexible

138. Add caching

139. HTTP cache
Web servers
Application servers
Data cache
Data store

140. HTTP cache
Web servers
Application servers
Data cache
Data store

141. Varnish:
HTTP reverse proxy

142. Memcached:
key/value store

143. May require
application refactor

144. Custom metrics

145. AGENDA
High Performance Websites
1. Availability
2. Static content
3. Multi-tier applications
4 . Per formance boost
5. Summar y

146. Importance of
high availability

147. Hosting assets on
Amazon S3

148. Content distribution with
Amazon CloudFront

149. Hosting static web content
on S3 and CloudFront

150. Web applications on
Amazon EC2

151. Designing for availability

152. Multi-tier application
hosting

153. Database management
with Amazon RDS

154. Slides + video
available soon

155. Thank you!

156. Q U E S T I O N S + C O M M E N T S
matthew@amazon.com
@mza
O N T W I T T E R