> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon MQ RabbitMQ Single

> Amazon MQ RabbitMQ Single APIs with Cloud Adapter.

This page describes how Amazon MQ RabbitMQ Single maps to services in the environment where the application runs, including backend choices, supported operations and service-specific behavior.

## Supported environments

* Akamai
* Azure
* DigitalOcean
* Google Cloud
* OCI
* Private Kubernetes
* Scaleway

Check the operation and capability tables for the behavior your application depends on. A supported environment does not imply that every operation of the origin service is available.

## How the backends compare

Each row compares a capability of Amazon MQ RabbitMQ Single with its adaptation on each backend.
A dash means this profile does not state the capability for that backend.

### Cloud Adapter

| Capability | Amazon MQ RabbitMQ Single | Akamai, Azure, DigitalOcean, Google Cloud, OCI, Private Kubernetes, and Scaleway |
| - | - | - |
| AMQP protocol | AMQP 0-9-1 (RabbitMQ) | native; same broker engine, client unchanged |
| Broker topology | single-instance | single node |
| High availability | none; Amazon MQ single-instance is non-HA | none (single node; size the cluster topology for HA) |
| Managed broker | Yes | No - you self-manage the broker on Kubernetes |
| Management API + UI | Yes | Yes - RabbitMQ management plugin (console URL differs) |
| TLS | Yes | Yes - self-signed / cert-manager issuer (trust chain differs from AWS-managed) |
| API coverage | full | high |

## On Akamai, Azure, DigitalOcean, Google Cloud, OCI, Private Kubernetes, and Scaleway

### Bitnami RabbitMQ

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| CloudWatch logs / KMS / maintenance window / VPC placement / minor-version upgrade | AWS control plane | Out of scope | Full surface | these AWS-managed settings are omitted. Configure logging, monitoring, encryption at rest and upgrades with the target cluster's tools |
| Management API + UI | Admin | Supported | Most usage | the RabbitMQ management plugin is enabled (the same HTTP API Amazon MQ exposes on 443/15671); the management console URL differs from Amazon MQ's |
| Plugins (Shovel / Federation / Consistent-Hash / Prometheus / OAuth2) | Admin | Supported | Most usage | because you operate the broker, you can enable any RabbitMQ plugin, a wider set than Amazon MQ's curated list (Management, dynamic Shovel, Federation, Consistent-Hash-Exchange, OAuth2, LDAP, Prometheus). Amazon MQ's private-broker Shovel/Federation restriction does not apply on the target cluster |
| Consumer acks / QoS prefetch | Delivery | Supported | Most usage | RabbitMQ handles acknowledgements and prefetch directly; consumer\_timeout sets the delivery acknowledgement timeout |
| Dead-letter exchanges / TTL | Delivery | Supported | Most usage | native RabbitMQ dead-letter exchanges and message/queue TTL |
| Publisher confirms | Delivery | Supported | Most usage | native RabbitMQ publisher confirms |
| Transactions (Tx.Select / Tx.Commit / Tx.Rollback) | Delivery | Supported | Full surface | native AMQP 0-9-1 transactions on the same broker engine; publisher confirms are the recommended higher-throughput path |
| ActiveMQ engine | Engine | Out of scope | Full surface | Amazon MQ's ActiveMQ engine is a different protocol and is out of scope; only RabbitMQ is supported |
| Bindings + routing keys | Messaging | Supported | Common | native RabbitMQ routing, unchanged |
| Exchanges (direct / fanout / topic / headers) | Messaging | Supported | Common | native RabbitMQ; every exchange type works unchanged |
| Queues (classic / quorum / lazy) | Messaging | Supported | Common | RabbitMQ queue types run on one node; replication across nodes requires a cluster |
| Streams (RabbitMQ 3.9+) | Messaging | Out of scope | Full surface | Streams are not part of this mapping: Amazon MQ for RabbitMQ does not offer them, and Tensor9 does not configure them. The target broker runs the RabbitMQ engine, so you can declare stream queues over AMQP 0-9-1 yourself. The dedicated RabbitMQ Stream protocol also needs its plugin, a listener and a compatible client, which you must enable and validate. |
| Authentication (authentication\_strategy=SIMPLE) | Security | Supported | Most usage | SIMPLE is the default strategy. The broker's declared user block (username/password) is written into a Kubernetes secret, and RabbitMQ's internal user backend authenticates against it unchanged |
| LDAP authentication | Security | Partial | Full surface | RabbitMQ's LDAP auth-backend plugin (rabbitmq\_auth\_backend\_ldap) is available on the self-operated broker; enable it and point it at your directory. Configure the LDAP server connection on RabbitMQ directly |
| TLS | Security | Supported | Most usage | TLS is on (Amazon MQ RabbitMQ is always-TLS); the certificate is self-signed or cert-manager-issued rather than AWS-managed, so the trust chain differs. Pin or trust the cluster's issuer |
| Connect (AMQP 0-9-1) | Wire protocol | Supported | Common | your AMQP client (pika, amqplib, the RabbitMQ Java client) connects without changes. Bitnami RabbitMQ runs the same broker engine as Amazon MQ, so the protocol is native; Tensor9 writes the backend broker endpoint into the generated Amazon MQ resource outputs |

