8. The Cloud Architect
Physical vs. Cloud
Scalability
How to access the Cloud
Costs
9. Storage in the Physical world
DAS
(Direct-Attached Storage)
SAN
(Storage Area Network)
NAS
(Network-Attached Storage)
10. Storage in the Cloud
EC2
(Local Instance Store)
EBS
(Elastic Block Store)
S3
(Simple Storage Service)
SimpleDB, SQS, etc.
11. Understanding Durability
Designed for a Durability of:
With 10,000 objects,
99.999999999 %
on average, you lose one
every 10,000,000 years
S3
(Simple Storage Service)
23. The Cloud Architect
Physical vs. Cloud
Scalability
How to access the Cloud
Costs
24. Acronyms!
Launch EC2 with EBS behind ELB
with your domain on Route 53
and your videos on CloudFront, backup to S3
and your DB on RDS with Multi-AZ.
27. Design for Failure and nothing will fail
Backup/Restore strategy
Become impervious to reboot/relaunch
Move in-memory sessions to data store
Use Availability Zones (AZ), distribute EC2
Use Elastic Load Balancer
Use Relational Database Service + Multi-AZ
Use Elastic IP
29. Regions
Region: set of multiple Data Centers
US West-2
US East
AP Japan
EU West
US West-1
AP Singapore
30. Regions
Region: set of multiple Data Centers
US West-2
GovCloud
US East
AP Japan
EU West
US West-1
AP Singapore
31. Availability Zones (AZ)
Distinct locations, insulated from failures
US West-2
A
B
US East
A
B
AP Japan
A
B
A
B
C
A
B
C
C
D
EU West
US West-1
A
B
AP Singapore
32. Availability Zones (AZ)
Distinct locations, insulated from failures
Low latency connectivity within same region
US West-2
A
B
US East
A
B
AP Japan
A
B
A
B
C
A
B
C
C
D
EU West
US West-1
A
B
AP Singapore
34. Amazon CloudFront + Route 53
Content Delivery Network (CDN) + DNS
Seattle
Amsterdam
New York
London
Newark
Stockholm
Palo Alto
Dublin
Tokyo
Frankfurt
Paris
Los Angeles
Ashburn
Jacksonville
Hong Kong
Dallas
St.Louis
Miami
Singapore
Sao Paulo
35. Multi-AZ
US West-2
A
B
US East
A
B
AP Japan
A
B
A
B
C
A
B
C
C
D
EU West
US West-1
A
B
AP Singapore
57. Dynamic and Static
Keep dynamic data closer to EC2.
E.g.: use same AZ for data-intensive applications
Keep static data closer to end-user
E.g.: use CloudFront to distribute content
Tools: Custom AMI (Amazon Machine Image),
bootstrap EC2 instances, Elastic IP
58. Remapping an Elastic IP
ec2-50-16-126-161.compute-1.amazonaws.com
web 1
107.20.243.251
web 2
68. Don t fear constraints
Need Better Database performance?
Sharding / Multiple Read-Only / Clustering
69. Don t fear constraints
Need Better Database performance?
Sharding / Multiple Read-Only / Clustering
Need More RAM?
Shared Distributed cache (Memcached)
70. Don t fear constraints
Need Better Database performance?
Sharding / Multiple Read-Only / Clustering
Need More RAM?
Shared Distributed cache (Memcached)
Need Faster disks?
Multiple EBS in Raid configuration
71. Multi-AZ for RDS
ap-southeast-1a
ap-southeast-1b
Master DB
RDS
RDS
Standby Replica
(as shown earlier)
79. IAM: Identity Access Management
Manage Users / Groups
Manage security credentials
Control access to API
Control access to specific resources
Control access based on environment variables
Cost: zero.
80. Net
Networking Security
Internet
Internet
AWS Direct Connect
Amazon Virtual Private Dedicated Instances
Cloud (VPC)
Dedicated connection between Create and connect your Run your applications in a single
your IT infrastructure and the isolated AWS resources and tenant model within the AWS
AWS datacenters
your IT infrastructure via a infrastructure
secure VPN connection
82. Seven principles: recap
1. Design for failure and nothing will fail
2. Decouple
3. Elasticity
4. Dynamic and Static
5. Think Parallel
6. Don t fear constraints
7. Security
84. Additional resources
Architecture on AWS:
http://aws.amazon.com/architecture
White paper: Cloud Architecture
http://j.mp/aws-architecture
This presentation:
http://slidesha.re/aws-architecting-cloud
