After cluster installation, some required monitoring pods cannot get persistent volumes attached when using custom AWS KMS key

Solution Verified - Updated -


  • After installing a Red Hat OpenShift on AWS by using a custom AWS KMS key, the monitoring operator is in DEGRADED state.
  • The pods alertmanager-main and prometheus-k8s along with their Persistent Volume Claims from openshift-monitoring namespace are on Pending state.


  • Red Hat OpenShift Service on AWS [ROSA]
    • 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content