# Rotating DB Connection credentials using AWS Secret Manager

**URL:** <https://forum.keycloak.org/t/rotating-db-connection-credentials-using-aws-secret-manager/20452>\
**Category:** Getting advice\
**Created:** [February 23, 2023, 10:01am UTC](https://forum.keycloak.org/t/rotating-db-connection-credentials-using-aws-secret-manager/20452 "2023-02-23T10:01:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dingo](https://avatars.discourse-cdn.com/v4/letter/d/c2a13f/32.png) [@Dingo](https://forum.keycloak.org/u/Dingo)\
**Post date:** [February 23, 2023, 10:01am UTC](https://forum.keycloak.org/t/rotating-db-connection-credentials-using-aws-secret-manager/20452/1 "2023-02-23T10:01:47Z")

</div>

I am trying to utilise AWS Secrets Manager to generate and automatically rotate secrets for my DB credentials (password).

From my research, it looks like one option is that the container running KeyCloak will need to be restarted when the secret is rotated. Alternatively, AWS provide a JDBC package that can cache secret information to obtain a new secret once it is rotated ([GitHub - aws/aws-secretsmanager-jdbc: The AWS Secrets Manager JDBC Library enables Java developers to easily connect to SQL databases using secrets stored in AWS Secrets Manager.](https://github.com/aws/aws-secretsmanager-jdbc)).

I am a Java novice, and was hoping I could get some advice on how to implement this on the KeyCloak server?

Alternatively, they provide this package ([GitHub - aws/aws-secretsmanager-caching-java: The AWS Secrets Manager Java caching client enables in-process caching of secrets for Java applications.](https://github.com/aws/aws-secretsmanager-caching-java/)) to cache secrets from Secrets Manager.

---

<div class="post-metadata">

**Author:** ![sachin1994](https://avatars.discourse-cdn.com/v4/letter/s/ce73a5/32.png) [@sachin1994](https://forum.keycloak.org/u/sachin1994)\
**Post date:** [May 12, 2026, 9:14am UTC](https://forum.keycloak.org/t/rotating-db-connection-credentials-using-aws-secret-manager/20452/2 "2026-05-12T09:14:46Z")

</div>

@Dingo We are hit with the same issue. Do you have any work around? Your inputs are really valuable for us.
