# AWS Announces Major Service Lifecycle Changes
AWS recently [announced](https://aws.amazon.com/about-aws/whats-new/2025/10/aws-service-availability/) **significant lifecycle changes** for over 20 services and features, classifying them into three categories: **Maintenance**, **Sunset**, and **End of Support**.
---
## Background: Previous Retirements
The [first wave of changes](https://www.infoq.com/news/2024/08/aws-discontinue-services/) occurred in **July 2024**, ending access for new customers to long-standing managed services like [AWS CodeCommit](https://aws.amazon.com/codecommit/).
This was followed in **October 2024** by the retirement of services such as:
- [AWS App Mesh](https://docs.aws.amazon.com/app-mesh/latest/userguide/what-is-app-mesh.html)
- [Amazon FSx File Gateway](https://docs.aws.amazon.com/filegateway/latest/filefsxw/what-is-file-fsxw.html)
---
## The Second Wave of Portfolio Review
AWS is again conducting a major review of its product portfolio, with availability changes across three lifecycle stages.
### Maintenance Phase
Services entering **Maintenance** will:
- **Be inaccessible to new customers starting November 7, 2025**
- Remain available to **existing customers** temporarily for migration and replacement planning
This is part of AWS’s strategy to retire **low-usage** offerings and consolidate capability into core products.
---
## Why It Matters
These transitions emphasize the need for:
- **Flexible architectures**
- **Contingency planning** for cloud-managed service deprecations
- **Workflow diversification** for creators and businesses
---
## Example: Using Modern Alternatives
Tools like [AiToEarn官网](https://aitoearn.ai/) help creators and teams adapt through:
- **AI content generation**
- **Cross-platform publishing** (Douyin, Kwai, WeChat, Bilibili, Rednote, Facebook, Instagram, LinkedIn, Threads, YouTube, Pinterest, X)
- **Analytics and AI model rankings** ([AI模型排名](https://rank.aitoearn.ai))
Open-source code: [AiToEarn开源地址](https://github.com/yikart/AiToEarn)
---
## Affected AWS Service Categories
### 1. Core Data and Storage
- **Amazon Glacier** ([details](https://docs.aws.amazon.com/amazonglacier/latest/dev/introduction.html))
- Moving away from its **standalone vault-based API** in favor of S3 Glacier classes
- APIs consolidated, removing “profoundly annoying” older interfaces ([Corey Quinn commentary](https://www.lastweekinaws.com/blog/aws-deprecates-two-dozen-services-most-of-which-youve-never-heard-of/))
- **Amazon S3 Object Lambda**
- Retired; capabilities still achievable with **standard Lambda on S3**
---
### 2. Developer and Specialized Tools
- [Amazon CodeCatalyst](https://docs.aws.amazon.com/codecatalyst/latest/userguide/migration.html) → Maintenance mode due to limited adoption
- [Amazon Cloud Directory](https://docs.aws.amazon.com/clouddirectory/latest/developerguide/cloud-directory-availability-change.html) → Retirement
- [Amazon CodeGuru Reviewer](https://www.infoq.com/news/2021/07/codeguru-github-actions/) → Already integrated into GitHub Actions
- [Amazon Fraud Detector](https://www.infoq.com/news/2020/08/amazon-fraud-detector-ga/) → Retirement
- [.NET Modernization Tools](https://docs.aws.amazon.com/portingassistant/latest/userguide/what-is-porting-assistant.html) → Retirement
---
### 3. Management, Mainframe, and Edge
- **Integrations & Replacements**
- [AWS Mainframe Modernization Service](https://www.infoq.com/news/2022/06/aws-mainframe-modernization-ga/) → Features moving into [AWS Transform](https://www.infoq.com/news/2025/05/aws-transform-ai-legacy-migrate/)
- [AWS Systems Manager – Change Manager](https://www.docs.aws.amazon.com/systems-manager/latest/userguide/change-manager-availability-change.html) → Deprecation
- [Incident Manager](https://www.infoq.com/news/2021/05/amazon-incident-manager/) → Deprecation
---
## Sunset Phase – Act Now
**Migration planning should start immediately** for these services:
- [Amazon FinSpace](https://docs.aws.amazon.com/finspace/latest/userguide/amazon-finspace-end-of-support.html) (2021 launch)
- [Amazon Lookout for Equipment](https://aws.amazon.com/blogs/machine-learning/preserve-access-and-explore-alternatives-for-amazon-lookout-for-equipment/)
- [AWS IoT Greengrass v1](https://docs.aws.amazon.com/greengrass/v2/developerguide/migrate-from-v1.html) → Upgrade to v2 recommended
- [AWS Proton](https://www.infoq.com/news/2021/06/aws-proton-container-ga/)
---
## End of Support
- **[AWS Mainframe Modernization App Testing](https://aws.amazon.com/about-aws/whats-new/2024/06/aws-mainframe-modernization-application-testing-generally-available/)**
- GA: 2024
- Ended: **October 7, 2025**
---
## Strategic Perspective
- [Corey Quinn](https://www.lastweekinaws.com/blog/aws-deprecates-two-dozen-services-most-of-which-youve-never-heard-of/): This is AWS “clearing out the rotten fruit” from overambitious service launches
- [Benjamen Pyle’s reminder](https://www.linkedin.com/posts/donkersgoed_aws-service-availability-updates-activity-7383567696849846272-o8yf/):
> Don’t build something integral to your product on a fringe service.
---
## Practical Advice for Architects
- Avoid new dependencies on **Snowball Edge Compute Optimized** and **Storage Optimized** ([details](https://docs.aws.amazon.com/snowball/latest/developer-guide/snowball-edge-availability-change.html))
- Leverage AWS [migration assistance teams](https://aws.amazon.com/products/lifecycle/) and guides
- Build on **widely adopted**, sustained services
---
## Parallel Lessons for Content Creators
For those producing content across multiple ecosystems:
- Minimize reliance on niche platforms
- Use integrated solutions like [AiToEarn官网](https://aitoearn.ai/) for:
- **AI-powered content generation**
- **Cross-platform publishing & analytics**
- **Model ranking integration**
As AWS is streamlining its **service portfolio**, creators can streamline their **distribution workflows**.
---
**Summary:**
AWS is moving dozens of services into **Maintenance**, **Sunset**, or **End of Support** stages in 2025–2026. Organizations and creators must act now to adopt widely-supported solutions and ensure workflows remain agile in an environment of constant change.
