diff --git a/docs/documentation/platform/dynamic-secrets/rabbit-mq.mdx b/docs/documentation/platform/dynamic-secrets/rabbit-mq.mdx
new file mode 100644
index 000000000..f8649b727
--- /dev/null
+++ b/docs/documentation/platform/dynamic-secrets/rabbit-mq.mdx
@@ -0,0 +1,116 @@
+---
+title: "RabbitMQ"
+description: "Learn how to dynamically generate RabbitMQ user credentials."
+---
+
+The Infisical RabbitMQ dynamic secret allows you to generate RabbitMQ credentials on demand based on configured role.
+
+## Prerequisites
+
+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
+
+
+
+ Open the Secret Overview dashboard and select the environment in which you would like to add a dynamic secret.
+
+
+ 
+
+
+ 
+
+
+
+ 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 when a secret is generate)
+
+
+
+ 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 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 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.
+
+
+ 
+
+
+
+
+ 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.
+
+
+
+
+ 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.
+
+ 
+
+
+ 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.
+
+ 
+
+
+
+## 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.
+This will allow you 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** as illustrated below.
+
+
+
+ Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret
+
diff --git a/docs/mint.json b/docs/mint.json
index c26245def..5528a22de 100644
--- a/docs/mint.json
+++ b/docs/mint.json
@@ -165,6 +165,7 @@
"documentation/platform/dynamic-secrets/redis",
"documentation/platform/dynamic-secrets/aws-elasticache",
"documentation/platform/dynamic-secrets/elastic-search",
+ "documentation/platform/dynamic-secrets/rabbit-mq",
"documentation/platform/dynamic-secrets/aws-iam",
"documentation/platform/dynamic-secrets/mongo-atlas",
"documentation/platform/dynamic-secrets/mongo-db"