Why AWS Is Dropping 9 Services – What It Means for Developers

Background

In June 2024 AWS appointed a new CEO, Matt Garman, who began a portfolio‑wide review aimed at eliminating low‑usage services and reducing operational overhead as generative‑AI becomes a core growth area.

Services announced for deprecation

Amazon QLDB (Quantum Ledger Database) – a multi‑region, immutable ledger service for high‑trust use cases such as financial transactions.

S3 Select – an SQL‑based query engine that filters data stored in Amazon S3 to reduce data transfer.

Amazon CloudSearch – a managed search service for web and application indexing.

AWS Cloud9 – a cloud‑based integrated development environment (IDE) that runs in a browser.

Amazon SimpleDB – a schemaless NoSQL data store with automatic indexing.

Amazon Forecast – a fully managed time‑series forecasting service that applies statistical and machine‑learning algorithms.

AWS Data Pipeline – a workflow service for moving and processing data between AWS services and on‑premises resources.

AWS CodeCommit – a fully managed Git repository service.

AWS Snowmobile – a 45‑foot shipping container that can transport up to 100 PB of data to AWS.

Impact on existing customers

Deprecated services will remain operational for current users, but no new features or enhancements will be added. Customers are advised to:

Continue using the legacy service while planning migration.

Migrate to alternative AWS offerings (e.g., OpenSearch for CloudSearch, Amazon S3 Select alternatives, or other forecasting tools).

Adopt third‑party solutions such as GitHub or GitLab for source‑code hosting.

For tightly integrated services—most notably CodeCommit, which is heavily used by AWS Amplify—customers should assess dependency maps and schedule migration well before any future shutdown.

Strategic rationale

The deprecation aligns with AWS’s “two‑pizza team” culture, which encourages small, autonomous teams to focus on high‑impact products. Consolidating overlapping services reduces maintenance costs, frees engineering resources for generative‑AI‑driven services, and addresses slowing revenue growth despite $100 B+ annual sales.

Key considerations for migration

Identify workloads that rely on the deprecated service and document integration points.

Evaluate AWS‑native replacements for functional parity and cost.

Plan data export or repository cloning (e.g., git clone --mirror for CodeCommit) before the end‑of‑support date.

Test the target solution in a staging environment to verify performance and security requirements.