company · deep · draft
Amazon / AWS (products & Dynamo paper)
Two layers stay distinct: the 2007 Dynamo paper (Amazon.com always-on storage design) and AWS’s public product surfaces (edge delivery, hybrid interconnect, compute/storage primitives). No Jupiter-style AWS Clos paper is claimed here.
In one sentence. Teaching Amazon-scale systems without conflating a historical retail storage paper with today’s AWS product docs, and without inventing unpublished datacenter fabric.
Why it exists
Dynamo (SOSP 2007) documents a decentralized KV store for highly available Amazon services (shopping-cart-class motivation). Separately, AWS publishes customer networking and primitives: CloudFront / Global Accelerator at the edge, Direct Connect + Transit Gateway for hybrid/multi-VPC, and S3/EBS/EFS, EC2/ECS/Lambda/Batch, API Gateway as product docs. Cross-links: `/architectures/storage-media/` (Dynamo/S3 teaching), `/architectures/apis-edge/`, `/architectures/compute-orchestration/`.
Visual walkthrough
Dynamo targets always-on Amazon services such as shopping-cart class workloads under disk, network, and datacenter failures — paper motivation, not a 2026 retail topology.
DNS steers the viewer to a suitable CloudFront POP (typically latency-oriented per docs). Do not invent unpublished PoP lists beyond product language.
Direct Connect carries BGP between on-prem and AWS. Public VIF docs emphasize AWS-side ASN 7224 and communities that scope prefix advertisement.
Control vs data plane
Control plane
AWS product control planes (API Gateway routes/throttles, TGW route tables, DX BGP communities, CloudFront distribution config) are **documented product surfaces**. Dynamo’s membership/gossip and N/R/W quorum parameters are **paper-era**. Do not equate Dynamo paper internals with live DynamoDB without a primary bridge (known unknown).
Data plane
CloudFront: DNS steers viewers to a suitable POP; hierarchy POP → Regional Edge Cache → origin over AWS backbone language in docs. Global Accelerator: anycast static IPs from the AWS edge, then carry to regional endpoints. Dynamo paper: consistent hashing + quorum read/write path. S3/EBS/EFS are separate interface contracts (see storage-media).
Request / packet path
North–south
Internet client → CloudFront POP or Global Accelerator edge → regional origin/endpoint; or client → API Gateway → service. Hybrid: on-prem → Direct Connect → DX gateway / Transit Gateway → VPC. Public VIF BGP docs emphasize AWS-side ASN **7224** — treat other Amazon ASNs as verify-before-ship (known unknowns).
East–west
Transit Gateway regional L3 hub between VPC, VPN, DX gateway, and TGW peering attachments via route tables. Internal AWS backbone TE algorithms are unpublished (unlike Google B4). Do not draw an invented AWS Clos.
Scaling & math
Dynamo publishes configurable N/R/W — teaching quorums, not live DynamoDB numbers. CloudFront features pages publish POP/REC counts as **time-stamped marketing snapshots**; re-verify at curation and never invent metro matrices. Well-Architected is guidance, not secret topology.
When it breaks
- Writes fail or hang; reads may still succeed depending on R/W.
Cause. Not enough replicas reachable for configured Dynamo-style W quorum (paper failure mode).
Mitigation. Understand N/R/W trade-offs from the Dynamo paper; do not invent live DynamoDB quorum values.
- Edge cache miss storms origin; viewers see elevated latency.
Cause. POP/REC miss path to origin under load (CloudFront delivery model).
Mitigation. Tune TTLs/origin capacity per product guidance; treat POP counts on features pages as snapshots.
- Anycast entry healthy but regional endpoint unhealthy → user errors.
Cause. Global Accelerator routes to unhealthy or misconfigured regional targets.
Mitigation. Monitor endpoint health checks; separate edge entry from regional capacity.
- On-prem prefixes missing in VPC or unexpected geographic advertisement scope.
Cause. Direct Connect BGP community / ASN misconfiguration on public VIF.
Mitigation. Follow DX routing docs (communities, ASN 7224 behavior); validate route tables on TGW/DX gateway.
- Teams treat Dynamo paper figures as DynamoDB SLOs or invent AWS Clos from Jupiter.
Cause. Conflating Amazon.com paper lineage with AWS product docs or Google fabric papers.
Mitigation. Cite Dynamo for lineage; cite AWS docs for products; leave DC Clos as known unknown.
Misconceptions
- “DynamoDB is byte-identical to the 2007 Dynamo paper.” — Related lineage themes; do not equate without a primary bridge.
- “AWS publishes a Jupiter-class Clos paper for its DCs.” — Not in this corpus; do not invent fabric generations.
- “CloudFront POP counts on a features page are permanent topology.” — Treat as time-stamped marketing snapshots.
Reference expression
Primary: Dynamo SOSP 2007 + announcement; CloudFront features/how-it-works; Global Accelerator; Direct Connect BGP + gateways; Transit Gateway; peering policy; fault-isolation PoPs whitepaper excerpt; S3 consistency; Well-Architected; EC2/Lambda as compute cross-links. review: draft. Retail paper ≠ AWS product dump.
Standards & sources
- amazon-dynamo-2007 · Dynamo KV design / N/R/WPrimary source, retrieved 2026-09-20. Dynamo: Amazon's Highly Available Key-value StoreDynamo: Amazon's Highly Available Key-value Store — Dynamo KV design / N/R/W
- amazon-dynamo-announcement-2007 · Dynamo announcement contextPrimary source, retrieved 2026-09-20. Amazon's DynamoAmazon's Dynamo — Dynamo announcement context
- aws-cloudfront-features · Edge network product claimsPrimary source, retrieved 2026-09-20. Amazon CloudFront features (global edge network)Amazon CloudFront features (global edge network) — Edge network product claims
- aws-cloudfront-how-it-works · How CloudFront delivers contentPrimary source, retrieved 2026-09-20. How CloudFront delivers contentHow CloudFront delivers content — How CloudFront delivers content
- aws-global-accelerator-how-it-works · Anycast edge entryPrimary source, retrieved 2026-09-20. How AWS Global Accelerator worksHow AWS Global Accelerator works — Anycast edge entry
- aws-direct-connect-routing-bgp · DX BGP / ASN 7224Primary source, retrieved 2026-09-20. Direct Connect routing policies and BGP communitiesDirect Connect routing policies and BGP communities — DX BGP / ASN 7224
- aws-direct-connect-gateways · DX gateway route reflection rolePrimary source, retrieved 2026-09-20. Direct Connect gatewaysDirect Connect gateways — DX gateway route reflection role
- aws-transit-gateway-how · TGW regional L3 hubPrimary source, retrieved 2026-09-20. How AWS Transit Gateway worksHow AWS Transit Gateway works — TGW regional L3 hub
- aws-peering-policy · Settlement-free Internet peering policyPrimary source, retrieved 2026-09-20. AWS Peering PolicyAWS Peering Policy — Settlement-free Internet peering policy
- aws-s3-consistency-docs · S3 strong consistency product claimPrimary source, retrieved 2026-09-20. Amazon S3 strong consistencyAmazon S3 strong consistency — S3 strong consistency product claim
- aws-well-architected · Well-Architected guidance (not topology)Primary source, retrieved 2026-09-20. AWS Well-Architected FrameworkAWS Well-Architected Framework — Well-Architected guidance (not topology)
- aws-fault-isolation-pops · PoP fault-isolation whitepaper excerptPrimary source, retrieved 2026-09-20. AWS Fault Isolation Boundaries — Points of presenceAWS Fault Isolation Boundaries — Points of presence — PoP fault-isolation whitepaper excerpt
Known unknowns
- Internal AWS datacenter fabric (Clos generation, oversubscription, control plane) comparable to Jupiter — not publicly documented at paper depth in this corpus.
- Backbone TE objectives, utilization targets, and failure domains beyond “redundant backbone” product language.
- Authoritative primary mapping of all Amazon ASNs (e.g. 16509 vs others) for deep claims — DX docs emphasize 7224 for public VIF BGP.
- Exact current POP / Regional Edge Cache / embedded POP counts (features-page numbers drift).
- Mapping from Dynamo paper to modern DynamoDB internals without a primary bridge; Amazon.com private service mesh and SLO tables.
Check yourself
How should Dynamo (2007) and AWS product docs be treated?
- As identical systems with one diagram
- As separate layers: retail paper vs public cloud products
- As proof of AWS Clos radix
- As Netflix Open Connect ASNs
Answer: As separate layers: retail paper vs public cloud products. Research rule: keep Amazon.com paper claims distinct from AWS docs.
Dynamo’s N/R/W parameters are…
- Live DynamoDB secret quotas to copy
- Paper-published quorum knobs for teaching availability/consistency trade-offs
- CloudFront POP counts
- Direct Connect community tags only
Answer: Paper-published quorum knobs for teaching availability/consistency trade-offs. Cite the paper for quorum teaching; do not invent DynamoDB internals.
Global Accelerator entry IPs are described as…
- Unicast only inside one AZ
- Anycast from the AWS edge network, then carried to regional endpoints
- OCA embedded ISP appliances
- B4 OpenFlow WAN TE
Answer: Anycast from the AWS edge network, then carried to regional endpoints. GA how-it-works: anycast edge entry.
AWS Direct Connect public VIF docs emphasize AWS-side ASN…
- 15169
- 2906
- 7224
- 65000 always
Answer: 7224. DX routing/BGP docs: ASN 7224 on the AWS side for public VIF themes.
Transit Gateway is best described as…
- A Jupiter Clos paper
- A regional L3 hub connecting VPC/VPN/DX attachments via route tables
- Netflix Steering
- Spanner TrueTime
Answer: A regional L3 hub connecting VPC/VPN/DX attachments via route tables. TGW how-it-works: regional L3 connectivity hub.
Why avoid drawing an AWS datacenter Clos here?
- Because Clos never exists in industry
- No primary AWS Jupiter-class fabric paper is in this corpus — inventing one is a defect
- Because CloudFront forbids teaching
- Because Dynamo already includes Clos figures
Answer: No primary AWS Jupiter-class fabric paper is in this corpus — inventing one is a defect. Phase 6 gate: zero invented topology; known unknowns stay visible.
Best pillar cross-link for S3 vs EBS vs EFS interfaces?
- /architectures/storage-media/
- /architectures/evpn-vxlan/
- /architectures/collapsed-core/
- /architectures/dci-multisite/
Answer: /architectures/storage-media/. storage-media teaches object/block/file with AWS product cites.
CloudFront features-page POP counts should be treated as…
- Permanent secret topology
- Time-stamped marketing snapshots to re-verify
- Dynamo N values
- Borg cell sizes
Answer: Time-stamped marketing snapshots to re-verify. Research: counts drift; stamp and do not invent metro matrices.