Amazon DevOps Guru ends support on September 30, 2027: what to move and when

On September 29, 2026, AWS announced that Amazon DevOps Guru is entering sunset, the lifecycle stage in which AWS sets the date it will end operations and support of a service. DevOps Guru stops accepting new customers on October 29, 2026. Accounts signed up before that date can keep using it until end of support on September 30, 2027. After that date the service can no longer be used.

DevOps Guru is a managed service that applies machine learning to operational data, metrics, and events, and reports what it finds as insights. AWS states that because it is a monitoring tool, losing it does not interrupt running workloads. The risk is in what teams have built around it.

What stops working

Until end of support, AWS says it will provide security patches and critical bug fixes, maintain availability, and continue support, but it will not add features. According to the AWS end of support guide, after September 30, 2027:

The DevOps Guru console is no longer accessible.
DevOps Guru API operations are no longer available. Internal tools, dashboards, and ticketing integrations that pull insights through the API stop returning data.
The CloudFormation resource types AWS::DevOpsGuru::ResourceCollection and AWS::DevOpsGuru::NotificationChannel are withdrawn. Templates and stacks that reference them fail to create or update.
Insights that DevOps Guru generated earlier can no longer be retrieved.

AWS calls the infrastructure as code issue the highest-severity impact, because a single failed resource can block an entire stack operation. A leftover DevOps Guru resource can therefore hold up changes to everything else in the same stack.

Where AWS says to move

The guide names two destinations, depending on how you use the service:

For anomaly detection and alerting on metrics: Amazon CloudWatch. CloudWatch anomaly detection builds a model of a metric's expected values from its past data, including hourly, daily, and weekly patterns. An alarm can then trigger when the metric goes above the band of expected values, below it, or either.
For enriching, correlating, and investigating operational issues: AWS DevOps Agent, which AWS documents as an AI-powered agent for investigating and preventing operational issues. The guide says to explore it. Some of its capabilities are labeled preview in its documentation, so check their status before you depend on them.

CloudWatch anomaly detection is enabled for a metric, not for a whole application. The migration therefore includes deciding which metrics to cover and where each alarm should be sent.

A migration plan

Take inventory. List every account and Region where DevOps Guru is enabled, and every template, stack, script, and tool that references it.
Export what you want to keep. AWS recommends using both an Amazon SNS notification channel, to capture insights from now until end of support, and the DevOps Guru API, to export the insights already accumulated.
Build the replacement CloudWatch alarms and notifications before you remove anything.
Remove DevOps Guru resources from your templates and deploy the change. AWS advises doing this in the templates, not by deleting resources out of band, so that stacks and templates stay in agreement.
Update API integrations to read equivalent signals from CloudWatch.
When the export is complete, set analysis coverage to None in each account and Region. AWS says this stops analysis and stops charges.

One caution on the date. The announcement and the service guide both give September 30, 2027, while the AWS General Reference list of services in sunset shows September 29, 2027. Plan to finish well before either.

Other changes in the same announcement

Amazon WorkSpaces Secure Browser and Amazon Chime SDK SIP Media Application move to maintenance. They close to new customers starting October 29, 2026. Existing customers can continue to use them, and AWS will continue to operate and support them.
Amazon Managed Blockchain and AWS Backint Agent for SAP ASE end support on September 29, 2027.
AWS Infrastructure Composer is entering sunset, with end of support for its standalone console on December 7, 2026.

If any of these appear in your accounts, read the AWS guide linked from the announcement for that service and put the date on your roadmap now.