AWS published service availability changes on September 29, 2026. Amazon Chime SDK SIP Media Application and Amazon WorkSpaces Secure Browser move to maintenance, restricting new customer access starting October 29. Existing users can continue using those services under the terms described in the notice.
The same update lists sunsets for Amazon Managed Blockchain, Amazon DevOps Guru and AWS Backint Agent for SAP ASE in September 2027, and the Infrastructure Composer standalone console in December 2026. It also says Mechanical Turk reached end of support on September 29. These are distinct lifecycle states, not one universal shutdown date.
Map the dates to what your application uses
The AWS notice gives Managed Blockchain and Backint Agent September 29, 2027 end dates, DevOps Guru September 30, 2027 and the standalone Infrastructure Composer console December 7, 2026. Review the linked product guidance for your configuration. A change to a named feature should not be generalized to every related AWS product.
Canadian cloud teams should inventory resources, automation scripts, documentation and billing references before deciding whether they are affected. A service can be present through an older deployment template even if nobody uses its console regularly. Assign an owner to each dependency and keep evidence of whether it is active.
Related sources: AWS September service availability update ↗
Plan a migration around observed behaviour
Define the behaviour a replacement must preserve: inputs, outputs, permissions and any recovery requirements. Test with a non-production copy of a representative workload. A similarly named service may differ in data formats or access controls, so migrating the application name alone is not a validation plan.
Record how data will be exported, checked and removed from the old environment. Preserve a rollback path while both systems are available. Include the least visible dependencies, such as alerts, deployment scripts and scheduled jobs; they are often discovered only after a new service appears to work during the first demonstration.
Budget time as well as cloud charges
A transition can temporarily require two environments and additional staff review. Estimate that overlap before setting a deadline, and verify any regional availability needed by the replacement. This announcement does not establish a price increase, so do not attribute migration cost to a new rate without checking the actual bill and pricing pages.
Our analysis is that lifecycle notices are operational news worth acting on early. Separate immediate failures from future planning: confirm whether a named service is actually used, then work backward from its applicable date. A documented inventory is more valuable than rushing every application into a redesign based on a headline.
Sources and editorial method
We use the linked original statements and reports to distinguish documented facts from our analysis. Company announcements describe their authors’ plans and claims; they are not independent verification of future outcomes. This article is dated and will be revised if material evidence changes. Read our editorial standards and corrections process.
- AWS September service availability update ↗ — Primary September 29, 2026 notice; maintenance restrictions and service-specific end-of-support dates.