This document guides you on how to enable and disable database secrets in SSM. After a secret is disabled, applications cannot obtain its content through the SDK. This is applicable in scenarios such as temporarily disabling secrets or for security control.
Prerequisites
A database secret has been created. If you have not created one, refer to Create Database Secret to create it. Disabling Secrets
1. Log in to the SSM console and click Database Credential in the left sidebar. 2. On the Database Secrets list page, select the region where your secrets are located in the upper-left corner.
3. In the Secrets list, locate the target secret whose status is enabled.
4. In the operation column, click Disable to disable the secret.
Note:
After a secret is disabled, an error will be returned when the application calls GetSecretValue through the SDK to obtain the secret content.
Enabling Secrets
1. In the Secrets list, locate the target secret whose status is disabled.
2. In the Operation column, click Enable. The secret will then be restored to the enabled state, and the application can normally obtain the secret content through the SDK.
Note:
Disabling a secret does not delete the secret data. Information such as the secret content, version history, and rotation configuration remains unchanged, and the secret can be re-enabled at any time.
While a secret is disabled, configured automatic rotation tasks will be suspended and will not automatically update the password.
After it is re-enabled, automatic rotation will resume according to the original configuration.