Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Preferences
Contact Us
Feedback
AWS Documentation
Create an AWS Account

Offboard from Monitoring and Incident Management for Amazon EKS in AMS Accelerate

PDF
RSS
Focus mode
Offboard from Monitoring and Incident Management for Amazon EKS in AMS Accelerate - AMS Accelerate User Guide

Notify your Cloud Service Delivery Manager (CSDM) with account IDs and cluster names to start the offboarding process. After you offboard, alert processing, metric storage, and metric querying are suspended and metrics are deleted in accordance with the default Amazon Managed Service for Prometheus data retention policies.

AMS performs the following offboarding steps:

  1. AMS disables alerts that are sent to you and AMS Operations.

  2. AMS removes the Prometheus instance from your Amazon EKS cluster.

  3. AMS removes other AWS resources that are installed in your account, such as IAM roles and AWS Config rules.

After these steps are completed, you must complete the following offboarding steps:

  1. Use eksctl to remove the Kubernetes RBAC permissions from the aws-auth ConfigMap.

  2. If you previously installed it, remove the Amazon Managed Grafana instance that you configured to connect to AMS.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.