RabbitMQ secrets engine (API)

This is the API documentation for the Vault RabbitMQ secrets engine. For general information about the usage and operation of the RabbitMQ secrets engine, please see the RabbitMQ documentation.

This documentation assumes the RabbitMQ secrets engine is enabled at the /rabbitmq path in Vault. Since it is possible to enable secrets engines at any location, please update your API calls accordingly.

Configure connection

This endpoint configures the connection string used to communicate with RabbitMQ.

Method	Path
POST	/rabbitmq/config/connection

Parameters

• connection_uri (string: <required>) – Specifies the RabbitMQ connection URI.

• username (string: <required>) – Specifies the RabbitMQ management administrator username.

• password (string: <required>) – Specifies the RabbitMQ management administrator password.

• verify_connection (bool: true) – Specifies whether to verify connection URI, username, and password.

• password_policy (string: "") - Specifies a password policy to use when creating dynamic credentials. Defaults to generating an alphanumeric password if not set.

• username_template (string) - Template describing how dynamic usernames are generated.

Sample payload

{
  "connection_uri": "https://...",
  "username": "user",
  "password": "password",
  "password_policy": "rabbitmq_policy"
}

Sample request

$ curl \
    --header "X-Vault-Token: ..." \
    --request POST \
    --data @payload.json \
    http://127.0.0.1:8200/v1/rabbitmq/config/connection

Configure lease

This endpoint configures the lease settings for generated credentials.

Method	Path
POST	/rabbitmq/config/lease

Parameters

• ttl (int: 0) – Specifies the lease ttl provided in seconds.

• max_ttl (int: 0) – Specifies the maximum ttl provided in seconds.

Sample payload

{
  "ttl": 1800,
  "max_ttl": 3600
}

Sample request

$ curl \
    --header "X-Vault-Token: ..." \
    --request POST \
    --data @payload.json \
    http://127.0.0.1:8200/v1/rabbitmq/config/lease

Create role

This endpoint creates or updates the role definition.

Method	Path
POST	/rabbitmq/roles/:name

Parameters

• name (string: <required>) – Specifies the name of the role to create. This is specified as part of the URL.

• tags (string: "") – Specifies a comma-separated RabbitMQ management tags.

• vhosts (string: "") – Specifies a map of virtual hosts to permissions.

• vhost_topics (string: "") – Specifies a map of virtual hosts and exchanges to topic permissions. This option requires RabbitMQ 3.7.0 or later.

Sample payload

{
  "tags": "tag1,tag2",
  "vhosts": "{\"/\": {\"configure\":\".*\", \"write\":\".*\", \"read\": \".*\"}}",
  "vhost_topics": "{\"/\": {\"amq.topic\": {\"write\":\".*\", \"read\": \".*\"}}}"
}

Sample request

$ curl \
    --header "X-Vault-Token: ..." \
    --request POST \
    --data @payload.json \
    http://127.0.0.1:8200/v1/rabbitmq/roles/my-role

Read role

This endpoint queries the role definition.

Method	Path
GET	/rabbitmq/roles/:name

Parameters

• name (string: <required>) – Specifies the name of the role to read. This is specified as part of the URL.

Sample request

$ curl \
    --header "X-Vault-Token: ..." \
    http://127.0.0.1:8200/v1/rabbitmq/roles/my-role

Sample response

{
  "data": {
    "tags": "",
    "vhosts": "{\"/\": {\"configure\":\".*\", \"write\":\".*\", \"read\": \".*\"}}",
    "vhost_topics": "{\"/\": {\"amq.topic\": {\"write\":\".*\", \"read\": \".*\"}}}"
  }
}

Delete role

This endpoint deletes the role definition.

Method	Path
DELETE	/rabbitmq/roles/:name

Parameters

• name (string: <required>) – Specifies the name of the role to delete. This is specified as part of the URL.

Sample request

$ curl \
    --header "X-Vault-Token: ..." \
    --request DELETE \
    http://127.0.0.1:8200/v1/rabbitmq/roles/my-role

Generate credentials

This endpoint generates a new set of dynamic credentials based on the named role.

Method	Path
GET	/rabbitmq/creds/:name

Parameters

• name (string: <required>) – Specifies the name of the role to create credentials against. This is specified as part of the URL.

Sample request

$ curl \
    --header "X-Vault-Token: ..." \
    http://127.0.0.1:8200/v1/rabbitmq/creds/my-role

Sample response

{
  "data": {
    "username": "root-4b95bf47-281d-dcb5-8a60-9594f8056092",
    "password": "e1b6c159-ca63-4c6a-3886-6639eae06c30"
  }
}