Amazon MQ (AMQP 0.9.1)

Overview

This guide describes how to add an Amazon MQ broker using the AMQP 0.9.1 protocol as a datasource in StrongDM.

When the resource is added, StrongDM proxies client connections through a node (gateway, relay, or proxy cluster). This enables centralized access control, credential management, and audit logging. StrongDM supports standard AMQP 0.9.1 clients and libraries that connect to Amazon MQ brokers.

If you wish to connect over the AMQP 1.0 instead, please see the Amazon MQ AMQP section of the documentation.

To add this datasource, you will need the broker’s hostname, port, and a valid username and password. Optionally, you can store credentials in a supported secrets manager and reference them from StrongDM.

TLS is supported and can be enabled during setup. For cloud-hosted brokers, ensure that security groups or firewall rules permit inbound connections from StrongDM nodes.

Use this guide to complete all necessary preparations to add this resource to your StrongDM environment; input the correct properties in the Admin UI, CLI, SDKs, or Terraform provider; and test for a successful connection. Once setup is complete, you can connect your AMQP 0.9.1 clients to Amazon MQ through StrongDM.

For general information about how to add a database as a resource in StrongDM, see our main guide, Add a Datasource.

Supported Versions and Clients

StrongDM supports Amazon MQ brokers using the AMQP protocol, including Apache ActiveMQ and RabbitMQ engines.

StrongDM is generally compatible with all AMQP clients, such as:

• The amqp Python library

• RabbitMQ clients (pika, amqplib)

• Java AMQP clients

• GUI tools such as RabbitMQ Management or AMQP console apps

StrongDM does not alter the AMQP wire protocol. Any client that supports Amazon MQ’s AMQP endpoint can be proxied through StrongDM.

Prerequisites

Before adding Amazon MQ (AMQP) as a datasource in StrongDM, ensure the following requirements are met.

In StrongDM, you must have the following:

• Administrator permission level

• At least one StrongDM node (gateway, relay, or proxy cluster) deployed in a location that can reach the broker’s host and port (default AMQP ports: 5671 for TLS, 5672 for non-TLS)

• Valid set of Amazon MQ credentials (username and password)

• If using secrets management tools for storing your credentials, a Secret Store configured in StrongDM

To verify that the resource is accessible by the node, log in to the gateway or relay and use Netcat: nc -zv <HOSTNAME> <PORT> (in this example, nc -zv testdb-01.fancy.org 3306). If your gateway server can connect to this hostname, proceed.

Netcat is a tool for checking various hostnames and ports by either sending data (a ping) or checking for listeners on the ports. The command in the aforementioned example use "-z" to check for listeners without sending data and "-v" to show verbose output. If you don't have Netcat, you can install the Netcat package with whatever package manager you are using, such as "apt-get install netcat".

On the AWS side, you must have the following:

• Amazon MQ broker configured with the AMQP protocol enabled

• AWS user account created in Amazon MQ with permissions to connect over AMQP

• Security groups or firewall rules that allow inbound traffic from your StrongDM nodes to the broker

Resource Management in StrongDM

After all prerequisites and prep work is done, you are ready to add the resource to StrongDM. This section provides instructions for adding the resource in either the StrongDM Admin UI, CLI, Terraform provider, or SDKs.

Admin UI

Set up and Manage With the Admin UI

If using the Admin UI to add Amazon MQ as a resource to StrongDM, use the following steps.

1. Log in to the StrongDM Admin UI.

2. Go to Resources > Datasources.

3. Click Add datasource.

4. Select Amazon MQ (AMQP 0.9.1) as the Datasource Type and set other configuration properties for your new resource.

5. Complete all required fields.

6. Click Create to save the resource.

7. Click the resource name to view status, diagnostic information, and setting details.

CLI

Set up and Manage With the CLI

This section provides an example of how to configure and manage the resource using the StrongDM CLI. For more information and examples, please see the CLI Reference documentation.

# Add Amazon MQ (AMQP 0.9.1) datasource
sdm admin datasources add amazonmqamqp091 my-mq-rabbit
  --hostname="b-12345678-1234.mq.us-west-2.amazonaws.com"
  --port=5671
  --username="mq_user"
  --password="secret"
  --tls-required
  --bind-interface="127.0.0.1"
  --egress-filter="tag:env=prod"
  --port-override="-1"
  --proxy-cluster-id="n-1a2b345c67890123"
  --secret-store-id="se-e1b2"
  --subdomain="mq-rabbit-prod"
  --tags="env=production,team=messaging"

# Clone Amazon MQ (AMQP 0.9.1) datasource
# Specify the ID of the resource to clone and give it a new name
sdm admin datasources clone rs-12a3456789b012cd --name "mq-rabbit-clone"

