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.
| Abbreviation | Full name | How the abbreviation is built |
|---|---|---|
| S3 | Simple Storage Service | Simple, Storage and Service each start with S, so three S's become S3 |
| EC2 | Elastic Compute Cloud | The initials are E, C and C; two C's in a row become EC2 |
| SQS | Simple Queue Service | The three initials are simply lined up, with no digit involved |
| SNS | Simple Notification Service | The same "Simple something Service" pattern |
| SES | Simple Email Service | The same "Simple something Service" pattern |
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
If you keep naming services up to the scale that AWS itself describes as "over 200" (as of August 2026), name collisions and confusion become inevitable. AWS's history includes several notable rebrandings. Amazon Elasticsearch Service was renamed Amazon OpenSearch Service in September 2021. The backdrop was a license change by Elastic. After Elasticsearch and Kibana moved away from the Apache 2.0 license, AWS launched the OpenSearch project as a fork that continues development under Apache 2.0, and aligned the service name once the service had completed its support for OpenSearch. AWS CodeStar ended console access and the creation of new projects as of July 31, 2024, and Amazon CodeCatalyst was pointed to as its successor. CodeCatalyst itself, however, stopped accepting new customers as of November 7, 2025, a turnover in which the designated successor in turn closed its doors. CodeCommit also stopped accepting new accounts in 2024, only to take an unusual turn: in response to customer demand, it returned to general availability in November 2025. Amazon Connect Wisdom became Amazon Q in Connect as an evolved version that incorporates large language models, consolidated under Amazon's generative AI brand "Q." Similarly, CodeWhisperer was renamed Amazon Q Developer, and consolidation under the "Q" brand progressed from 2023 into 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. Wickr kept the acquired company's name almost as is and became AWS Wickr, whereas CloudEndure Migration was not renamed; instead, the path taken was a migration to its successor service, AWS Application Migration Service (MGN). Whether to retain the acquired brand or consolidate under the AWS brand varies based on recognition and strategic judgment.
- First, when it is Amazon and when it is AWSServices aimed at end users (Amazon S3, Amazon DynamoDB, Amazon Bedrock) carry "Amazon", while infrastructure and developer services (AWS Lambda, AWS CloudFormation, AWS IAM) carry "AWS". The line is not strict: Amazon CloudWatch is a developer service that still gets "Amazon".
- Second, names keep getting longerEarly names were short - S3, EC2, SQS - but as the namespace filled up they grew. Descriptive names such as AWS Application Migration Service and Amazon Managed Streaming for Apache Kafka are now the norm.
- Third, how acquisitions are renamedWickr kept its name and became AWS Wickr, while CloudEndure Migration was succeeded by AWS Application Migration Service (MGN) rather than renamed. Whether the acquired brand survives or is folded into the AWS brand depends on how well known it is and on strategy.
Reading AWS Strategy Through Service Names
Tracing naming patterns chronologically reveals the evolution of AWS's strategy. The periodization below is not something AWS has presented officially; it is this site's own arrangement of trends in service names. In the early period, the "Simple XX Service" pattern was central, a stage of providing basic cloud functionality. Next, memorable names borrowed from mythology and natural phenomena increased, as AWS established its brand identity. After that, the "Amazon Managed XX" pattern became prominent. 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 into 2024, consolidation under the "Amazon Q" brand stood out. Q Developer, Q Business, Q in Connect - the move to aggregate generative AI capabilities under the "Q" umbrella embodied AWS's strategy of permeating generative AI across all services at the naming level. This consolidation, however, has not proceeded in a straight line. Amazon Q Business, in an announcement in June 2026, ended availability to new customers as of July 30 of the same year (as of August 2026). Because brand consolidation and the pruning of individual services proceed at the same time, it is also necessary not to over-read naming trends as a statement of future direction. Service names are not mere labels but mirrors reflecting AWS's strategic priorities of each era.
References (Official AWS Resources)
The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.
If this page and the official documentation disagree, treat the official documentation as authoritative.