#### How it works

Tensor9 deploys the Bitnami RabbitMQ Helm chart on your Kubernetes cluster and puts the broker's host and port in the generated Amazon MQ outputs. Your application connects straight to that broker over AMQP 0-9-1 and keeps its RabbitMQ client library; Tensor9 is not in the message path. Clients that pin the AWS certificate chain must trust the new broker's certificate issuer instead.

The deployment has 1 broker pod, persistent storage and a Kubernetes Service. Your platform team operates the broker, storage, upgrades and recovery. A disconnected deployment also needs the container images, chart, certificates and other dependencies available locally.

#### Queues and broker configuration

Exchanges, bindings, routing keys, publisher confirms, transactions, consumer acknowledgments, prefetch, dead-letter exchanges and TTL work as they do on Amazon MQ, because the broker is RabbitMQ. When you import definitions, check queue types and enabled plugins against the broker version.

Declare quorum queues explicitly, or set the broker's default queue type. RabbitMQ defaults to classic queues unless you change that default; running RabbitMQ 4.x alone does not select quorum queues. The management HTTP API and console show broker definitions and state.

Set broker settings, credentials, TLS and plugins through the Helm chart's values. This mapping does not need a RabbitmqCluster custom resource or the RabbitMQ Cluster Operator.

#### Single-node deployment and recovery

This deployment runs one broker pod. Its persistent volume keeps messages when the pod is replaced, but no second broker takes client connections while it is down. A quorum queue with one member is unavailable when its only node fails. Use the clustered mapping if your application needs broker failover.

Size each persistent volume for the backlog you keep and your recovery needs. Storage availability and backups are separate from broker replication: a replicated queue does not protect against deletion or a wrong retention policy.

