A Complete History of AWS: Launch Dates from SQS to 2026

When Did Every AWS Service Launch?

Senior Developer Advocate Brooke Jamieson compiled a comprehensive timeline of over 250 AWS service launches using the AWS MCP Server. The data reveals that Amazon SQS was the first service, debuting in preview on November 3, 2004, more than a year before S3 existed. This technical index tracks the platform’s expansion from basic queuing to advanced agentic AI tools launched in 2026.

Why This Matters

Understanding the chronological release of AWS services provides critical context for architectural decisions, distinguishing between legacy systems like Simple Workflow Service (SWF) and modern successors like Step Functions. The rapid acceleration from two services in 2006 to over 30 new services in 2017 highlights the shift from basic compute and storage to specialized AI, serverless, and industry-specific tools. This historical perspective allows engineers to navigate the technical reality of AWS’s vast ecosystem, where the line between a new service and a major feature often blurs. By tracking General Availability (GA) dates against preview phases, developers can better assess the stability and production-readiness of tools like Amazon Aurora DSQL or Bedrock AgentCore, avoiding the common mistake of building critical infrastructure on experimental features.

Key Insights

• Amazon SQS launched in preview on November 3, 2004, making it the oldest AWS service according to original launch announcements.
• Serverless orchestration evolved from Simple Workflow Service (2012) to AWS Step Functions (2016) for visual workflow management.
• The AWS MCP Server is used by engineers in tools like Claude Code and Cursor to access authenticated AWS documentation and APIs via the Model Context Protocol.
• Infrastructure as Code transitioned from JSON/YAML templates in CloudFormation (2011) to imperative logic in the AWS CDK (2019).
• Generative AI agents are now deployed using Amazon Bedrock AgentCore (2025), which provides the necessary runtime, memory, and identity components.

Practical Applications

• Modernizing Legacy Workloads: Organizations use AWS Transform (2025) to automate the migration of .NET and VMware environments. Pitfall: Relying on automated modernization without manual code review can lead to unoptimized cloud-native performance.
• Scaling Real-time Media: Media companies utilize AWS Elemental Inference (2026) to automatically generate vertical content for mobile platforms during live broadcasts. Pitfall: High-speed data ingest without using S3 Tables (2024) can lead to performance bottlenecks in large-scale analytics pipelines.
• Implementing Zero-Trust Access: Remote teams deploy AWS Verified Access (2023) to provide secure corporate application access without a traditional VPN. Pitfall: Misconfiguring IAM Identity Center (2017) can result in overly permissive access across a multi-account organization.

References:

• https://dev.to/aws/when-did-every-aws-service-launch-3kc7