AWS ends Mechanical Turk and sets sunset dates for DevOps Guru, Managed Blockchain and three more services

AWS ends Mechanical Turk and sets sunset dates for DevOps Guru, Managed Blockchain and three more services

30 September 2026 —

Not yet independently verified. The maintenance and sunset dates rest on AWS’s own announcement; the independent report found covers the Mechanical Turk shutdown only. We will update this when the other dates are reported independently, and remove this note. We will update this when it can be confirmed, and remove this note.

On 29 September 2026 Amazon Web Services published one of its periodic service availability updates. It does three things: it switches off one service that day, it puts two services into maintenance, and it gives end-of-support dates for four more. Anyone with workloads or procurement plans on these services now has fixed dates to plan against.

Ended on 29 September: Amazon Mechanical Turk

AWS says Amazon Mechanical Turk "reached end of support" and is no longer available as of 29 September 2026. MTurk was the crowd-work marketplace many research teams and data-labelling pipelines used to pay people for small tasks such as tagging images, transcribing audio or answering surveys. GeekWire reported the shutdown the same day from the workers' side.

What to do: if any internal tool, research study or labelling pipeline still calls the MTurk API, it has stopped working. Move the work to another labelling vendor or an in-house workforce, and check for task results or worker data you still need to export or delete under your own retention rules.

Closed to new customers from 29 October 2026

Two services move to maintenance. From 29 October 2026 new customers cannot start using them. Existing customers can carry on, and AWS says it will keep operating and supporting them:

• Amazon Chime SDK SIP Media Application
• Amazon WorkSpaces Secure Browser

What to do: existing users are not forced to move. But a service in maintenance gets no new features, so do not build new projects on either one. If a team is evaluating one of them now, the account needs to be onboarded before 29 October or the plan should change.

Entering sunset, with end-of-support dates

These four have a fixed end date. AWS asks users to plan a migration using the updated service pages:

Service	End of support
AWS Infrastructure Composer (standalone console only)	7 December 2026
Amazon Managed Blockchain	29 September 2027
AWS Backint Agent for SAP ASE	29 September 2027
Amazon DevOps Guru	30 September 2027

The Infrastructure Composer date is the near one: only the standalone console ends, and teams that use it to draw CloudFormation templates should move to the alternative AWS points to before December. DevOps Guru users lose its machine-learning anomaly detection and should compare CloudWatch's own anomaly detection or a third-party observability tool. SAP teams backing up SAP ASE databases with the Backint Agent need a new backup route before September 2027.

Why it matters for buyers

These come on top of the AWS retirements that fall in October, among them WAF Classic, Proton and Greengrass v1, which we covered on 29 September. The pattern is the same each time: an announcement, a maintenance stage that closes the door to newcomers, then an end date about a year out. When you choose any cloud service, check the provider's product lifecycle page as part of due diligence. Build an exit route into the design of anything that depends on a narrow, less-used service.

AWS points customers to its product lifecycle page and says migration guides exist for the affected services. Neither the announcement nor the lifecycle page gives a reason for the changes.

Sources

• AWS What’s New: AWS Service Availability Updates — 29 September 2026
• GeekWire: gig workers look back as Amazon’s Mechanical Turk shuts down — 29 September 2026