![The Bitnami RabbitMQ Helm chart deploys 1 broker pod with a persistent volume. There is no second broker or replicated queue member to take over.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjAyIiB2aWV3Qm94PSIwIDAgODM2IDIwMiIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJUaGUgQml0bmFtaSBSYWJiaXRNUSBIZWxtIGNoYXJ0IGRlcGxveXMgMSBicm9rZXIgcG9kIHdpdGggYSBwZXJzaXN0ZW50IHZvbHVtZS4gVGhlcmUgaXMgbm8gc2Vjb25kIGJyb2tlciBvciByZXBsaWNhdGVkIHF1ZXVlIG1lbWJlciB0byB0YWtlIG92ZXIuIj48c3R5bGU+dGV4dHtmb250LWZhbWlseTpJbnRlciwtYXBwbGUtc3lzdGVtLEJsaW5rTWFjU3lzdGVtRm9udCwnU2Vnb2UgVUknLFJvYm90bywnSGVsdmV0aWNhIE5ldWUnLEFyaWFsLHNhbnMtc2VyaWY7ZmlsbDojMzM0MTU1fTwvc3R5bGU+CiAgICAgICAgICAgICAgICA8ZGVmcz48bWFya2VyIGlkPSJybXEtay1oZWxtIiB2aWV3Qm94PSIwIDAgMTAgMTAiIHJlZlg9IjgiIHJlZlk9IjUiIG1hcmtlcldpZHRoPSI3IiBtYXJrZXJIZWlnaHQ9IjciIG9yaWVudD0iYXV0by1zdGFydC1yZXZlcnNlIj48cGF0aCBkPSJNMCwwIEwxMCw1IEwwLDEwIHoiIHN0eWxlPSJmaWxsOiM5NGEzYjgiLz48L21hcmtlcj48L2RlZnM+CiAgICAgICAgICAgICAgICA8dGV4dCB4PSIyNCIgeT0iMjQiIHN0eWxlPSJmb250OiA3MDAgMTBweCBJbnRlciwgc2Fucy1zZXJpZjsgbGV0dGVyLXNwYWNpbmc6IDEuM3B4OyBmaWxsOiAjOTRhM2I4Ij5IRUxNIENPTkZJR1VSQVRJT048L3RleHQ+CiAgICAgICAgICAgICAgICA8dGV4dCB4PSIzMjIiIHk9IjI0IiBzdHlsZT0iZm9udDogNzAwIDEwcHggSW50ZXIsIHNhbnMtc2VyaWY7IGxldHRlci1zcGFjaW5nOiAxLjNweDsgZmlsbDogIzk0YTNiOCI+S1VCRVJORVRFUyBTVEFURUZVTFNFVDwvdGV4dD4KICAgICAgICAgICAgICAgIDxyZWN0IHg9IjI0IiB5PSI0NiIgd2lkdGg9IjI1MCIgaGVpZ2h0PSIxMjgiIHJ4PSIxMSIgc3Ryb2tlLXdpZHRoPSIxLjUiIHN0eWxlPSJmaWxsOiNmZmZmZmY7c3Ryb2tlOiNjYmQ1ZTEiLz4KPHRleHQgeD0iMTQ5IiB5PSI5MSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDY1MCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwZjE3MmE7IGZvbnQtc2l6ZToxMnB4Ij5CaXRuYW1pIFJhYmJpdE1RPC90ZXh0Pgo8dGV4dCB4PSIxNDkiIHk9IjEwNyIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDExcHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2NDc0OGIiPnJlcGxpY2FDb3VudDogMTwvdGV4dD4KPHRleHQgeD0iMTQ5IiB5PSIxMjMiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5wZXJzaXN0ZW50IHN0b3JhZ2U8L3RleHQ+Cjx0ZXh0IHg9IjE0OSIgeT0iMTM5IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogMTFweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzY0NzQ4YiI+Y3JlZGVudGlhbHMgKyBUTFM8L3RleHQ+CiAgICAgICAgICAgICAgICA8bGluZSB4MT0iMjc4IiB5MT0iMTEwIiB4Mj0iMzA4IiB5Mj0iMTEwIiBzdHJva2Utd2lkdGg9IjIiIG1hcmtlci1lbmQ9InVybCgjcm1xLWstaGVsbSkiIHN0eWxlPSJzdHJva2U6Izk0YTNiOCIvPgogICAgICAgICAgICAgICAgPHJlY3QgeD0iMzEyIiB5PSIzNiIgd2lkdGg9IjUwMCIgaGVpZ2h0PSIxNDIiIHJ4PSIxMiIgc3Ryb2tlLXdpZHRoPSIxLjYiIHN0eWxlPSJmaWxsOiNlY2ZkZjU7c3Ryb2tlOiMwNDc4NTciLz4KICAgICAgICAgICAgICAgIDx0ZXh0IHg9IjU2MiIgeT0iNjYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwNDc4NTciPlNlcnZpY2U6IEFNUVBTIDU2NzEgwrcgbWFuYWdlbWVudCAxNTY3MTwvdGV4dD4KICAgICAgICAgICAgICAgIDxyZWN0IHg9IjQ1MCIgeT0iODgiIHdpZHRoPSIyMjIiIGhlaWdodD0iNTgiIHJ4PSIxMSIgc3Ryb2tlLXdpZHRoPSIxLjUiIHN0eWxlPSJmaWxsOiNmZmZmZmY7c3Ryb2tlOiNjYmQ1ZTEiLz4KPHRleHQgeD0iNTYxIiB5PSIxMTQiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA2NTAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjMGYxNzJhOyBmb250LXNpemU6MTJweCI+cmFiYml0LTA8L3RleHQ+Cjx0ZXh0IHg9IjU2MSIgeT0iMTMwIiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogMTFweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzY0NzQ4YiI+YnJva2VyICsgdm9sdW1lPC90ZXh0PgogICAgICAgICAgICAgICAgPHRleHQgeD0iNTYyIiB5PSIxNjYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwNDc4NTciPk9uZSBicm9rZXI6IG5vIHJlcGxpY2EgdG8gdGFrZSBvdmVyPC90ZXh0PgogICAgICAgICAgICAgICAgPC9zdmc+)

