> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/enterprise/keeper-connection-manager/kcm-version-2.20.1.md).

# KCM Version 2.20.1

Released on August 25, 2025

## Support for EL9 <a href="#support-for-el9" id="support-for-el9"></a>

**KCM-408**: Add EL9 build for Keeper Connection Manager

KCM has historically support EL7 and EL8 versions of Red Hat and derivatives, with EL7 support having been dropped in our previous release. This release introduces package builds and support for EL9.

## Production of SBOMs as part of KCM build <a href="#production-of-sboms-as-part-of-kcm-build" id="production-of-sboms-as-part-of-kcm-build"></a>

**KCM-429**: Produce SBOM for all packages included with Keeper Connection Manager

Each RPM package produced as part of KCM now includes at least one SBOM describing its contents, and the Docker images that contain KCM packages also contain these SBOM files.

The files can be found beneath `/opt/keeper/share` for each relevant component of each KCM package installed.<br>

***

[Upgrade instructions](/release-notes/enterprise/keeper-connection-manager/upgrading.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/release-notes/enterprise/keeper-connection-manager/kcm-version-2.20.1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.