View a markdown version of this page

Amazon DevOps Guru end of support - Amazon DevOps Guru
OverviewService status until September 30, 2027What this means for youChoosing the right migration pathAlternative solutionsMigration stepsOffboarding steps: Export your dataFrequently asked questionsAdditional resources

End of support notice: On September 30, 2027, AWS will end support for Amazon DevOps Guru. After September 30, 2027, you will no longer be able to access the Amazon DevOps Guru console or Amazon DevOps Guru resources. For more information, see Amazon DevOps Guru end of support.

Amazon DevOps Guru end of support

Overview

After careful consideration, we decided to end support for Amazon DevOps Guru, effective September 30, 2027. Amazon DevOps Guru will no longer accept new customers beginning October 29, 2026. As an existing customer with an account signed up for the service before October 29, 2026, you can continue to use Amazon DevOps Guru features. After September 30, 2027, you will no longer be able to use Amazon DevOps Guru.

We recommend that customers move their alerting and anomaly-detection needs to Amazon CloudWatch, and, for AI-assisted operational investigation and insight enrichment, explore Amazon DevOps Agent. See Alternative solutions for details.

Service status until September 30, 2027

Until September 30, 2027, existing Amazon DevOps Guru customers can continue to use the service normally. During this period, AWS will:

  1. Provide security patches and critical bug fixes

  2. Maintain service availability and performance

  3. Continue to offer support through AWS Support channels

  4. Not add new features to the service

What happens to your resources after September 30, 2027

After September 30, 2027:

  • You will no longer be able to access the Amazon DevOps Guru console.

  • Amazon DevOps Guru API operations will no longer be available. Any application, script, or pipeline that calls the Amazon DevOps Guru API will need to be updated before this date. See What this means for you.

  • The Amazon DevOps Guru resource types will be withdrawn, and AWS CloudFormation or AWS CLI operations that create or update those resource types will fail. See Migrate infrastructure as code and CLI usage.

  • Insights previously generated by Amazon DevOps Guru will no longer be retrievable.

What this means for you

The impact of this change depends on how you use Amazon DevOps Guru. Because Amazon DevOps Guru is a monitoring tool, the loss does not interrupt running workloads. Customers who have built automation, infrastructure as code, or downstream tooling on top of Amazon DevOps Guru need to take action before September 30, 2027 to avoid any impact.

If you declare Amazon DevOps Guru resources in infrastructure as code (AWS CloudFormation, AWS CDK, Terraform) or the AWS CLI. Templates and stacks that reference AWS::DevOpsGuru::ResourceCollection or AWS::DevOpsGuru::NotificationChannel will fail to create or update once the resource types are withdrawn. Because a single failed resource can block an entire stack operation, this is the highest-severity impact. Remove these resources from your templates before end of support. See Migrate infrastructure as code and CLI usage.

If you call the Amazon DevOps Guru API from your own tooling. If you pull insights into internal developer tools, dashboards, or ticketing systems through the Amazon DevOps Guru API, those integrations will stop returning data at end of support. Update them to source the equivalent signals from Amazon CloudWatch. See Migrate API integrations.

Choosing the right migration path

Use the following guidance to decide where to move each way you use Amazon DevOps Guru today.

  • You use Amazon DevOps Guru primarily for anomaly detection and alerting on metrics. Move to Amazon CloudWatch. See Amazon CloudWatch.

  • You use Amazon DevOps Guru to enrich, correlate, or investigate operational issues. Explore Amazon DevOps Agent. See Amazon DevOps Agent.

Alternative solutions

We have identified the following alternatives to Amazon DevOps Guru that can help you maintain operational visibility and anomaly detection.

Amazon CloudWatch

Best for: Customers who use Amazon DevOps Guru for metric anomaly detection and operational alerting.

Amazon CloudWatch provides metric monitoring, alarms, and anomaly detection across your AWS resources and applications.

Key benefits:

  1. Native anomaly detection on CloudWatch metrics, with alarms that notify you when metrics deviate from expected patterns.

  2. Broad, first-party coverage of AWS services and custom metrics.

  3. Integrated with the wider CloudWatch observability suite (metrics, logs, dashboards).

Learn more: Amazon CloudWatch documentation.

Amazon DevOps Agent

Best for: Customers who rely on Amazon DevOps Guru to enrich, correlate, and investigate operational issues.

Learn more: Amazon DevOps Agent documentation.

Migration steps

The following sections describe how to migrate your infrastructure as code, CLI usage, and API integrations off Amazon DevOps Guru before September 30, 2027.

Migrate infrastructure as code and CLI usage

If you declare Amazon DevOps Guru resources in AWS CloudFormation, AWS CDK, Terraform, or create them through the AWS CLI, remove those resources before September 30, 2027 to avoid failed stack operations.

Amazon DevOps Guru exposes the following resource types:

  • AWS::DevOpsGuru::ResourceCollection

  • AWS::DevOpsGuru::NotificationChannel

  1. Inventory the templates and stacks that reference the preceding resource types.

  2. Stand up the equivalent Amazon CloudWatch configuration (for example, the alarms and notifications that replace your Amazon DevOps Guru notification channel).

  3. Remove the Amazon DevOps Guru resources from your templates and deploy the change so the resources are no longer managed by your stacks.

Migrate API integrations

If your tooling calls the Amazon DevOps Guru API, update it to source equivalent signals from Amazon CloudWatch before end of support.

Offboarding steps: Export your data

Amazon DevOps Guru insights are not retrievable after September 30, 2027. If you want to keep a record of your insights, export them before that date. There are two ways to do this, and we recommend that most customers use both: an Amazon SNS notification channel to capture insights from now until end of support, and the Amazon DevOps Guru API to export the insights you have already accumulated.

Delete your Amazon DevOps Guru resources

To stop analysis and stop incurring charges before end of support, set your analysis coverage to None for each account and Region where Amazon DevOps Guru is enabled. In the console, choose Settings, then DevOps Guru analysis coverage, then Manage, then None. You can also call UpdateResourceCollection to remove the CloudFormation stacks or tags that define your coverage boundary. Complete your data export before you do this.

To remove a notification channel, call RemoveNotificationChannel or delete it from Settings in the console. Removing the channel does not delete the Amazon SNS topic or anything you have already archived through it.

If you declare Amazon DevOps Guru resources in infrastructure as code, remove them from your templates rather than deleting them out of band, so your stacks and templates stay in agreement. See Migrate infrastructure as code and CLI usage.

Frequently asked questions

Will my applications or databases stop working after September 30, 2027?

No. Amazon DevOps Guru is a monitoring service: it observes resources you run, it does not host them. After end of support you lose Amazon DevOps Guru's visibility and recommendations, but your applications, databases, and infrastructure continue to run.

What happens if I do not migrate by September 30, 2027?

After September 30, 2027 you will no longer be able to access the Amazon DevOps Guru console or API, and Amazon DevOps Guru resource types will fail in AWS CloudFormation and the AWS CLI.

Additional resources

For more information, see the following resources.

If you have additional questions, contact AWS Support.