User Role: Administrator, Workspace manager, Editor
AWS Secrets Manager encrypts sensitive information to prevent unauthorized users from accessing your database. This information can include your URL, username, password, API encryption keys, passwords, tokens, and certificates. You should use this to store sensitive Liquibase authentication details if you need teammates to connect to a database without having direct access to credentials.
For more information, see AWS Secrets Manager documentation.
It is important to note that you can only create an AWS Secrets Manager connection if you are an IAM user. You must use an AWS Access Key ID and AWS Secret Access Key that is not temporary.
2. Select the Add Connection button.
3. Type the Connection name and select the AWS Secrets Manager platform.
Each connection name must be unique within your Liquibase.io instance, and no two connections can have the same name.
Connection Name
Select the AWS Secrets Manager platform.
4. Fill in your AWS Access Key ID, AWS Secret Access Key, and AWS Region and select the Save button.
As an IAM user, you must use an AWS Access Key ID and AWS Secret Access Key that is not temporary.
Learn more about IAM user access keys here
The vault connection is successfully created.