# Update Amazon MQ (AMQP 0.9.1) datasource
# Specify the ID of the resource to update and change some options
sdm admin datasources update rs-12a3456789b012cd \
  --port 1234 \
  --tags "env=staging,team=search"

# Delete Amazon MQ datasource
# Specify the ID of the resource to delete
sdm admin datasources delete rs-12a3456789b012cd

Terraform

Set up and Manage With Terraform

This section provides an example of how to configure and manage the resource using the Terraform provider. For more information and examples, please see the Terraform provider documentation.

# Install StrongDM provider
terraform {
  required_providers {
    sdm = {
      source  = "strongdm/sdm"
      version = "5.1.0"
    }
  }
}

# Configure StrongDM provider
provider "sdm" {
  # Add API access key and secret key from Admin UI
  api_access_key = "njjSn...5hM"
  api_secret_key = "ziG...="
}

# Create Amazon MQ AMQP 0.9.1 resource
resource "sdm_amazonmqamqp091" "mq_prod" {
  name             = "mq-rabbit-prod"
  hostname         = "b-12345678-1234.mq.us-west-2.amazonaws.com"
  port             = 5671
  username         = "mq_user"
  password         = "secret"

  tls_required     = true
  bind_interface   = "127.0.0.1"
  egress_filter    = "tag:env=prod"
  port_override    = 12345
  proxy_cluster_id = "n-1a2b345c67890123"
  secret_store_id  = "se-e1b2"
  subdomain        = "mq-rabbit-prod"
  tags = {
    env  = "production"
    team = "messaging"
  }
}

# Clone Amazon MQ AMQP 0.9.1 resource
resource "sdm_amazonmqamqp091" "mq_clone" {
  name             = "mq-rabbit-clone"
  hostname         = sdm_amazonmqamqp091.mq_prod.hostname
  port             = sdm_amazonmqamqp091.mq_prod.port
  username         = sdm_amazonmqamqp091.mq_prod.username
  password         = sdm_amazonmqamqp091.mq_prod.password

  tls_required     = sdm_amazonmqamqp091.mq_prod.tls_required
  bind_interface   = sdm_amazonmqamqp091.mq_prod.bind_interface
  egress_filter    = sdm_amazonmqamqp091.mq_prod.egress_filter
  port_override    = sdm_amazonmqamqp091.mq_prod.port_override
  proxy_cluster_id = sdm_amazonmqamqp091.mq_prod.proxy_cluster_id
  secret_store_id  = sdm_amazonmqamqp091.mq_prod.secret_store_id
  subdomain        = "mq-rabbit-clone" # give the clone a distinct subdomain
  tags             = sdm_amazonmqamqp091.mq_prod.tags
}

# Update Amazon MQ AMQP 0.9.1 resource
# Updates in Terraform are applied by changing arguments in the same resource
# and re-running `terraform apply`. For illustration, here we change port,
# egress_filter, and tags.

resource "sdm_amazonmqamqp091" "mq_prod_updated" {
  name             = "mq-rabbit-prod"
  hostname         = "b-12345678-1234.mq.us-west-2.amazonaws.com"
  port             = 5672                   # updated port (non-TLS)
  username         = "mq_user"
  password         = "secret"

  tls_required     = false                  # updated to disable TLS
  bind_interface   = "127.0.0.1"
  egress_filter    = "tag:env=staging"      # updated egress filter
  port_override    = 15432                  # updated override
  proxy_cluster_id = "n-1a2b345c67890123"
  secret_store_id  = "se-e1b2"
  subdomain        = "mq-rabbit-prod"
  tags = {
    env  = "staging"                        # updated tag
    team = "messaging"
  }
}

SDKs

Set up and manage with SDKs

In addition to the Admin UI, CLI, and Terraform, you may configure and manage your resource with any of the following SDK options: Go, Java, Python, and Ruby. Please see the following references for more information and examples.

Language	Reference	GitHub	Examples
Go	pkg.go.dev	strongdm-sdk-go	Go SDK Examples
Java	javadoc	strongdm-sdk-java	Java SDK Examples
Python	pdocs	strongdm-sdk-python	Python SDK Examples
Ruby	RubyDoc	strongdm-sdk-ruby	Ruby SDK Examples

Configuration Properties

The following configuration properties are required to define an Amazon Elasticsearch datasource in StrongDM. These settings control how StrongDM connects to the resource, authenticates the connection, and optionally uses encryption or secret management. Each property must be correctly configured to ensure connectivity and access enforcement through StrongDM.

