AWS Retired Services History and Timeline - Discontinued, Sunset, and Closed-to-New-Customer Services
First Published:
Last Updated:
The aim is accuracy and usefulness for people doing real migration work, not commentary. There is no "graveyard" framing here and no speculation about why a service did or did not succeed. Where AWS stated a reason, it is described only within the bounds of the official wording; where AWS did not, none is invented.
This is part of the series that began with the "AWS History and Timeline - Almost All AWS Services List, Announcements, General Availability(GA)", where I extract features from the history and timeline of AWS services. It is the deliberate counterpart to that overview: where the overview records when services launched, this article records when they were wound down. To keep the record honest, I summarize the criteria and the current lifecycle picture as a Current Overview of AWS Service Retirements.
This article focuses on service-level retirements, closures, and sunsets, rather than individual feature deprecations or SDK and runtime end-of-life. It is written for engineers who need to answer a concrete question — "was this service retired, and if so, when, and what do I move to?" — in a single fetch, with the official source next to every date.
Background and Method of Creating the AWS Retired Services Timeline
The reason for creating this timeline is that AWS does not maintain a single, permanent, human-readable history of everything it has retired. Product pages for discontinued services are frequently removed or redirected, announcements are sometimes made only through a blog update banner or a customer email, and community lists tend to blur important distinctions. This article organizes that scattered record in one place, and it applies a deliberately strict method so that each entry can be trusted.Three distinctions run through the whole article, because conflating them is the most common error in "discontinued services" lists.
- What state a service is in. Each row is labeled as one of three: fully discontinued (the service is shut down), closed to new customers (existing customers continue to use it), or sunset (a migration window is open and a firm end date is in the future). AWS CodeCommit, whose closure was later reversed, is the one exception and is labeled by its current state.
- Which date is which. The announcement date, the new-customer-close date, and the end-of-service date are three different things, and they are distinguished within each row.
- What counts as a retirement. A rename is not a retirement. For example, AWS CodeStar Connections was renamed AWS CodeConnections, and Amazon CodeWhisperer became part of Amazon Q Developer; those are covered in other articles rather than listed here.
- Service-level only. Individual feature deprecations and SDK/runtime end-of-life are out of scope. EC2-Classic is included as an exception because it is a platform-level retirement with service-level impact.
- Official primary source per row. Every entry links to an AWS-owned page — a What's New post, an AWS blog notice, a documentation "end of support" or "availability change" page, or SDK/CLI reference text. Where a retired service's own page has been removed, the surviving official notice is used and the situation is flagged.
- Integrity over completeness. Where AWS never published an official notice, the entry is either recorded with an explicit lower-certainty flag or left out entirely (see the exclusions below).
- What's New with AWS?
- AWS News Blog
- AWS Product Lifecycle - AWS General Reference
- Per-service documentation "end of support" and "availability change" pages
- Amazon SimpleDB. Press reports in July 2024 listed SimpleDB among the services closed to new customers, but no official AWS page carries a closure notice for it, and its documentation was still receiving updates in 2026. Because there is no primary source for a retirement, it is not recorded here as retired.
- AWS OpsWorks, AWS RoboMaker, and Amazon Lumberyard. All three were wound down before AWS introduced its consolidated lifecycle announcement posts, and the pages that stated their exact retirement dates have since been removed (the former RoboMaker and Lumberyard product URLs now redirect to generic AWS pages). Surviving official material confirms the outcomes — AWS Cloud Operations Blog posts walk through migrating AWS OpsWorks Stacks to AWS Systems Manager and off-boarding from OpsWorks Stacks, current SDK documentation records that OpsWorks reached end of life and marks RoboMaker APIs as no longer supported, and Lumberyard's engine continued outside AWS as the community-governed Open 3D Engine (O3DE) under the Linux Foundation from July 2021 — but because no surviving AWS-owned page states the retirement dates themselves, these three are acknowledged here rather than given timeline rows whose dates could not be verified against a primary source.
- Amazon Comprehend Medical and Amazon CodeGuru Profiler. Both were still active as of 2026 and are sometimes confused with retired relatives (Amazon Comprehend features and Amazon CodeGuru Security / Reviewer). They are not retirements and are not listed.
Please note that this timeline records service-level retirements, closures, and sunsets that are backed by an official AWS source, and is not an exhaustive list of every feature AWS has ever deprecated.
AWS Retired Services Timeline (Retirements Announced from November 27, 2018)
Here is the timeline. Rows are ordered by the date each retirement or closure was announced or, where AWS published no separate announcement, the date it took effect. The heaviest activity falls in the second half of 2024 and across 2025 and 2026, after AWS began systematically reviewing its portfolio.2018 | 2021 | 2022 | 2024 | 2025 | 2026
* The table can be sorted by clicking on the column names.| Date | Summary |
|---|---|
| 2018-11-27 | AWS folds AWS Mobile Hub into AWS Amplify. AWS Mobile Hub (launched in beta on 2015-10-08) provided a console to configure and manage mobile app backends. On 2018-11-27 AWS announced that its functionality had become part of AWS Amplify and offered a tool to migrate existing Mobile Hub projects; the Mobile Hub console and documentation were later removed. Status: discontinued (integrated into a successor). Migration target: AWS Amplify. [Source] |
| 2021-07-28 | AWS announces the retirement of EC2-Classic networking. EC2-Classic was the original flat-network platform introduced when Amazon EC2 launched in beta on 2006-08-24. On 2021-07-28 AWS announced a phased retirement; the platform was scheduled to retire on 2022-08-15, and AWS confirmed on 2023-08-23 that no instances were left running with EC2-Classic networking. This is a platform-level retirement within Amazon EC2 rather than a standalone service, included here for its significance. Status: fully discontinued. Migration target: Amazon VPC. [Source] |
| 2022-05-18 | Amazon Sumerian closes to new customers, ahead of its shutdown. Amazon Sumerian (announced in preview on 2017-11-26 and generally available on 2018-05-15) was a managed service for building 3D, AR, and VR scenes that run in a browser. An update dated 2022-05-18 on the launch announcement states that the service was no longer available to new customers and that existing customers' data would remain available until 2023-02-21. Status: fully discontinued. Migration guidance: rebuild scenes with the open-source Babylon.js library and host them using AWS Amplify. [Source] |
| 2022-11-09 | AWS transitions AWS IoT Things Graph to AWS IoT TwinMaker. AWS IoT Things Graph (preview on 2018-11-26, generally available on 2019-05-30) let developers connect devices and web services into IoT applications using a visual model. An update dated 2022-11-09 states that the service was transitioned to AWS IoT TwinMaker, and current AWS SDK and CLI references state that "the AWS IoT Things Graph service is discontinued." Status: fully discontinued. Migration target: AWS IoT TwinMaker. [Source] |
| 2024-01-31 | AWS DeepLens reaches end of support. AWS DeepLens (a deep-learning-enabled video camera for hands-on machine learning, available to purchase from 2018-06-14) was retired: a notice first posted as an April 2023 update states that, starting 2024-01-31, users can no longer access DeepLens through the console, manage devices, or open the projects they created. Status: fully discontinued. There is no direct successor; AWS points to Amazon SageMaker for model training. Note: the dedicated DeepLens product and FAQ pages have since been removed, so this entry is sourced from the surviving AWS Machine Learning Blog notice. [Source] |
| 2024-02-29 | The Amazon Honeycode beta service ends. Amazon Honeycode (launched in beta on 2020-06-24) let customers build web and mobile applications without writing code. Its launch announcement now carries an update stating that, after careful consideration, AWS ended the Honeycode beta, effective 2024-02-29. Status: fully discontinued (the service never left beta). There is no one-to-one successor; AWS pointed customers toward general no-code and low-code tooling. [Source] |
| 2024-04-17 | Press reports confirm that AWS has discontinued AWS Snowmobile. AWS Snowmobile (unveiled on 2016-11-30 as an exabyte-scale data-transfer service, using a 45-foot shipping container hauled by a truck) was discontinued around early 2024. Unusually, AWS did not publish a formal retirement announcement; the discontinuation was confirmed through press reporting citing an AWS statement (for example, on 2024-04-17), and the Snowmobile product page now redirects to AWS Snowball. Because there is no official AWS notice, this entry is recorded with lower certainty than the others. Status: fully discontinued. Alternatives: AWS Snowball / AWS Snowball Edge and AWS DataSync. [Launch source] |
| 2024-04-25 | Amazon WorkDocs closes to new customers. Amazon WorkDocs (originally launched as Amazon Zocalo in 2014 and renamed on 2015-01-28) was a managed content-collaboration and file service. On 2024-04-25 AWS stopped new customer sign-ups and account upgrades; existing customers were later notified that the service would end, reported as 2025-04-25. Status: fully discontinued. Migration target: export content to Amazon S3 using the WorkDocs migration tooling, or move to a partner service. Note: the new-customer-close is documented on AWS pages; the final end date is based on customer notifications. [Source] |
| 2024-07-18 | Amazon QLDB begins its wind-down toward end of support. Amazon Quantum Ledger Database (QLDB), a ledger database with a cryptographically verifiable transaction log, became generally available in 2019. AWS published migration guidance in July 2024 and set end of support for 2025-07-31, after which the service is no longer available. Status: fully discontinued. Migration target: Amazon Aurora PostgreSQL (QLDB's cryptographic immutability must be reconstructed at the application level). Note: QLDB's end-of-support documentation pages have since been removed; the general-availability announcement and the SLA page remain. [Source] |
| 2024-07-25 | AWS Cloud9 closes to new customers. AWS Cloud9 (a browser-based integrated development environment, launched on 2017-11-30) stopped accepting new customers on 2024-07-25, as one of a group of services closed the same day; existing customers can continue to use it. Status: closed to new customers. Migration guidance: AWS IDE Toolkits (for VS Code or JetBrains) or AWS CloudShell. [Source] |
| 2024-07-25 | AWS CodeCommit closes to new customers — a decision AWS later reversed. AWS CodeCommit (a managed, private Git repository service, generally available on 2015-07-09) stopped accepting new customers on 2024-07-25, with AWS recommending migration to external Git providers. On 2025-11-24 AWS reversed course and returned CodeCommit to full general availability, reopening new-customer sign-ups (the announcement blog is dated 2025-11-24, while CodeCommit's own document history records the change under 2025-11-25). CodeCommit is therefore a rare example of AWS walking back a retirement, and a useful illustration that "closed to new customers" is not the same as "ended." Status: reopened and active. [Source] [Reversal] |
| 2024-07-25 | Amazon CloudSearch closes to new customers. Amazon CloudSearch (a managed search service, announced on 2012-04-11) stopped accepting new customers on 2024-07-25; existing customers can continue to use it. Status: closed to new customers. Migration target: Amazon OpenSearch Service. [Source] |
| 2024-07-25 | AWS Data Pipeline closes to new customers. AWS Data Pipeline (a workflow-orchestration service for moving and transforming data, announced on 2012-12-20) stopped accepting new customers on 2024-07-25; existing customers can continue to use it. On the same day, Amazon S3 Select and S3 Glacier Select — query features rather than standalone services — were also closed to new customers. Status: closed to new customers. Migration targets: AWS Glue, AWS Step Functions, or Amazon MWAA. Note: an AWS document-history page lists this change as "25 July 2025," which appears to be a typo for 2024. [Source] |
| 2024-07-29 | Amazon Forecast closes to new customers. Amazon Forecast (a managed time-series forecasting service, generally available on 2019-08-22) closed to new customers, effective 2024-07-29 (an AWS document-history entry gives 2024-07-25 for the same change). Existing customers can continue to use it. Status: closed to new customers. Migration target: Amazon SageMaker Canvas. [Source] |
| 2024-07-31 | AWS CodeStar (classic) reaches end of support. AWS CodeStar (launched on 2017-04-19) provided unified project templates that wired together AWS CodeCommit, AWS CodePipeline, and AWS CodeBuild. AWS discontinued the ability to create and view CodeStar projects on 2024-07-31; the underlying resources it had provisioned continue to run independently. Status: fully discontinued. The migration target named at the time was Amazon CodeCatalyst, which itself later closed to new customers on 2025-11-07. Note: AWS removed the CodeStar product and documentation pages, so the exact date here is based on AWS customer notifications and is recorded with medium certainty; the separate AWS CodeStar Connections feature was renamed AWS CodeConnections and is not retired. [Launch source] |
| 2024-09-17 | AWS announces the end of support for AWS DeepComposer. AWS DeepComposer (a machine-learning-enabled music keyboard for learning generative AI, generally available on 2020-04-02) was retired: a notice published on 2024-09-17 states that support ended on 2025-09-17, after which the console, device management, and saved compositions are no longer accessible. Status: fully discontinued. There is no functional successor; AWS suggested PartyRock as a hands-on generative-AI learning alternative. Note: the DeepComposer product pages have been removed; this entry is sourced from the surviving AWS Machine Learning Blog notice. [Source] |
| 2024-09-24 | AWS App Mesh closes to new customers, with a scheduled end of support. AWS App Mesh (a service mesh for microservices, generally available on 2019-03-27) stopped onboarding new customers on 2024-09-24 and is scheduled to be discontinued on 2026-09-30; existing customers can use it until then. Status: sunset (scheduled end 2026-09-30). Migration targets: Amazon ECS Service Connect, or Amazon VPC Lattice for Amazon EKS workloads. [Source] |
| 2024-10-10 | Amazon Lookout for Vision closes to new customers, ahead of its shutdown. Amazon Lookout for Vision (a service that spots defects in images, generally available on 2021-02-24) closed to new customers on 2024-10-10, and support ended on 2025-10-31. Status: fully discontinued. Migration targets: Amazon SageMaker for custom models, or Amazon Bedrock for generative-AI-based inspection. [Source] |
| 2024-10-28 | Amazon FSx File Gateway closes to new customers. Amazon FSx File Gateway (a gateway that provided low-latency, on-premises access to Amazon FSx for Windows File Server, generally available on 2021-04-27) closed to new customers on 2024-10-28; existing customers can continue to use it. Status: closed to new customers. Migration guidance: access Amazon FSx for Windows File Server directly. [Source] |
| 2024-10-31 | Amazon Monitron closes to new customers. Amazon Monitron (an end-to-end equipment-monitoring system with its own sensors and gateway, launched on 2020-12-01) closed to new customers on 2024-10-31; existing customers can continue to use it. Status: closed to new customers. AWS pointed customers to the AWS Partner Network for alternative predictive-maintenance offerings. [Source] |
| 2025-01-08 | Amazon Aurora Serverless v1 stops new cluster creation, ahead of end of life. Aurora Serverless v1 (generally available for the MySQL-compatible edition on 2018-08-09) could no longer be created after 2025-01-08, and its end of life was set for 2025-03-31; clusters not migrated by then were converted to Aurora Serverless v2. Status: fully discontinued. Migration target: Amazon Aurora Serverless v2. [Source] |
| 2025-02-19 | AWS announces the end of the Amazon Chime communications application. Amazon Chime (an online meetings and messaging application, launched on 2017-02-13) stopped accepting new Team and Enterprise accounts on 2025-02-19, and support ended on 2026-02-20. Status: fully discontinued. Migration targets: AWS Wickr, or third-party communication services. Note: this does not affect the Amazon Chime SDK, a separate developer service for embedding voice, video, and messaging, which remains supported. [Source] |
| 2025-05-20 | Amazon Pinpoint closes to new customers, with a scheduled end of support. The Amazon Pinpoint engagement application (campaigns, journeys, segments, and analytics; the service launched in 2016 and reached general availability on 2017-01-12) stopped accepting new customers on 2025-05-20 and is scheduled to end support on 2026-10-30. Status: sunset (scheduled end 2026-10-30). Migration targets: Amazon Connect for customer engagement and Amazon SES for email. Note: Pinpoint's transactional messaging channel APIs (SMS, push, and similar) were rebranded as AWS End User Messaging and are not retired. [Source] |
| 2025-05-20 | AWS announces end of support for a wider May 2025 group of services. The same 2025-05-20 "AWS service changes" post that covered Amazon Pinpoint also announced end of support — each with its own end-of-support date and migration path — for AWS IQ, AWS IoT Analytics, AWS IoT Events, AWS SimSpace Weaver, AWS Panorama, Amazon Inspector Classic, Amazon Connect Voice ID, and AWS DMS Fleet Advisor. The post also closed Amazon Timestream for LiveAnalytics to new customers effective 2025-06-20, and recorded that AWS Private 5G and AWS DataSync Discovery had already reached their end-of-support dates. Several of these retirements have since completed; the product and documentation pages for AWS IoT Analytics and AWS IoT Events, for example, have already been removed. Status: sunset (per-service end dates), with several since fully discontinued. [Source] |
| 2025-10-07 | AWS Proton closes to new customers, with a scheduled end of support. AWS Proton (a service for provisioning and managing container and serverless deployments through platform templates, generally available on 2021-06-09) stopped accepting new customers on 2025-10-07 and is scheduled to end support on 2026-10-07. Status: sunset (scheduled end 2026-10-07). Migration targets: AWS CloudFormation Git sync, AWS CodePipeline with AWS CodeBuild, or partner solutions. [Source] |
| 2025-10-07 | Amazon Lookout for Equipment closes to new customers, with a scheduled end of support. Amazon Lookout for Equipment (a service that detects abnormal industrial-equipment behavior from sensor data, generally available on 2021-04-08) stopped accepting new customers on 2025-10-07 and is scheduled to be discontinued on 2026-10-07. Status: sunset (scheduled end 2026-10-07). Migration target: the anomaly-detection capability in AWS IoT SiteWise. [Source] |
| 2025-11-07 | AWS moves a group of services to Maintenance, closing them to new customers. Effective 2025-11-07, and announced on 2025-10-13 through the AWS Service Availability Updates process, the following services stopped accepting new customers while existing customers can continue to use them: Amazon Cloud Directory, Amazon CodeCatalyst, Amazon CodeGuru Reviewer, Amazon Fraud Detector, the standalone Amazon Glacier service (distinct from the Amazon S3 Glacier storage classes), Amazon S3 Object Lambda, AWS Application Discovery Service, AWS Mainframe Modernization, AWS Migration Hub, and AWS Snowball Edge (Compute Optimized and Storage Optimized). Status: closed to new customers (Maintenance). [Source] |
| 2025-11-07 | AWS places additional services into Sunset, with migration windows. In the same 2025-10-13 update, Amazon FinSpace and AWS IoT Greengrass v1 entered the Sunset stage, with AWS providing migration guidance ahead of their end-of-support dates. (Amazon Lookout for Equipment and AWS Proton, listed above, were part of the same update.) Status: sunset. [Source] |
| 2025-11-13 | Amazon Elastic Transcoder reaches end of support. Amazon Elastic Transcoder (a media-transcoding service, announced on 2013-01-28) was discontinued on 2025-11-13; after that date the console and its resources are no longer accessible. Status: fully discontinued. Migration target: AWS Elemental MediaConvert. [Source] |
| 2025-11-20 | Amazon CodeGuru Security reaches end of support. Amazon CodeGuru Security (a static application security testing service introduced in 2023) was discontinued on 2025-11-20. Status: fully discontinued. Migration targets: code reviews in Amazon Q Developer, or code scanning in Amazon Inspector. Note: the dedicated end-of-support page has been removed; the notice survives in the AWS CLI and SDK reference documentation. For clarity, Amazon CodeGuru Reviewer moved to Maintenance on 2025-11-07, while Amazon CodeGuru Profiler remains available. [Source] |
| 2025-12-15 | AWS DeepRacer as a service reaches end of support. AWS DeepRacer (a reinforcement-learning autonomous-racing service and 1/18th-scale car, introduced in November 2018) ended as a console service on 2025-12-15, and DeepRacer devices are no longer sold; the DeepRacer Student portal had already closed on 2025-09-15. Status: fully discontinued as a managed service. AWS published a self-hosted, open-source successor ("DeepRacer on AWS") that customers can deploy into their own accounts. [Source] |
| 2026-03-31 | AWS moves more services to Maintenance in its March 2026 Service Availability Updates. Announced on 2026-03-31, AWS App Runner, AWS Audit Manager, AWS CloudTrail Lake, and AWS IoT FleetWise move to the Maintenance stage: they stop accepting new customers on 2026-04-30 (2026-05-31 for AWS CloudTrail Lake), while existing customers can continue to use them. The same post also moved a set of individual features (for example, Amazon SNS Message Data Protection and several Amazon Comprehend and Amazon Rekognition features) to Maintenance; feature-level items are out of scope for this timeline. Status: closed to new customers (Maintenance). [Source] |
| 2026-03-31 | AWS places Amazon WorkMail and three other services into Sunset. In the same March 2026 update, Amazon RDS Custom for Oracle, Amazon WorkMail, Amazon WorkSpaces Thin Client, and AWS Service Management Connector entered the Sunset stage, with AWS publishing the end-of-support timeline and migration guidance on each service's own pages. Status: sunset. [Source] |
| 2026-06-30 | AWS moves Amazon Q Business, Amazon Kendra, and other services to Maintenance in its June 2026 update. Announced on 2026-06-30, Amazon Q Business, Amazon Kendra, Amazon Cognito Sync, and AWS Directory Service - Simple AD move to the Maintenance stage, closing to new customers on 2026-07-30, and the November 2023 generation of Amazon Bedrock Agents — renamed Amazon Bedrock Agents Classic — moves to Maintenance as well. In the same post, AWS Managed Services (AMS) Advanced, AWS re:Post Private, Amazon WorkSpaces - PCoIP, Amazon WorkSpaces - Pool, and Amazon SageMaker AI - Profiler enter Sunset; Amazon Chime SDK - Carrier Voice Focus and Amazon SageMaker AI - Ground Truth Plus reach end of support as of 2026-06-30; and a long list of feature-level items (including several Amazon SageMaker AI features) changes stage. Status: closed to new customers (Maintenance) for the named Maintenance services; sunset for the named Sunset group. [Source] |
Current Overview of AWS Service Retirements
The individual rows above are easier to use when placed against the process AWS now follows and grouped by status. This section explains how AWS retires a service today, then summarizes the services by state and points to where the excluded cases belong.How AWS Retires a Service Today
The 2024 closures drew criticism for how quietly they were communicated — several were first noticed through updated product pages and a social-media post rather than a formal announcement. In response, AWS introduced a dedicated AWS Product Lifecycle page in May 2025 and began publishing recurring "AWS Service Availability Updates." AWS now describes three lifecycle stages.- Maintenance — the service is closed to new customers and receives no new features, but existing customers are unaffected.
- Sunset — existing customers are asked to migrate within a defined window (typically about twelve months), and a firm end-of-support date is set.
- Full Shutdown — the final stage, after which the service is removed from the AWS portfolio.
Services That Have Been Fully Discontinued
These services are shut down (or, where a date is in the near future, on a fixed path to shutdown with clusters/projects already being migrated). Existing usage is no longer possible after the end date shown.| Service | Available | End of service | Successor / migration |
|---|---|---|---|
| AWS Mobile Hub | 2015–2018 | 2018-11-27 (into Amplify) | AWS Amplify |
| EC2-Classic (platform) | 2006–2023 | 2022-08-15 (completed 2023-08-23) | Amazon VPC |
| Amazon Sumerian | 2018–2023 | 2023-02-21 | Babylon.js + AWS Amplify |
| AWS IoT Things Graph | 2019–2022 | 2022-11-09 (transitioned) | AWS IoT TwinMaker |
| AWS DeepLens | 2018–2024 | 2024-01-31 | Amazon SageMaker (training) |
| Amazon Honeycode | 2020–2024 | 2024-02-29 | No-code / low-code alternatives |
| AWS Snowmobile | 2016–2024 | ~2024 (no official notice) | AWS Snowball / AWS DataSync |
| Amazon WorkDocs | 2014–2025 | ~2025-04-25 | Amazon S3 / partner |
| Amazon QLDB | 2019–2025 | 2025-07-31 | Amazon Aurora PostgreSQL |
| AWS CodeStar (classic) | 2017–2024 | 2024-07-31 | Amazon CodeCatalyst |
| AWS DeepComposer | 2020–2025 | 2025-09-17 | None (PartyRock as learning tool) |
| Amazon Lookout for Vision | 2021–2025 | 2025-10-31 | Amazon SageMaker / Amazon Bedrock |
| Amazon Aurora Serverless v1 | 2018–2025 | 2025-03-31 | Amazon Aurora Serverless v2 |
| Amazon Chime (application) | 2017–2026 | 2026-02-20 | AWS Wickr |
| Amazon Elastic Transcoder | 2013–2025 | 2025-11-13 | AWS Elemental MediaConvert |
| Amazon CodeGuru Security | 2023–2025 | 2025-11-20 | Amazon Q Developer / Amazon Inspector |
| AWS DeepRacer (service) | 2018–2025 | 2025-12-15 | DeepRacer on AWS (open source) |
Services Closed to New Customers or in Sunset
These services are still usable by existing customers. "Closed to new customers" (Maintenance) has no announced end date; "Sunset" has a firm, future end-of-support date.| Service | Closed to new customers | Scheduled end | Successor / migration |
|---|---|---|---|
| AWS Cloud9 | 2024-07-25 | — | AWS IDE Toolkits / AWS CloudShell |
| Amazon CloudSearch | 2024-07-25 | — | Amazon OpenSearch Service |
| AWS Data Pipeline | 2024-07-25 | — | AWS Glue / Step Functions / MWAA |
| Amazon Forecast | 2024-07-29 | — | Amazon SageMaker Canvas |
| Amazon FSx File Gateway | 2024-10-28 | — | Amazon FSx (direct access) |
| Amazon Monitron | 2024-10-31 | — | AWS Partner Network |
| AWS App Mesh | 2024-09-24 | 2026-09-30 | ECS Service Connect / VPC Lattice |
| Amazon Pinpoint (engagement) | 2025-05-20 | 2026-10-30 | Amazon Connect / Amazon SES |
| AWS Proton | 2025-10-07 | 2026-10-07 | CloudFormation Git sync / CodePipeline |
| Amazon Lookout for Equipment | 2025-10-07 | 2026-10-07 | AWS IoT SiteWise |
| May 2025 end-of-support group (AWS IQ, AWS IoT Analytics, AWS IoT Events, AWS SimSpace Weaver, AWS Panorama, Amazon Inspector Classic, Amazon Connect Voice ID, AWS DMS Fleet Advisor) | 2025-05-20 (announced) | Per-service end dates | Per service migration guide |
| Amazon Timestream for LiveAnalytics | 2025-06-20 | — | Per service migration guide |
| Nov 2025 Maintenance wave | 2025-11-07 | — | Per service (see the timeline row) |
| Amazon FinSpace; AWS IoT Greengrass v1 | 2025-11-07 | Sunset window | Per service migration guide |
| Mar 2026 Maintenance wave (AWS App Runner, AWS Audit Manager, AWS CloudTrail Lake, AWS IoT FleetWise) | 2026-04-30 (CloudTrail Lake: 2026-05-31) | — | Per service (see the timeline row) |
| Mar 2026 Sunset group (Amazon WorkMail, Amazon RDS Custom for Oracle, Amazon WorkSpaces Thin Client, AWS Service Management Connector) | 2026-03-31 (announced) | Sunset window | Per service migration guide |
| Jun 2026 Maintenance wave (Amazon Q Business, Amazon Kendra, Amazon Cognito Sync, AWS Directory Service - Simple AD, Amazon Bedrock Agents Classic) | 2026-07-30 | — | Per service (see the timeline row) |
| Jun 2026 Sunset group (AWS Managed Services Advanced, AWS re:Post Private, Amazon WorkSpaces - PCoIP, Amazon WorkSpaces - Pool, Amazon SageMaker AI - Profiler) | 2026-06-30 (announced) | Sunset window | Per service migration guide |
What This Timeline Deliberately Excludes
- Renames, not retirements. AWS CodeStar Connections was renamed AWS CodeConnections (2024-03-29); Amazon Pinpoint's channel APIs became AWS End User Messaging; Amazon CodeWhisperer became part of Amazon Q Developer; and Amazon Elasticsearch Service was renamed Amazon OpenSearch Service (2021-09-08). These are covered in the relevant history articles, such as the Amazon Q history and timeline and the Amazon OpenSearch Service history and timeline, and are excluded here because the capability continues under a new name.
- Feature and runtime end-of-life. Deprecations of individual features, API versions, and language runtimes are out of scope for a service-level record. Those are tracked separately in the AWS End-of-Support and EOL Reference.
- Still-active services that were misreported. Amazon SimpleDB has no official closure notice and was still receiving documentation updates in 2026; Amazon Comprehend Medical and Amazon CodeGuru Profiler remain active. None of these are retirements.
Frequently Asked Questions about AWS Retired Services History
Which AWS services have been discontinued or closed to new customers?
Between 2024 and 2026, AWS discontinued or wound down a range of services. Fully discontinued examples include Amazon Sumerian, Amazon Honeycode, AWS DeepLens, AWS DeepComposer, AWS DeepRacer (as a managed service), Amazon Elastic Transcoder, Amazon QLDB, Amazon Aurora Serverless v1, the Amazon Chime application, and AWS CodeStar. Services closed to new customers (with existing customers continuing) include AWS Cloud9, Amazon CloudSearch, AWS Data Pipeline, and Amazon Forecast, along with recurring Maintenance and Sunset waves announced in October 2025, March 2026, and June 2026 (the June 2026 wave reaching Amazon Q Business and Amazon Kendra). The timeline above lists each with its official source and exact dates.What happens when AWS retires a service?
Since May 2025, AWS follows a published lifecycle with three stages: Maintenance (closed to new customers, no new features, existing customers unaffected), Sunset (a defined migration window and a firm end-of-support date), and Full Shutdown (removal from the portfolio). AWS notifies affected accounts directly, publishes migration guidance, and lists changes in recurring AWS Service Availability Updates. Existing data and resources typically remain available until the stated end date, after which the console and APIs for that service are no longer accessible.What is the difference between closing to new customers and ending a service?
Closing to new customers means the service stops onboarding new sign-ups, but existing customers keep using it, often with no announced end date. Ending a service (end of support or full shutdown) means the service becomes unavailable to everyone after a specific date. The two are frequently confused. AWS CodeCommit is the clearest illustration: it was closed to new customers on 2024-07-25, but it was never shut down, and on 2025-11-24 AWS reopened it to new customers and returned it to full general availability.Where does AWS officially list service lifecycle changes?
AWS publishes a Product Lifecycle page in the AWS General Reference that defines the Maintenance, Sunset, and Full Shutdown stages, and it posts recurring "AWS Service Availability Updates" under What's New that name the specific services in each wave. Individual services also carry an "availability change" or "end of support" notice in their own documentation, though these pages are sometimes removed after a service is fully shut down.Has AWS ever reversed a decision to retire a service?
Yes. AWS CodeCommit was closed to new customers on 2024-07-25 as part of a group of services, and AWS initially recommended migrating to external Git providers. After customer feedback, AWS reversed the decision and returned CodeCommit to full general availability on 2025-11-24, reopening new-customer sign-ups. This is a rare case, and it is a useful reminder that "closed to new customers" does not automatically mean a service will disappear.Summary
AWS spent its first fifteen years rarely retiring anything, and then, beginning in 2024, started systematically reviewing its portfolio. This article records that shift as a single, respectful, source-backed timeline: services that were fully discontinued (from Amazon Sumerian and Amazon Honeycode to Amazon Elastic Transcoder and AWS DeepRacer), services closed to new customers while existing customers continue (such as AWS Cloud9, Amazon CloudSearch, and AWS Data Pipeline), and services in a scheduled sunset (such as AWS App Mesh, AWS Proton, and the Amazon Pinpoint engagement application), through to the recurring Service Availability Updates waves that carried the review into 2026 and reached services such as AWS App Runner, AWS CloudTrail Lake, Amazon Kendra, and Amazon Q Business. Throughout, three distinctions were kept explicit — the status class, the specific date type, and whether a change was a retirement at all rather than a rename.The most useful lesson is the one AWS CodeCommit teaches: closing to new customers is not the same as shutting down, and a decision can even be reversed. Since May 2025, AWS has made this easier to track through its published Product Lifecycle stages and recurring availability updates.
For the broader context of when these services launched, see the main "AWS History and Timeline - Almost All AWS Services List, Announcements, General Availability(GA)". For the naming and consolidation history that this article deliberately delegates, see the "AWS History and Timeline regarding Amazon Q". For the EC2-Classic to Amazon VPC transition, see the "AWS History and Timeline regarding Amazon EC2", and for the launches that many of these services first received on stage, see the "AWS re:Invent History and Timeline".
This timeline will be updated as AWS continues to evolve its service portfolio.
References:
AWS Product Lifecycle - AWS General Reference
Introducing the AWS Product Lifecycle page and AWS service availability updates - AWS News Blog
AWS Service Availability Updates - What's New with AWS
AWS CodeCommit returns to General Availability - AWS DevOps Blog
What's New with AWS?
AWS History and Timeline - Almost All AWS Services List, Announcements, General Availability(GA)
AWS History and Timeline regarding Amazon Q
AWS History and Timeline regarding Amazon EC2
AWS re:Invent History and Timeline
References:
Tech Blog with curated related content
Written by Hidekazu Konishi