![The Bitnami RabbitMQ Helm chart deploys 1 broker pod with a persistent volume. There is no second broker or replicated queue member to take over.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjAyIiB2aWV3Qm94PSIwIDAgODM2IDIwMiIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJUaGUgQml0bmFtaSBSYWJiaXRNUSBIZWxtIGNoYXJ0IGRlcGxveXMgMSBicm9rZXIgcG9kIHdpdGggYSBwZXJzaXN0ZW50IHZvbHVtZS4gVGhlcmUgaXMgbm8gc2Vjb25kIGJyb2tlciBvciByZXBsaWNhdGVkIHF1ZXVlIG1lbWJlciB0byB0YWtlIG92ZXIuIj48c3R5bGU+dGV4dHtmb250LWZhbWlseTpJbnRlciwtYXBwbGUtc3lzdGVtLEJsaW5rTWFjU3lzdGVtRm9udCwnU2Vnb2UgVUknLFJvYm90bywnSGVsdmV0aWNhIE5ldWUnLEFyaWFsLHNhbnMtc2VyaWY7ZmlsbDojY2JkNWUxfTwvc3R5bGU+CiAgICAgICAgICAgICAgICA8ZGVmcz48bWFya2VyIGlkPSJybXEtay1oZWxtIiB2aWV3Qm94PSIwIDAgMTAgMTAiIHJlZlg9IjgiIHJlZlk9IjUiIG1hcmtlcldpZHRoPSI3IiBtYXJrZXJIZWlnaHQ9IjciIG9yaWVudD0iYXV0by1zdGFydC1yZXZlcnNlIj48cGF0aCBkPSJNMCwwIEwxMCw1IEwwLDEwIHoiIHN0eWxlPSJmaWxsOiM2NDc0OGIiLz48L21hcmtlcj48L2RlZnM+CiAgICAgICAgICAgICAgICA8dGV4dCB4PSIyNCIgeT0iMjQiIHN0eWxlPSJmb250OiA3MDAgMTBweCBJbnRlciwgc2Fucy1zZXJpZjsgbGV0dGVyLXNwYWNpbmc6IDEuM3B4OyBmaWxsOiAjNjQ3NDhiIj5IRUxNIENPTkZJR1VSQVRJT048L3RleHQ+CiAgICAgICAgICAgICAgICA8dGV4dCB4PSIzMjIiIHk9IjI0IiBzdHlsZT0iZm9udDogNzAwIDEwcHggSW50ZXIsIHNhbnMtc2VyaWY7IGxldHRlci1zcGFjaW5nOiAxLjNweDsgZmlsbDogIzY0NzQ4YiI+S1VCRVJORVRFUyBTVEFURUZVTFNFVDwvdGV4dD4KICAgICAgICAgICAgICAgIDxyZWN0IHg9IjI0IiB5PSI0NiIgd2lkdGg9IjI1MCIgaGVpZ2h0PSIxMjgiIHJ4PSIxMSIgc3Ryb2tlLXdpZHRoPSIxLjUiIHN0eWxlPSJmaWxsOiMxZTI5M2I7c3Ryb2tlOiM0NzU1NjkiLz4KPHRleHQgeD0iMTQ5IiB5PSI5MSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDY1MCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICNmMWY1Zjk7IGZvbnQtc2l6ZToxMnB4Ij5CaXRuYW1pIFJhYmJpdE1RPC90ZXh0Pgo8dGV4dCB4PSIxNDkiIHk9IjEwNyIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDExcHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM5NGEzYjgiPnJlcGxpY2FDb3VudDogMTwvdGV4dD4KPHRleHQgeD0iMTQ5IiB5PSIxMjMiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5wZXJzaXN0ZW50IHN0b3JhZ2U8L3RleHQ+Cjx0ZXh0IHg9IjE0OSIgeT0iMTM5IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogMTFweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzk0YTNiOCI+Y3JlZGVudGlhbHMgKyBUTFM8L3RleHQ+CiAgICAgICAgICAgICAgICA8bGluZSB4MT0iMjc4IiB5MT0iMTEwIiB4Mj0iMzA4IiB5Mj0iMTEwIiBzdHJva2Utd2lkdGg9IjIiIG1hcmtlci1lbmQ9InVybCgjcm1xLWstaGVsbSkiIHN0eWxlPSJzdHJva2U6IzY0NzQ4YiIvPgogICAgICAgICAgICAgICAgPHJlY3QgeD0iMzEyIiB5PSIzNiIgd2lkdGg9IjUwMCIgaGVpZ2h0PSIxNDIiIHJ4PSIxMiIgc3Ryb2tlLXdpZHRoPSIxLjYiIHN0eWxlPSJmaWxsOiMwNjRlM2I7c3Ryb2tlOiM2ZWU3YjciLz4KICAgICAgICAgICAgICAgIDx0ZXh0IHg9IjU2MiIgeT0iNjYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2ZWU3YjciPlNlcnZpY2U6IEFNUVBTIDU2NzEgwrcgbWFuYWdlbWVudCAxNTY3MTwvdGV4dD4KICAgICAgICAgICAgICAgIDxyZWN0IHg9IjQ1MCIgeT0iODgiIHdpZHRoPSIyMjIiIGhlaWdodD0iNTgiIHJ4PSIxMSIgc3Ryb2tlLXdpZHRoPSIxLjUiIHN0eWxlPSJmaWxsOiMxZTI5M2I7c3Ryb2tlOiM0NzU1NjkiLz4KPHRleHQgeD0iNTYxIiB5PSIxMTQiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA2NTAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjZjFmNWY5OyBmb250LXNpemU6MTJweCI+cmFiYml0LTA8L3RleHQ+Cjx0ZXh0IHg9IjU2MSIgeT0iMTMwIiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogMTFweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzk0YTNiOCI+YnJva2VyICsgdm9sdW1lPC90ZXh0PgogICAgICAgICAgICAgICAgPHRleHQgeD0iNTYyIiB5PSIxNjYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2ZWU3YjciPk9uZSBicm9rZXI6IG5vIHJlcGxpY2EgdG8gdGFrZSBvdmVyPC90ZXh0PgogICAgICAgICAgICAgICAgPC9zdmc+)

