---
name: openshift-ts-ingress-esssmi
title: 'Ingress error: ESSSMI'
description: Troubleshoot Ingress ESSSMI (Exposed Service Set missing Service Monitor Instance) errors.
last-updated: 2026-08-12
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Ingress error: ESSSMI
{: #ts-ingress-esssmi}
{: troubleshoot}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf} [Satellite]{: tag-satellite}

Troubleshoot Ingress ESSSMI (Exposed Service Set missing Service Monitor Instance) errors.
{: shortdesc}


When you check the status of your cluster's Ingress components by running the `ibmcloud oc ingress status-report get` command, you see an error similar to the following example.
{: tsSymptoms}

```sh
Could not access Secrets Manager instance (ESSSMI).
```
{: screen}

Red Hat OpenShift on IBM Cloud receives an unauthorized message when attempting to update or apply secrets from the Secrets Manager instance registered with the cluster.
{: tsCauses}

1. Follow the steps to ensure you have a valid [service-to-service authorization policy](https://cloud.ibm.com/docs/openshift?topic=openshift-secrets-mgr&format=markdown#secrets-mgr_setup_s2s) in place for the Kubernetes Service and Secrets Manager.
{: tsResolve}

1. If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/support?topic=support-using-avatar&format=markdown). In the case details, be sure to include any relevant log files, error messages, or command outputs.