diff --git a/docs/documentation/platform/dynamic-secrets/aws-elasticache.mdx b/docs/documentation/platform/dynamic-secrets/aws-elasticache.mdx
index 2cf4edc0e..de8278a8f 100644
--- a/docs/documentation/platform/dynamic-secrets/aws-elasticache.mdx
+++ b/docs/documentation/platform/dynamic-secrets/aws-elasticache.mdx
@@ -60,7 +60,7 @@ The Infisical AWS ElastiCache dynamic secret allows you to generate AWS ElastiCa
-
+
@@ -94,21 +94,29 @@ The Infisical AWS ElastiCache dynamic secret allows you to generate AWS ElastiCa
- If you want to provide specific privileges for the generated dynamic credentials, you can modify the ElastiCache statement to your needs. This is useful if you want to only give access to a specific table(s).
+ 
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
- 
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
+ If you want to provide specific privileges for the generated dynamic credentials, you can modify the ElastiCache statement to your needs. This is useful if you want to only give access to a specific table(s).
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
- If this step fails, you may have to add the CA certificate.
+ If this step fails, you may have to add the CA certificate.
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
@@ -123,14 +131,14 @@ The Infisical AWS ElastiCache dynamic secret allows you to generate AWS ElastiCa
- Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the expiration time of the lease or delete a lease before it's set time to live.
@@ -141,4 +149,4 @@ To extend the life of the generated dynamic secret leases past its initial time
Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret
-
\ No newline at end of file
+
diff --git a/docs/documentation/platform/dynamic-secrets/aws-iam.mdx b/docs/documentation/platform/dynamic-secrets/aws-iam.mdx
index 730e2b287..56a10419c 100644
--- a/docs/documentation/platform/dynamic-secrets/aws-iam.mdx
+++ b/docs/documentation/platform/dynamic-secrets/aws-iam.mdx
@@ -40,7 +40,7 @@ Infisical needs an initial AWS IAM user with the required permissions to create
}
```
-To minimize managing user access you can attach a resource in format
+To minimize managing user access you can attach a resource in format
> arn:aws:iam::\:user/\
@@ -94,28 +94,36 @@ Replace **\** with your AWS account id and **\** w
- The AWS IAM groups that should be assigned to the created users. Multiple values can be provided by separating them with commas
+ The AWS IAM groups that should be assigned to the created users. Multiple values can be provided by separating them with commas
-
+
- The AWS IAM managed policies that should be attached to the created users. Multiple values can be provided by separating them with commas
+ The AWS IAM managed policies that should be attached to the created users. Multiple values can be provided by separating them with commas
- The AWS IAM inline policy that should be attached to the created users. Multiple values can be provided by separating them with commas
+ The AWS IAM inline policy that should be attached to the created users. Multiple values can be provided by separating them with commas
+
+
+
+Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
+
+Allowed template variables are
+- `{{randomUsername}}`: Random username string
+- `{{unixTimestamp}}`: Current Unix timestamp
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
@@ -130,14 +138,14 @@ Replace **\** with your AWS account id and **\** w
- Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the lease details and delete the lease ahead of its expiration time.
diff --git a/docs/documentation/platform/dynamic-secrets/cassandra.mdx b/docs/documentation/platform/dynamic-secrets/cassandra.mdx
index e7ec4f69d..0c4221f53 100644
--- a/docs/documentation/platform/dynamic-secrets/cassandra.mdx
+++ b/docs/documentation/platform/dynamic-secrets/cassandra.mdx
@@ -7,7 +7,7 @@ The Infisical Cassandra dynamic secret allows you to generate Cassandra database
## Prerequisite
-Infisical requires a Cassandra user in your instance with the necessary permissions. This user will facilitate the creation of new accounts as needed.
+Infisical requires a Cassandra user in your instance with the necessary permissions. This user will facilitate the creation of new accounts as needed.
Ensure the user possesses privileges for creating, dropping, and granting permissions to roles for it to be able to create dynamic secrets.
@@ -19,7 +19,7 @@ authorizer: CassandraAuthorizer
```
-The above configuration allows user creation and granting permissions.
+The above configuration allows user creation and granting permissions.
## Set up Dynamic Secrets with Cassandra
@@ -69,31 +69,39 @@ The above configuration allows user creation and granting permissions.
Keyspace name where you want to create dynamic secrets. This ensures that the user is limited to that keyspace.
-
+
- A CA may be required if your cassandra requires it for incoming connections.
+ A CA may be required if your cassandra requires it for incoming connections.
- If you want to provide specific privileges for the generated dynamic credentials, you can modify the CQL statement to your needs. This is useful if you want to only give access to a specific key-space(s).
+ 
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
- 
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
+ If you want to provide specific privileges for the generated dynamic credentials, you can modify the CQL statement to your needs. This is useful if you want to only give access to a specific key-space(s).
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
- If this step fails, you may have to add the CA certficate.
+ If this step fails, you may have to add the CA certficate.
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
@@ -108,14 +116,14 @@ The above configuration allows user creation and granting permissions.
- Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the lease details and delete the lease ahead of its expiration time.
diff --git a/docs/documentation/platform/dynamic-secrets/elastic-search.mdx b/docs/documentation/platform/dynamic-secrets/elastic-search.mdx
index 0e1bc5104..6c5028bb2 100644
--- a/docs/documentation/platform/dynamic-secrets/elastic-search.mdx
+++ b/docs/documentation/platform/dynamic-secrets/elastic-search.mdx
@@ -7,13 +7,14 @@ The Infisical Elasticsearch dynamic secret allows you to generate Elasticsearch
## Prerequisites
-
-
1. Create a role with at least `manage_security` and `monitor` permissions.
2. Assign the newly created role to your API key or user that you'll use later in the dynamic secret configuration.
- For testing purposes, you can also use a highly privileged role like `superuser`, that will have full control over the cluster. This is not recommended in production environments following the principle of least privilege.
+ For testing purposes, you can also use a highly privileged role like
+ `superuser`, that will have full control over the cluster. This is not
+ recommended in production environments following the principle of least
+ privilege.
## Set up Dynamic Secrets with Elasticsearch
@@ -33,95 +34,115 @@ The Infisical Elasticsearch dynamic secret allows you to generate Elasticsearch
Name by which you want the secret to be referenced
-
- Default time-to-live for a generated secret (it is possible to modify this value after a secret is generated)
-
+
+ Default time-to-live for a generated secret (it is possible to modify this value after a secret is generated)
+
-
- Maximum time-to-live for a generated secret.
-
+
+ Maximum time-to-live for a generated secret.
+
-
+
Your Elasticsearch host. This is the endpoint that your instance runs on. _(Example: https://your-cluster-ip)_
-
+
-
- The port that your Elasticsearch instance is running on. _(Example: 9200)_
-
+
-
- The roles that the new user that is created when a lease is provisioned will be assigned to. This is a required field. This defaults to `superuser`, which is highly privileged. It is recommended to create a new role with the least privileges required for the lease.
-
+The port that your Elasticsearch instance is running on. _(Example: 9200)_
+
-
+
+ The roles that the new user that is created when a lease is provisioned will
+ be assigned to. This is a required field. This defaults to `superuser`, which
+ is highly privileged. It is recommended to create a new role with the least
+ privileges required for the lease.
+
+
+
Select the authentication method you want to use to connect to your Elasticsearch instance.
-
+
-
- The username of the user that will be used to provision new dynamic secret leases. Only required if you selected the `Username/Password` authentication method.
-
+
+ The username of the user that will be used to provision new dynamic secret
+ leases. Only required if you selected the `Username/Password` authentication
+ method.
+
-
- The password of the user that will be used to provision new dynamic secret leases. Only required if you selected the `Username/Password` authentication method.
-
+
+ The password of the user that will be used to provision new dynamic secret
+ leases. Only required if you selected the `Username/Password` authentication
+ method.
+
-
- The ID of the API key that will be used to provision new dynamic secret leases. Only required if you selected the `API Key` authentication method.
-
+
+ The ID of the API key that will be used to provision new dynamic secret
+ leases. Only required if you selected the `API Key` authentication method.
+
-
- The API key that will be used to provision new dynamic secret leases. Only required if you selected the `API Key` authentication method.
-
+
+ The API key that will be used to provision new dynamic secret leases. Only
+ required if you selected the `API Key` authentication method.
+
-
- A CA may be required if your DB requires it for incoming connections. This is often the case when connecting to a managed service.
-
+
+ A CA may be required if your DB requires it for incoming connections. This is often the case when connecting to a managed service.
+
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
- 
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
-
- If this step fails, you may have to add the CA certificate.
-
+
+ If this step fails, you may have to add the CA certificate.
+
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
- 
- 
+ 
+ 
- When generating these secrets, it's important to specify a Time-to-Live (TTL) duration. This will dictate how long the credentials are valid for.
+ When generating these secrets, it's important to specify a Time-to-Live (TTL) duration. This will dictate how long the credentials are valid for.
- 
+ 
-
- Ensure that the TTL for the lease fall within the maximum TTL defined when configuring the dynamic secret.
-
+
+ Ensure that the TTL for the lease fall within the maximum TTL defined when configuring the dynamic secret.
+
- Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
+
+ 
- 
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the expiration time of the lease or delete a lease before it's set time to live.
## Renew Leases
+
To extend the life of the generated dynamic secret leases past its initial time to live, simply click on the **Renew** button as illustrated below.
- Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret
+ Lease renewals cannot exceed the maximum TTL set when configuring the dynamic
+ secret
diff --git a/docs/documentation/platform/dynamic-secrets/ldap.mdx b/docs/documentation/platform/dynamic-secrets/ldap.mdx
index a1731432c..1a3eca404 100644
--- a/docs/documentation/platform/dynamic-secrets/ldap.mdx
+++ b/docs/documentation/platform/dynamic-secrets/ldap.mdx
@@ -123,6 +123,13 @@ The Infisical LDAP dynamic secret allows you to generate user credentials on dem
changetype: delete
```
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
+
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
diff --git a/docs/documentation/platform/dynamic-secrets/mongo-atlas.mdx b/docs/documentation/platform/dynamic-secrets/mongo-atlas.mdx
index 5eda1669e..983078796 100644
--- a/docs/documentation/platform/dynamic-secrets/mongo-atlas.mdx
+++ b/docs/documentation/platform/dynamic-secrets/mongo-atlas.mdx
@@ -6,11 +6,10 @@ description: "Learn how to dynamically generate Mongo Atlas Database user creden
The Infisical Mongo Atlas dynamic secret allows you to generate Mongo Atlas Database credentials on demand based on configured role.
## Prerequisite
+
Create a project scopped API Key with the required permission in your Mongo Atlas following the [official doc](https://www.mongodb.com/docs/atlas/configure-api-access/#grant-programmatic-access-to-a-project).
-
- The API Key must have permission to manage users in the project.
-
+The API Key must have permission to manage users in the project.
## Set up Dynamic Secrets with Mongo Atlas
@@ -29,86 +28,104 @@ Create a project scopped API Key with the required permission in your Mongo Atla
Name by which you want the secret to be referenced
-
- Default time-to-live for a generated secret (it is possible to modify this value after a secret is generated)
-
+
+ Default time-to-live for a generated secret (it is possible to modify this value after a secret is generated)
+
-
- Maximum time-to-live for a generated secret
-
+
+ Maximum time-to-live for a generated secret
+
-
- The public key of your generated Atlas API Key. This acts as a username.
-
+
+ The public key of your generated Atlas API Key. This acts as a username.
+
-
- The private key of your generated Atlas API Key. This acts as a password.
-
+
+ The private key of your generated Atlas API Key. This acts as a password.
+
-
- Unique 24-hexadecimal digit string that identifies your project. This is same as project id
-
+
+ Unique 24-hexadecimal digit string that identifies your project. This is same as project id
+
-
- List that provides the pairings of one role with one applicable database.
- - **Database Name**: Database to which the user is granted access privileges.
- - **Collection**: Collection on which this role applies.
- - **Role Name**: Human-readable label that identifies a group of privileges assigned to a database user. This value can either be a built-in role or a custom role.
- - Enum: `atlasAdmin` `backup` `clusterMonitor` `dbAdmin` `dbAdminAnyDatabase` `enableSharding` `read` `readAnyDatabase` `readWrite` `readWriteAnyDatabase` ``.
-
+
+ List that provides the pairings of one role with one applicable database.
+ - **Database Name**: Database to which the user is granted access privileges.
+ - **Collection**: Collection on which this role applies.
+ - **Role Name**: Human-readable label that identifies a group of privileges assigned to a database user. This value can either be a built-in role or a custom role.
+ - Enum: `atlasAdmin` `backup` `clusterMonitor` `dbAdmin` `dbAdminAnyDatabase` `enableSharding` `read` `readAnyDatabase` `readWrite` `readWriteAnyDatabase` ``.
+
- 
+ 
- List that contains clusters, MongoDB Atlas Data Lakes, and MongoDB Atlas Streams Instances that this database user can access. If omitted, MongoDB Cloud grants the database user access to all the clusters, MongoDB Atlas Data Lakes, and MongoDB Atlas Streams Instances in the project.
- 
- - **Label**: Human-readable label that identifies the cluster or MongoDB Atlas Data Lake that this database user can access.
- - **Type**: Category of resource that this database user can access.
+
+
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
+
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
+
+ List that contains clusters, MongoDB Atlas Data Lakes, and MongoDB Atlas Streams Instances that this database user can access. If omitted, MongoDB Cloud grants the database user access to all the clusters, MongoDB Atlas Data Lakes, and MongoDB Atlas Streams Instances in the project.
+ - **Label**: Human-readable label that identifies the cluster or MongoDB Atlas Data Lake that this database user can access.
+ - **Type**: Category of resource that this database user can access.
+
+
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
-
- If this step fails, you may have to add the CA certficate.
-
+
+ If this step fails, you may have to add the CA certficate.
+
+
+ 
- 
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
- 
- 
+ 
+ 
- When generating these secrets, it's important to specify a Time-to-Live (TTL) duration. This will dictate how long the credentials are valid for.
+ When generating these secrets, it's important to specify a Time-to-Live (TTL) duration. This will dictate how long the credentials are valid for.
- 
+ 
-
- Ensure that the TTL for the lease fall within the maximum TTL defined when configuring the dynamic secret.
-
+
+ Ensure that the TTL for the lease fall within the maximum TTL defined when configuring the dynamic secret.
+
- Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
+
+ 
- 
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the expiration time of the lease or delete a lease before it's set time to live.
## Renew Leases
+
To extend the life of the generated dynamic secret leases past its initial time to live, simply click on the **Renew** button as illustrated below.
- Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret
+ Lease renewals cannot exceed the maximum TTL set when configuring the dynamic
+ secret
diff --git a/docs/documentation/platform/dynamic-secrets/mongo-db.mdx b/docs/documentation/platform/dynamic-secrets/mongo-db.mdx
index ec384f7a9..f71922473 100644
--- a/docs/documentation/platform/dynamic-secrets/mongo-db.mdx
+++ b/docs/documentation/platform/dynamic-secrets/mongo-db.mdx
@@ -62,25 +62,32 @@ Create a user with the required permission in your MongoDB instance. This user w
Human-readable label that identifies a group of privileges assigned to a database user. This value can either be a built-in role or a custom role.
- Enum: `atlasAdmin` `backup` `clusterMonitor` `dbAdmin` `dbAdminAnyDatabase` `enableSharding` `read` `readAnyDatabase` `readWrite` `readWriteAnyDatabase` ``.
-
+
A CA may be required if your DB requires it for incoming connections.
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
+
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
- If this step fails, you may have to add the CA certificate.
+ If this step fails, you may have to add the CA certificate.
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
@@ -95,14 +102,14 @@ Create a user with the required permission in your MongoDB instance. This user w
- Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the expiration time of the lease or delete a lease before it's set time to live.
diff --git a/docs/documentation/platform/dynamic-secrets/mssql.mdx b/docs/documentation/platform/dynamic-secrets/mssql.mdx
index 2a279ce90..4fc710e01 100644
--- a/docs/documentation/platform/dynamic-secrets/mssql.mdx
+++ b/docs/documentation/platform/dynamic-secrets/mssql.mdx
@@ -62,7 +62,7 @@ Create a user with the required permission in your SQL instance. This user will
Name of the database for which you want to create dynamic secrets
-
+
A CA may be required if your DB requires it for incoming connections. AWS RDS instances with default settings will requires a CA which can be downloaded [here](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.CertificatesAllRegions).
@@ -71,22 +71,30 @@ Create a user with the required permission in your SQL instance. This user will
- If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs. This is useful if you want to only give access to a specific table(s).
+ 
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
- 
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
+ If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs. This is useful if you want to only give access to a specific table(s).
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
- If this step fails, you may have to add the CA certficate.
+ If this step fails, you may have to add the CA certficate.
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
@@ -101,14 +109,14 @@ Create a user with the required permission in your SQL instance. This user will
- Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the expiration time of the lease or delete the lease before it's set time to live.
diff --git a/docs/documentation/platform/dynamic-secrets/mysql.mdx b/docs/documentation/platform/dynamic-secrets/mysql.mdx
index f88a88d35..6f708ebba 100644
--- a/docs/documentation/platform/dynamic-secrets/mysql.mdx
+++ b/docs/documentation/platform/dynamic-secrets/mysql.mdx
@@ -61,29 +61,37 @@ Create a user with the required permission in your SQL instance. This user will
Name of the database for which you want to create dynamic secrets
-
+
A CA may be required if your DB requires it for incoming connections. AWS RDS instances with default settings will requires a CA which can be downloaded [here](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.CertificatesAllRegions).
- If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs. This is useful if you want to only give access to a specific table(s).
+ 
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
- 
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
+ If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs. This is useful if you want to only give access to a specific table(s).
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
- If this step fails, you may have to add the CA certificate.
+ If this step fails, you may have to add the CA certificate.
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
@@ -98,14 +106,14 @@ Create a user with the required permission in your SQL instance. This user will
- Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the expiration time of the lease or delete a lease before it's set time to live.
@@ -116,4 +124,4 @@ To extend the life of the generated dynamic secret leases past its initial time
Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret
-
\ No newline at end of file
+
diff --git a/docs/documentation/platform/dynamic-secrets/oracle.mdx b/docs/documentation/platform/dynamic-secrets/oracle.mdx
index c7b34bec9..c1a15fd9f 100644
--- a/docs/documentation/platform/dynamic-secrets/oracle.mdx
+++ b/docs/documentation/platform/dynamic-secrets/oracle.mdx
@@ -61,7 +61,7 @@ Create a user with the required permission in your SQL instance. This user will
Name of the database for which you want to create dynamic secrets
-
+
A CA may be required if your DB requires it for incoming connections. AWS RDS instances with default settings will requires a CA which can be downloaded [here](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.CertificatesAllRegions).
@@ -70,20 +70,30 @@ Create a user with the required permission in your SQL instance. This user will
+ 
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
+
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs. This is useful if you want to only give access to a specific table(s).
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
- If this step fails, you may have to add the CA certficate.
+ If this step fails, you may have to add the CA certficate.
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
@@ -98,14 +108,14 @@ Create a user with the required permission in your SQL instance. This user will
- Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the expiration time of the lease or delete a lease before it's set time to live.
@@ -116,4 +126,4 @@ To extend the life of the generated dynamic secret leases past its initial time
Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret
-
\ No newline at end of file
+
diff --git a/docs/documentation/platform/dynamic-secrets/postgresql.mdx b/docs/documentation/platform/dynamic-secrets/postgresql.mdx
index feb81d6d6..f6012d277 100644
--- a/docs/documentation/platform/dynamic-secrets/postgresql.mdx
+++ b/docs/documentation/platform/dynamic-secrets/postgresql.mdx
@@ -62,7 +62,7 @@ Create a user with the required permission in your SQL instance. This user will
Name of the database for which you want to create dynamic secrets
-
+
A CA may be required if your DB requires it for incoming connections. AWS RDS instances with default settings will requires a CA which can be downloaded [here](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.CertificatesAllRegions).
@@ -71,22 +71,30 @@ Create a user with the required permission in your SQL instance. This user will
- If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs. This is useful if you want to only give access to a specific table(s).
-
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
+
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
+ If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs. This is useful if you want to only give access to a specific table(s).
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
- If this step fails, you may have to add the CA certficate.
+ If this step fails, you may have to add the CA certficate.
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
@@ -101,14 +109,14 @@ Create a user with the required permission in your SQL instance. This user will
- Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the expiration time of the lease or delete the lease before it's set time to live.
diff --git a/docs/documentation/platform/dynamic-secrets/rabbit-mq.mdx b/docs/documentation/platform/dynamic-secrets/rabbit-mq.mdx
index 6ac5ac069..4ec7a62ab 100644
--- a/docs/documentation/platform/dynamic-secrets/rabbit-mq.mdx
+++ b/docs/documentation/platform/dynamic-secrets/rabbit-mq.mdx
@@ -9,7 +9,6 @@ The Infisical RabbitMQ dynamic secret allows you to generate RabbitMQ credential
1. Ensure that the `management` plugin is enabled on your RabbitMQ instance. This is required for the dynamic secret to work.
-
## Set up Dynamic Secrets with RabbitMQ
@@ -19,98 +18,116 @@ The Infisical RabbitMQ dynamic secret allows you to generate RabbitMQ credential
-
- 
+
+ 
Name by which you want the secret to be referenced
-
- Default time-to-live for a generated secret (it is possible to modify this value after a secret is generated)
-
+
+ Default time-to-live for a generated secret (it is possible to modify this value after a secret is generated)
+
-
- Maximum time-to-live for a generated secret.
-
+
+ Maximum time-to-live for a generated secret.
+
-
+
Your RabbitMQ host. This must be in HTTP format. _(Example: http://your-cluster-ip)_
-
+
-
- The port that the RabbitMQ management plugin is listening on. This is `15672` by default.
-
+
-
- The name of the virtual host that the user will be assigned to. This defaults to `/`.
-
+The port that the RabbitMQ management plugin is listening on. This is `15672` by default.
+
+
+
+ The name of the virtual host that the user will be assigned to. This defaults
+ to `/`.
+
The permissions that the user will have on the virtual host. This defaults to `.*`.
The three permission fields all take a regular expression _(regex)_, that should match resource names for which the user is granted read / write / configuration permissions
+
+
+ The username of the user that will be used to provision new dynamic secret
+ leases.
+
-
- The username of the user that will be used to provision new dynamic secret leases.
-
+
+ The password of the user that will be used to provision new dynamic secret
+ leases.
+
-
- The password of the user that will be used to provision new dynamic secret leases.
+
+ A CA may be required if your DB requires it for incoming connections. This is often the case when connecting to a managed service.
+
+Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
-
- A CA may be required if your DB requires it for incoming connections. This is often the case when connecting to a managed service.
-
+Allowed template variables are
+- `{{randomUsername}}`: Random username string
+- `{{unixTimestamp}}`: Current Unix timestamp
+
- 
+
+ A CA may be required if your DB requires it for incoming connections. This is often the case when connecting to a managed service.
+
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
-
- If this step fails, you may have to add the CA certificate.
-
+
+ If this step fails, you may have to add the CA certificate.
+
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
- 
- 
+ 
+ 
- When generating these secrets, it's important to specify a Time-to-Live (TTL) duration. This will dictate how long the credentials are valid for.
+ When generating these secrets, it's important to specify a Time-to-Live (TTL) duration. This will dictate how long the credentials are valid for.
- 
+ 
-
- Ensure that the TTL for the lease fall within the maximum TTL defined when configuring the dynamic secret.
-
+
+ Ensure that the TTL for the lease fall within the maximum TTL defined when configuring the dynamic secret.
+
- Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
+
+ 
- 
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the expiration time of the lease or delete a lease before it's set time to live.
## Renew Leases
+
To extend the life of the generated dynamic secret leases past its initial time to live, simply click on the **Renew** button as illustrated below.
- Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret
+ Lease renewals cannot exceed the maximum TTL set when configuring the dynamic
+ secret
diff --git a/docs/documentation/platform/dynamic-secrets/redis.mdx b/docs/documentation/platform/dynamic-secrets/redis.mdx
index 43fbc6b61..b3e585204 100644
--- a/docs/documentation/platform/dynamic-secrets/redis.mdx
+++ b/docs/documentation/platform/dynamic-secrets/redis.mdx
@@ -56,21 +56,29 @@ Create a user with the required permission in your Redis instance. This user wil
- If you want to provide specific privileges for the generated dynamic credentials, you can modify the Redis statement to your needs. This is useful if you want to only give access to a specific table(s).
+ 
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
- 
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
+ If you want to provide specific privileges for the generated dynamic credentials, you can modify the Redis statement to your needs. This is useful if you want to only give access to a specific table(s).
+
- After submitting the form, you will see a dynamic secret created in the dashboard.
+ After submitting the form, you will see a dynamic secret created in the dashboard.
- If this step fails, you may have to add the CA certificate.
+ If this step fails, you may have to add the CA certificate.
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
@@ -85,14 +93,14 @@ Create a user with the required permission in your Redis instance. This user wil
- Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
## Audit or Revoke Leases
-Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
This will allow you to see the expiration time of the lease or delete a lease before it's set time to live.
@@ -103,4 +111,4 @@ To extend the life of the generated dynamic secret leases past its initial time
Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret
-
\ No newline at end of file
+
diff --git a/docs/documentation/platform/dynamic-secrets/sap-ase.mdx b/docs/documentation/platform/dynamic-secrets/sap-ase.mdx
index 3b7a895fb..2737ab084 100644
--- a/docs/documentation/platform/dynamic-secrets/sap-ase.mdx
+++ b/docs/documentation/platform/dynamic-secrets/sap-ase.mdx
@@ -62,21 +62,30 @@ The Infisical SAP ASE dynamic secret allows you to generate SAP ASE database cre
-
- If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs.
+
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
-
- Due to SAP ASE limitations, the attached SQL statements are not executed as a transaction.
-
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
+
+If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs.
+
+Due to SAP ASE limitations, the attached SQL statements are not executed as a transaction.
+
+
After submitting the form, you will see a dynamic secret created in the dashboard.
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
diff --git a/docs/documentation/platform/dynamic-secrets/sap-hana.mdx b/docs/documentation/platform/dynamic-secrets/sap-hana.mdx
index 668777549..597d69803 100644
--- a/docs/documentation/platform/dynamic-secrets/sap-hana.mdx
+++ b/docs/documentation/platform/dynamic-secrets/sap-hana.mdx
@@ -62,14 +62,25 @@ The Infisical SAP HANA dynamic secret allows you to generate SAP HANA database c
-
- If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs.
- 
+
+ 
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
+
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
+
+ If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL statement to your needs.
Due to SAP HANA limitations, the attached SQL statements are not executed as a transaction.
+
+
After submitting the form, you will see a dynamic secret created in the dashboard.
@@ -80,8 +91,8 @@ The Infisical SAP HANA dynamic secret allows you to generate SAP HANA database c
- Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
- To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
+ Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
+ To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
diff --git a/docs/documentation/platform/dynamic-secrets/snowflake.mdx b/docs/documentation/platform/dynamic-secrets/snowflake.mdx
index 75db96c8f..86378bbf6 100644
--- a/docs/documentation/platform/dynamic-secrets/snowflake.mdx
+++ b/docs/documentation/platform/dynamic-secrets/snowflake.mdx
@@ -8,22 +8,27 @@ Infisical's Snowflake dynamic secrets allow you to generate Snowflake user crede
## Snowflake Prerequisites
- Infisical requires a Snowflake user in your account with the USERADMIN role. This user will act as a service account for Infisical and facilitate the creation of new users as needed.
+ Infisical requires a Snowflake user in your account with the USERADMIN role.
+ This user will act as a service account for Infisical and facilitate the
+ creation of new users as needed.
-
- 
-
-
-
- Be sure to uncheck "Force user to change password on first time login"
-
- 
-
-
- 
-
+
+ 
+
+
+
+ Be sure to uncheck "Force user to change password on first time login"
+
+ 
+
+
+ 
+
## Set up Dynamic Secrets with Snowflake
@@ -71,10 +76,23 @@ Infisical's Snowflake dynamic secrets allow you to generate Snowflake user crede
- If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL
- statement to your needs.
-
+
+ Specifies a template for generating usernames. This field allows customization of how usernames are automatically created.
+
+ Allowed template variables are
+ - `{{randomUsername}}`: Random username string
+ - `{{unixTimestamp}}`: Current Unix timestamp
+
+
+
+ If you want to provide specific privileges for the generated dynamic credentials, you can modify the SQL
+ statement to your needs.
+
+
+
+
+
After submitting the form, you will see a dynamic secret created in the dashboard.
@@ -104,6 +122,7 @@ Infisical's Snowflake dynamic secrets allow you to generate Snowflake user crede
+
## Audit or Revoke Leases
@@ -119,6 +138,6 @@ To extend the life of the generated dynamic secret lease past its initial time t
- Lease renewals cannot exceed the maximum TTL set when configuring the dynamic
- secret.
+ Lease renewals cannot exceed the maximum TTL set when configuring the dynamic
+ secret.
diff --git a/docs/images/platform/dynamic-secrets/advanced-option-atlas.png b/docs/images/platform/dynamic-secrets/advanced-option-atlas.png
index 50c9f89bd..5ddf3920e 100644
Binary files a/docs/images/platform/dynamic-secrets/advanced-option-atlas.png and b/docs/images/platform/dynamic-secrets/advanced-option-atlas.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-input-modal-elastic-search.png b/docs/images/platform/dynamic-secrets/dynamic-secret-input-modal-elastic-search.png
index 14d2d48b2..fd7834302 100644
Binary files a/docs/images/platform/dynamic-secrets/dynamic-secret-input-modal-elastic-search.png and b/docs/images/platform/dynamic-secrets/dynamic-secret-input-modal-elastic-search.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-mongodb.png b/docs/images/platform/dynamic-secrets/dynamic-secret-mongodb.png
index d3a804f8f..e978c7d30 100644
Binary files a/docs/images/platform/dynamic-secrets/dynamic-secret-mongodb.png and b/docs/images/platform/dynamic-secrets/dynamic-secret-mongodb.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-setup-modal-aws-iam.png b/docs/images/platform/dynamic-secrets/dynamic-secret-setup-modal-aws-iam.png
index d412109fa..0ba6aa172 100644
Binary files a/docs/images/platform/dynamic-secrets/dynamic-secret-setup-modal-aws-iam.png and b/docs/images/platform/dynamic-secrets/dynamic-secret-setup-modal-aws-iam.png differ
diff --git a/docs/images/platform/dynamic-secrets/modify-cql-statements.png b/docs/images/platform/dynamic-secrets/modify-cql-statements.png
index d1e1b9b98..6bbb44780 100644
Binary files a/docs/images/platform/dynamic-secrets/modify-cql-statements.png and b/docs/images/platform/dynamic-secrets/modify-cql-statements.png differ
diff --git a/docs/images/platform/dynamic-secrets/modify-elasticache-statement.png b/docs/images/platform/dynamic-secrets/modify-elasticache-statement.png
index c8cd662d0..d9675849d 100644
Binary files a/docs/images/platform/dynamic-secrets/modify-elasticache-statement.png and b/docs/images/platform/dynamic-secrets/modify-elasticache-statement.png differ
diff --git a/docs/images/platform/dynamic-secrets/modify-redis-statement.png b/docs/images/platform/dynamic-secrets/modify-redis-statement.png
index c9726f752..d37cf9bd0 100644
Binary files a/docs/images/platform/dynamic-secrets/modify-redis-statement.png and b/docs/images/platform/dynamic-secrets/modify-redis-statement.png differ
diff --git a/docs/images/platform/dynamic-secrets/modify-sap-hana-sql-statements.png b/docs/images/platform/dynamic-secrets/modify-sap-hana-sql-statements.png
index 973fcf731..bfff5baa0 100644
Binary files a/docs/images/platform/dynamic-secrets/modify-sap-hana-sql-statements.png and b/docs/images/platform/dynamic-secrets/modify-sap-hana-sql-statements.png differ
diff --git a/docs/images/platform/dynamic-secrets/modify-sql-statement-mysql.png b/docs/images/platform/dynamic-secrets/modify-sql-statement-mysql.png
index 8ad9fc0e3..312a63d6c 100644
Binary files a/docs/images/platform/dynamic-secrets/modify-sql-statement-mysql.png and b/docs/images/platform/dynamic-secrets/modify-sql-statement-mysql.png differ
diff --git a/docs/images/platform/dynamic-secrets/modify-sql-statement-oracle.png b/docs/images/platform/dynamic-secrets/modify-sql-statement-oracle.png
index 0874aa23d..800ef05b1 100644
Binary files a/docs/images/platform/dynamic-secrets/modify-sql-statement-oracle.png and b/docs/images/platform/dynamic-secrets/modify-sql-statement-oracle.png differ
diff --git a/docs/images/platform/dynamic-secrets/modify-sql-statements-mssql.png b/docs/images/platform/dynamic-secrets/modify-sql-statements-mssql.png
index e399db47d..58c33e655 100644
Binary files a/docs/images/platform/dynamic-secrets/modify-sql-statements-mssql.png and b/docs/images/platform/dynamic-secrets/modify-sql-statements-mssql.png differ
diff --git a/docs/images/platform/dynamic-secrets/modify-sql-statements.png b/docs/images/platform/dynamic-secrets/modify-sql-statements.png
index d0f3b09da..feda34830 100644
Binary files a/docs/images/platform/dynamic-secrets/modify-sql-statements.png and b/docs/images/platform/dynamic-secrets/modify-sql-statements.png differ
diff --git a/docs/images/platform/dynamic-secrets/sap-ase/dynamic-secret-sap-ase-statements.png b/docs/images/platform/dynamic-secrets/sap-ase/dynamic-secret-sap-ase-statements.png
index 9ac56f456..c133505b7 100644
Binary files a/docs/images/platform/dynamic-secrets/sap-ase/dynamic-secret-sap-ase-statements.png and b/docs/images/platform/dynamic-secrets/sap-ase/dynamic-secret-sap-ase-statements.png differ
diff --git a/docs/images/platform/dynamic-secrets/snowflake/dynamic-secret-snowflake-sql-statements.png b/docs/images/platform/dynamic-secrets/snowflake/dynamic-secret-snowflake-sql-statements.png
index 44c41bd52..fc7e9f663 100644
Binary files a/docs/images/platform/dynamic-secrets/snowflake/dynamic-secret-snowflake-sql-statements.png and b/docs/images/platform/dynamic-secrets/snowflake/dynamic-secret-snowflake-sql-statements.png differ