7.
Slide213a o h N. Virginia N. California Ireland Singapore Regional Expansion g First 5 years: 4 regions
8.
Slide214a o h AWS GovCloud West N. Virginia Oregon N. California São Paulo Ireland Frankfurt Singapore Sydney Beijing Tokyo First 5 years: 4 regions Next 5 years: 7 regions Regional Expansion m c g b n s k v
9.
Slide215a e o q t i h p AWS GovCloud West Montreal Ohio N. Virginia Oregon N. California São Paulo Ireland London Frankfurt Paris Mumbai Singapore Sydney Seoul Ningxia Beijing Tokyo Cape Town u Hong Kong Sweden AWS GovCloud East First 5 years: 4 regions 2016–2018: 9 regions and 1 local region Next 5 years: 7 regions Regional Expansion d m c g b n s k v e e Osaka t e d p Milan p Coming soon: 4 regions p Bahrain
10.
AWS Region DesignAWS Pop-up Loft I Johannesburg AWS Region Design AWS Regions are comprised of multiple AZs for high availability, high scalability, and high fault tolerance. Applications and data are replicated in real time and consistent in the different AZs 10 AWS Availability Zone (AZ) A Region is a physical location in the world where we have multiple Availability Zones. Availability Zones consist of one or more discrete data centers, each with redundant power, networking, and connectivity, housed in separate facilities. AZ AZ AZ AZ Transit Transit Datacenter Datacenter Datacenter AWS Region
11.
Availability ZonesAWS Pop-up Loft I Johannesburg •Fully isolated infrastructure with one or more datacenters •Meaningful distance of separation •Unique power infrastructure •Many 100Ks of servers at scale •Data centers connected via fully redundant and isolated metro fiber Availability Zones
12.
Anatomy of an AWS RegionAWS Pop-up Loft I Johannesburg Most with 3+ AZs Some with as many as 6 AZs — Intra-AZ connections Anatomy of an AWS Region Metro Fiber: Intra-AZ Connections
13.
Anatomy of an AWS RegionAWS Pop-up Loft I Johannesburg — Intra-AZ connections — Inter-AZ connections Anatomy of an AWS Region Metro Fiber: Inter-AZ Connections
14.
Anatomy of an AWS RegionAWS Pop-up Loft I Johannesburg 2 redundant Transit Centers Highly peered & connected — Intra-AZ connections — Inter-AZ connections — Transit Center connections Redundant transit centers Anatomy of an AWS Region
15.
Slide1274AWS Pop-up Loft I Johannesburg 160 Global
16.
Slide1289AWS Pop-up Loft I Johannesburg Inside an Edge POP Multiple AWS services: AWS Direct Connect Amazon CloudFront (CDN) Amazon Route 53 (DNS) AWS Shield (DDoS Protection) AWS Global network access External internet connectivity
18.
Why have a backbone network?AWS Pop-up Loft I Johannesburg Why have a backbone network? Security Traffic traverses our infrastructure rather than the internet Availability Controlling scaling and redundancy Traffic operates over Amazon-controlled infrastructure Reliable performance Controlling specific paths customer traffic traverses Connecting closer to customers Avoiding internet “hot spots” or sub-optimal external connectivity All commercial Region-to-Region traffic traverses the backbone except China
19.
Backbone path additionsAWS Pop-up Loft I Johannesburg Backbone path additions Three new cable additions to the AWS Global network: Hawaiki Jupiter Bay to Bay Express
21.
Advantages of purpose-build custom serversAWS Pop-up Loft I Johannesburg •Work directly with component manufacturers like memory, HDD, CPU •Design optimized for specific workloads •Hardware and software not burdened with unnecessary features •Highly utilized Advantages of purpose-build custom servers
22.
Building an AWS RegionAWS Pop-up Loft I Johannesburg Planning Design Construction Building an AWS Region
23.
AWS renewable energy commitmentAWS Pop-up Loft I Johannesburg •Commitment to 100% renewable energy •Achieved 50% renewable in January 2018 •4.8 MW battery pilot with Tesla •American Council on Renewable Energy (ACORE) •Advance Energy Buyers Group AWS renewable energy commitment
Foundations of AWS Global Cloud Infrastructure - 20 September - 15:00
Thank you for your comment.