AWS sets service sunset dates and new-customer restrictions

AWS announced lifecycle changes on September 29, 2026, covering two offerings moving to maintenance, four entering sunset and Amazon Mechanical Turk reaching end of support. The AWS availability notice distinguishes restrictions on new customers from deadlines when operations and support end.

Maintenance: existing customers retain access

Starting October 29, 2026, Amazon Chime SDK SIP Media Application and Amazon WorkSpaces Secure Browser will no longer be accessible to new customers. Existing customers can continue using them, and AWS says it will keep operating and supporting both.

The October date is a new-customer cutoff, not a shutdown deadline for existing customers.

Sunset: deadlines for four offerings

AWS’s notice describes sunset as a scheduled end to operations and support. It lists these end-of-support milestones:

• AWS Infrastructure Composer: December 7, 2026, specifically for the standalone console.
• Amazon Managed Blockchain: September 29, 2027.
• AWS Backint Agent for SAP ASE: September 29, 2027.
• Amazon DevOps Guru: September 30, 2027.

AWS directs affected customers to the relevant service pages and documentation to understand the timelines and begin planning migration.

End of support: Mechanical Turk unavailable

Amazon Mechanical Turk reached end of support and is no longer available as of September 29, 2026, according to AWS.

Engineering impact: separate access restrictions from retirement

Record the exact service or feature, lifecycle status and applicable date for each affected dependency. For maintenance entries, check new-customer eligibility before planning adoption rather than treating existing usage as unsupported. For sunset entries, work backward from the deadline to build a migration schedule. For Mechanical Turk, check immediately for dependencies on the unavailable service.

Assess Infrastructure Composer standalone-console usage separately: the listed deadline should not be generalized to the entire product. AWS says it has prepared migration guides, but this announcement does not name specific replacement services.