Close
logodocs

RabbitMQ

To add RabbitMQ as a Datasource in the Admin UI, set the following configuration properties. For more information, see our main guide, Add a Datasource.

The only supported RabbitMQ protocol for connections through strongDM is the AMQP 0.9.1 model. Feel free to email support with any questions.

Configuration Properties

Add RabbitMQ Datasource Dialog
Add RabbitMQ Datasource Dialog
  • Display Name (Required): Enter a meaningful name for this resource, such as "rabbitmq." This name displays throughout strongDM. Do not include special characters like quotes (") or angle brackets (< or >).
  • Datasource Type (Required): Select RabbitMQ (AMQP 0.9.1).
  • Hostname (Required): Enter the hostname. Note that it must be accessible to a Gateway or Relay. Do not include the protocol (ampq://) or port.
  • Port (Required): Enter the port to connect to the service (default: 5672).
  • Port Override: After this Datasource has been created, this field will be automatically filled with a port between 1024-59999 that is not in use by another Datasource. You can optionally overwrite it with your own preferred port later in the Port Overrides settings.
  • Secret Store: This field lets you specify where the credentials for this Resource are stored (i.e., strongDM, AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, HashiCorp Vault, etc.). This field is only displayed if Secret Store integration is configured in the Admin UI. The default Secret Store type is strongDM. Selecting any other Secret Store type causes properties unique to that Secret Store to appear, such as Username (path), Password (path), and so forth. For more detailed information about path to the secrets you've stored in a particular Secret Store, see the Secret Store integration configuration guide for the one you are using.
  • Username (Required): This field is shown when Secret Store integration is not configured for your organization, or when it is and strongDM is the selected Secret Store type. Enter the username of the user that will be used for this Datasource.
  • Username (path) (Required): If Secret Store integration is configured for your organization and you selected a Secret Store type that is not strongDM, enter the path to the secret in your Secret Store (e.g., path/to/credential?key=optionalKeyName). The key argument is optional.
  • Password (Required): This field is shown when Secret Store integration is not configured for your organization, or when it is and strongDM is the selected Secret Store type. Enter the password of the user that will be used for this Datasource.
  • Password (path) (Required): If Secret Store integration is configured for your organization and you selected a Secret Store type that is not strongDM, enter the path to the secret in your Secret Store (e.g., path/to/credential?key=optionalKeyName). The key argument is optional.
  • TLS Required? (Optional): If your RabbitMQ configuration requires TLS, you can select this checkbox to enable strongDM to use a TLS connection.
  • Resource Tags (Optional): Assign tags to the Datasource by entering key-value pairs in the format <KEY>=<VALUE> (e.g., env=dev).

If the MIME Content Type of a given RabbitMQ message body is not text/plain or application/json, but is instead some form of binary data, strongDM does not log that message body. Binary data could be anything in any format, and strongDM would be unable to ascertain what it was or know how to display it in log records.

If any errors occur, please copy them into an email and send them to support@strongdm.com.

Previous
Presto
Next
Redis