Property	Requirement	Description
Display Name	Required	Meaningful name to display the resource throughout StrongDM; exclude special characters like quotes (") or angle brackets (< or >)
Datasource Type	Required	Amazon MQ (AMQP 0.9.1)
Proxy Cluster	Required	Defaults to "None (use gateways)"; if using proxy clusters, select the appropriate cluster to proxy traffic to this resource
Hostname	Required	Hostname for your resource; must be accessible to a gateway or relay
Port	Required	Port to connect to the service; use port 5671 for TLS; use port 5672 for non-TLS; default port value is 5671
Connectivity Mode	Required	Select either Virtual Networking Mode, which lets users connect to the resource with a software-defined, IP-based network; or Loopback Mode, which allows users to connect to the resource using the local loopback adapter in their operating system; this field is shown if Virtual Networking Mode enabled for your organization
IP Address	Optional	If Virtual Networking Mode is the selected connectivity mode, an IP address value in the configured Virtual Networking Mode subnet in the organization network settings; if Loopback Mode is the selected connectivity mode, an IP address value in the configured Loopback IP range in the organization network settings (by default, 127.0.0.1); if not specified, an available IP address in the configured IP address space for the selected connectivity mode will be automatically assigned; this field is shown if Virtual Networking Mode and/or multi-loopback mode is enabled for your organization
Port Override	Optional	If Virtual Networking Mode is the selected connectivity mode, a port value between 1 and 65535 that is not already in use by another resource with the same IP address; if Loopback Mode is the selected connectivity mode, a port value between 1024 to 64999 that is not already in use by another resource with the same IP address; when left empty with Virtual Networking Mode, the system assigns the default port to this resource; when left empty for Loopback Mode, an available port that is not already in use by another resource is assigned; preferred port also can be modified later from the Port Overrides settings
DNS	Optional	If Virtual Networking Mode is the selected connectivity mode, a unique hostname alias for this resource; when set, causes the desktop app to display this resource's human-readable DNS name (for example, k8s.my-organization-name) instead of the bind address that includes IP address and port (for example, 100.64.100.100:5432)
Secret Store	Optional	Credential store location; defaults to Strong Vault; learn more about Secret Store options
Username	Required	Username to utilize when connecting to this datasource; displays when Secret Store integration is not configured for your organization or when StrongDM serves as the Secret Store type
Password	Required	Password for the user connecting to this datasource; displays when Secret Store integration is not configured for your organization or when StrongDM serves as the Secret Store type
Username (path)	Required	Path to the secret in your Secret Store location (for example, path/to/credential?key=optionalKeyName where key argument is optional); required when using a non-StrongDM Secret Store type
Password (path)	Required	Path to the secret in your Secret Store location (for example, path/to/credential?key=optionalKeyName where key argument is optional); required when using a non-StrongDM Secret Store type
TLS Required	Optional	When selected, requires TLS for connections to this resource
Resource Tags	Optional	Datasource Tags consisting of key-value pairs <KEY>=<VALUE> (for example, env=dev)

Secret Store options

By default, datasource credentials are stored in StrongDM. However, these credentials can also be saved in a secrets management tool.

Non-StrongDM options appear in the Secret Store dropdown if they are created under Settings > Secrets Management. When you select another Secret Store type, its unique properties display. For more details, see Configure Secret Store Integrations.

Resource status

After a resource is created, the Admin UI displays that resource as unhealthy until the health checks run successfully. When the resource is ready, the Health icon indicates a positive, green status.

When the resource does not display a positive status, click the resource name to go to the Diagnostics tab and check for errors.

Test the Connection

After you have added your resource in StrongDM, follow these steps to verify that it’s working correctly.

1. Assign yourself access by ensuring that your user or role has access to the resource. In the StrongDM Admin UI, go to Access > Roles, and ensure that your user or role is assigned to the Amazon MQ AMQP 0.9.1 resource.

2. In the CLI, run sdm status to list the available datasources. Ensure that the Amazon MQ AMQP 0.9.1 resource appears in your list of accessible datasources.

3. Connect through StrongDM, as in the following example:

   sdm connect mq-rabbit-prod

   See the CLI Reference documentation for details on sdm connect.

4. Use your AMQP 0.9.1 client to connect and send a basic message. For example, using Python with pika:

   import pika
   connection = pika.BlockingConnection(pika.ConnectionParameters(
       host="mq-rabbit-prod.<ORG>.sdm.network",
       port=5671,
       ssl=True,
       credentials=pika.PlainCredentials("mq_user", "secret")
   ))
   channel = connection.channel()
   channel.queue_declare(queue="test")
   channel.basic_publish(exchange="", routing_key="test", body="hello world")
   print("Sent message")
   connection.close()

5. In the StrongDM Admin UI, check Logs > Queries (and Logs > Connections) to confirm your session and commands are recorded.

6. If you set TLS required on the resource, confirm that the connection negotiates TLS successfully.

When these steps succeed, you’re ready to connect to your resource through StrongDM.

Help

If you encounter issues, please consult the StrongDM Help Center.

Be prepared to provide the following information to StrongDM Support, so that they can inspect logs and confirm node and resource health:

• Resource name or ID

• CLI error output or logs

• Node name and region

• Timestamps of failed attempts