- Task
- Version · 6.0.2
- Create
Use the AWS Secrets manager extension
Last updated: November 17, 2026
The Liquibase AWS extension is included in Liquibase Secure, so you do not need to download or install it. If you previously installed the standalone AWS S3, AWS Secrets Manager, or Amazon DynamoDB Secure extensions, remove them to avoid conflicts.
You can natively read your application secrets in Liquibase with the AWS Secrets Manager extension. If you connect to your vault using the liquibase.properties file, you can store sensitive Liquibase authentication details such as database url, username, and password attributes, your Liquibase Secure license key, and the license endpoint settings in your vault.
Note: By default, AWS Secrets Manager enforces TLS, ensuring that secrets are safe in transit. Learn more here: Infrastructure security in AWS Secrets Manager.
For more information, see AWS Secrets Manager documentation.
Before you begin
Liquibase 4.18.0+
AWS Secrets Manager credentials.
Configure your AWS credentials in any standard method.
aws_access_key_id,aws_secret_access_keyandaws_regionare required.
Procedure
In AWS Secrets Manager, configure sensitive properties like your database username, password, URL, Liquibase Secure license key, and license endpoint settings as secrets.
Gather the secret name of each secret in your vault.
For example, my-database-secret.
Specify each secret name.
Specify each secret using the format VAULT,SECRET,KEY in your liquibase.properties file or any other supported configuration method, such as environment variables or command-line arguments. For example, use this syntax as the value for parameters like url. If you're using AWS Systems Manager instead of Secrets Manager, use the format VAULT,PARAMETER.
The following example shows a liquibase.properties file configured to store secrets in a vault:
# Liquibase Secure license key
liquibase.licenseKey= aws-secrets,liquibase-secret-license,pro_key
# AWS Secrets Manager
url= aws-secrets,liquibase-secret,url
username= aws-secrets,liquibase-secret,username
password= aws-secrets,liquibase-secret,password
# AWS Systems Manager
url= aws-ssm,liquibase-secret-url
username= aws-ssm,liquibase-secret-username
password= aws-ssm,liquibase-secret-password
License from the license endpoint
A node that gets its license from the license endpoint can read the endpoint URL in liquibase.license.endpointUrl and the access token in liquibase.platform.apiKey from AWS Secrets Manager too. So can liquibase.license.cacheFile and liquibase.license.endpointTimeoutSeconds. Liquibase reads these four settings before the node has a license. Every other setting held in a secrets manager is read only after the node is licensed.
The following example sets every Liquibase Secure credential for a pipeline from AWS Secrets Manager:
If one of the four license settings cannot be resolved, the run is refused with LB-LIC-0029. The message names the setting and shows the AWS Secrets Manager error.