Origins and Naming Conventions of AWS Service Names - Why S3 Has Three S's
Dig into the origins of major service names like S3, EC2, Lambda, and Aurora, exploring the hidden patterns in AWS naming conventions, naming missteps, and the history of rebranding.
The Golden Age of Acronyms - Naming Patterns of Early Services
AWS's early services were named with acronyms that succinctly described their function. S3 (Simple Storage Service) gets its name from the three S's in "Simple," "Storage," and "Service." EC2 (Elastic Compute Cloud) is similarly an abbreviation of its initials. SQS (Simple Queue Service), SNS (Simple Notification Service), SES (Simple Email Service) - the "Simple XX Service" pattern was heavily used in the early days. This "Simple" prefix reflects AWS's design philosophy. In 2006, building a message queue or email delivery infrastructure in-house required months of middleware selection, server procurement, and operational setup. AWS expressed making this available through a single API as "Simple." That said, SQS's specifications are far from simple, featuring advanced capabilities like visibility timeout, dead-letter queues, and FIFO queues. "Simple" refers to the ease of getting started, not the simplicity of features.
Names Borrowed from Mythology, Astronomy, and Natural Phenomena
As the number of services grew, AWS moved away from acronyms toward more memorable proper nouns. Aurora is named after the Roman goddess of dawn. While maintaining compatibility with MySQL and PostgreSQL, it symbolizes a "new dawn" that transcends the performance limits of traditional databases. Neptune is the Roman god of the sea, evoking the image of swimming through a "sea of relationships" in a graph database. Lambda derives from lambda calculus. Devised by Alonzo Church in the 1930s, this computational model that treats functions as first-class objects directly connects to the serverless paradigm of "deploying and executing functions." Kinesis comes from the Greek word for "movement" (kinesis), representing the flow of real-time data. Glacier refers to the ice formation. It likens the nature of archive storage - preserving data at low cost for extended periods - to how glaciers preserve matter over thousands of years. The fact that retrieval takes time makes the glacier metaphor particularly apt.
Naming Collisions and the History of Rebranding
When you keep naming over 200 services, name collisions and confusion become inevitable. AWS's history includes several notable rebrandings. Amazon Elasticsearch Service was renamed to Amazon OpenSearch Service in 2021. A trademark dispute with Elastic was the backdrop - AWS forked Elasticsearch to launch the OpenSearch project and changed the service name accordingly. AWS CodeStar was discontinued in 2023, with some functionality consolidated into CodeCatalyst. CodeCommit also stopped accepting new accounts in 2024, effectively heading toward deprecation. Amazon Wisdom was renamed to Amazon Q in Connect, consolidated under Amazon's generative AI brand "Q." Similarly, CodeWhisperer became Amazon Q Developer, and some Lex functionality was integrated into Amazon Q in Connect, with consolidation under the "Q" brand accelerating through 2023-2024. This consolidation also addresses the problem of too many service names causing customer confusion.
Implicit Rules Hidden in Naming Conventions
AWS service names follow several implicit rules that are not officially documented. First, the distinction between "Amazon" and "AWS." Generally, end-user-facing services (Amazon S3, Amazon DynamoDB, Amazon Bedrock) carry "Amazon," while infrastructure and developer-facing services (AWS Lambda, AWS CloudFormation, AWS IAM) carry "AWS." However, this distinction isn't strict - Amazon CloudWatch uses "Amazon" despite being developer-oriented. Second, there's a trend in service name length. Early services had short names (S3, EC2, SQS), but as the namespace filled up, names have tended to grow longer. Descriptive names like AWS Application Migration Service and Amazon Managed Streaming for Apache Kafka have become more common. Third, naming of acquired services. CloudEndure was renamed to AWS Application Migration Service, and Wickr became AWS Wickr. Whether to retain the acquired brand or consolidate under the AWS brand varies based on recognition and strategic judgment.
Reading AWS Strategy Through Service Names
Tracing naming patterns chronologically reveals the evolution of AWS's strategy. The early period of 2006-2012 featured the "Simple XX Service" pattern, a stage of providing basic cloud functionality. From 2012-2018, memorable names borrowed from mythology and natural phenomena increased, a period when AWS established its brand identity. From 2018-2022, the "Amazon Managed XX" pattern surged. Managed Blockchain, Managed Grafana, Managed Streaming for Apache Kafka - reflecting the strategy of offering existing OSS and third-party technologies as managed services. From 2023 onward, consolidation under the "Amazon Q" brand has been prominent. Q Developer, Q Business, Q in Connect - the move to aggregate generative AI capabilities under the "Q" umbrella embodies AWS's strategy of permeating generative AI across all services at the naming level. Service names are not mere labels but mirrors reflecting AWS's strategic priorities of each era. To systematically learn about AWS's history and strategy, specialized books (Amazon) can be helpful.