AWS S3 (Amazon Simple Storage Service, 2006)

AWS S3 is the foundational object-storage instance of the AWS cloud platform — launched March 14, 2006, five months before EC2 (August 2006). S3 was the FIRST AWS public service and the move that opened Amazon Web Services as a public-cloud business. Designed by Andy Jassy's team and Werner Vogels under Bezos's 2002-2005 internal-API mandate. Initial pricing: ~$0.15/GB/month (2006); fallen to ~$0.023/GB/month by 2024 — a 6.5x real-price reduction, the canonical hyperscale cost-curve signal. Durability claim: eleven nines (99.999999999%) via cross-AZ redundant storage. Objects stored: >280 trillion (AWS 2024 figures). Total requests served: trillions/day. S3 is the universal data lake substrate for DM-Day digital machines: Pinterest, Dropbox, Netflix (encoded content pre-CDN), Spotify (audio files), GitHub (Git objects), Reddit (media), Airbnb (property photos), Slack (file storage), and most serverless ML training pipelines. The s3:// URI scheme has become an informal standard — S3 Compatible API is now implemented by Cloudflare R2, MinIO, Backblaze B2, DigitalOcean Spaces, and every competing object-storage offering, making S3's API grammar the lingua franca of cloud object storage (a DM-Day semiotic lock-in beyond the platform itself). Motor = flywheel (NOT push like the class parent): more objects stored → more ecosystem tools (AWS SDK, Boto3, CDK, Terraform AWS provider, Spark S3A, DeltaLake, etc.) → lower unit cost through scale → more storage growth → more objects. The flywheel has a secondary arm: more data in S3 → more ML training pipelines on S3 → more AWS compute (EC2/SageMaker/ Bedrock) sold → Amazon ARPU per customer rises. Key events: S3 launch 2006-03-14. Netflix migration from own datacenters to S3+CloudFront 2008-2016 (canonical early-adopter trajectory). us-east-1 S3 outage February 2017 (~$300M customer impact; revealed S3 as blast-radius OPP for large fraction of DM internet). S3 Object Lambda 2021. S3 Express One Zone 2023 (high-performance single-AZ tier). Substrate note (C5 gap): S3's operational grammar is semiotic (API + URI namespace as naming substrate), cognitive (ML-training-data pipelines; semantic indexing), and social (the s3-compatible-API community of practice that converged around the AWS API grammar). Substrate.institutional is NOT in the enum; [STUB-substrate-enum-gap] recorded. LM anti-pattern note: S3 is an "always-on-energy" machine — 11-nines durability requires cross-AZ replication consuming grid electricity 24/7. LM heretic cards (machine:capture-resistant-ai-infrastructure-class, machine:permacomputing-collective-class) identify S3's energy model as an anti-pattern for LM transition. v0.2 gap surfaced: commodity enum lacks petabytes-stored / GET-request / data-egress-bytes / object-versions throughput values — all filed as [STUB-commodity-enum-gap].