#### Limitations

Where RabbitMQ on Kubernetes and Amazon MQ differ

* **TLS trust behaves differently.** The broker uses a self-signed or cert-manager-issued certificate, not an AWS-managed one. Set up client trust and certificate renewal before you switch endpoints.
* **AWS broker settings are not supported.** CloudWatch logs, KMS encryption, the maintenance window, VPC placement and minor-version upgrades are omitted. Use the target environment's monitoring, storage encryption and upgrade tools instead. Broker credentials and TLS settings are part of the Kubernetes deployment.
* **Streams are not supported.** Amazon MQ for RabbitMQ does not offer them, and this mapping does not set them up. The self-operated broker can run Streams if you add them yourself: core stream queues can use AMQP; the RabbitMQ Stream protocol also needs its plugin, listener and a compatible client.
* **ActiveMQ is not supported.** This mapping covers the RabbitMQ engine only. Amazon MQ's ActiveMQ engine uses a different broker and protocols.

#### Other considerations

**Moving from AWS.** Export exchanges, queues, bindings, users, virtual hosts and policies from the source management API as definitions.json, then import the supported definitions into the new broker. Applications that declare their own topology recreate it when they connect.

**Messages do not move.** Definitions do not include the backlog, and the new broker starts empty. Drain the old broker, or use Shovel or Federation if you need continuity. Deliveries in flight at cutover are not transferred, so test consumer retries.

**Capacity and monitoring.** The broker and its volumes run all the time. Plan capacity from backlog, message sizes, publish and consume rates, and recovery tests on the actual cluster. After cutover, watch disk capacity, queue growth and consumer progress.

Provider references: [quorum queues](https://www.rabbitmq.com/docs/quorum-queues), [default queue type](https://www.rabbitmq.com/docs/vhosts), and [core Streams and the Stream plugin](https://www.rabbitmq.com/docs/stream-core-plugin-comparison).

## Install and run

The documentation and SLAs are public. Downloading and running the Cloud Adapter binary requires an entitled customer account. Set `T9_API_KEY` as described in [Install and Authenticate](https://docs.tensor9.com/cloud-adapter-early-access/getting-started/install-and-authenticate.md), then list the adapters your account may use with this origin:

```sh theme={null}
tensor9 adapt svc list \
  -origin aws::1.0.0::mq::rabbitmq::single
```

The result is limited to directed mappings for this origin that your account is entitled to use. Use a returned backend identifier when configuring the adapter or investigating a request.

Request binary access from [hello@tensor9.com](mailto:hello@tensor9.com) if your account does not yet include this direction.

## Existing data and credentials

Selecting a backend does not copy existing data, credentials or access policies. Plan and verify migration separately before changing an application's endpoint. Do not assume an identifier, credential or encrypted value from the origin service works unchanged on the target.

## Configure, tune and debug

Start with [setup](https://docs.tensor9.com/cloud-adapter-early-access/getting-started/overview.md) and [configuration](https://docs.tensor9.com/cloud-adapter-early-access/configuration/overview.md). Use [tuning](https://docs.tensor9.com/cloud-adapter-early-access/tuning/overview.md) to understand supported request tags, [debugging](https://docs.tensor9.com/cloud-adapter-early-access/debugging/overview.md) to investigate a request, and [High Fidelity Cloud Emulators](https://docs.tensor9.com/cloud-adapter-early-access/local-testing/overview.md) to validate a bounded reproduction.

For requests that go through an entitled service adapter, use [tensor9 explain](https://docs.tensor9.com/cloud-adapter-early-access/debugging/explain.md) and [x-t9-explain](https://docs.tensor9.com/cloud-adapter-early-access/debugging/response-headers.md) to inspect the selected mapping.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.