> For the complete documentation index, see [llms.txt](https://academy.cegedim.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.cegedim.cloud/message-brokers/rabbitmq/rabbitmq-features.md).

# RabbitMQ - Features

## Topologies <a href="#rabbitmqarchitecture-topologies" id="rabbitmqarchitecture-topologies"></a>

### Standalone instance <a href="#rabbitmqarchitecture-singleinstance" id="rabbitmqarchitecture-singleinstance"></a>

RabbitMQ can be provisioned as a standalone instance on self-service using ITCare.

**Properties**

A standalone instance will have the following properties :

<table><thead><tr><th width="249">Component</th><th>Value</th></tr></thead><tbody><tr><td>AMQP listening port</td><td><ul><li>5672 if TLS is disabled</li><li>5671 if TLS is enabled</li></ul></td></tr><tr><td>Prometheus endpoint</td><td>http://my-instance.hosting.cegedim.cloud:15692/metrics</td></tr><tr><td>Administration URL</td><td>http://my-instance.hosting.cegedim.cloud:15672/</td></tr><tr><td>REST API endpoint</td><td>http://my-instance.hosting.cegedim.cloud:15672/api</td></tr></tbody></table>

### Cluster <a href="#rabbitmqarchitecture-cluster" id="rabbitmqarchitecture-cluster"></a>

RabbitMQ can be provisioned as a cluster on self-service using ITCare.

A RabbitMQ cluster can be deployed in 3 nodes or 5 nodes topology tailored for quorum queues use.

Nodes will be spread on **all** availability zones available in the targeted area.

```mermaid
graph TD
    subgraph region["Region"]
        subgraph aza["Availability Zone A"]
            na["🐰 RabbitMQ<br/>node 1"]
        end
        subgraph azb["Availability Zone B"]
            nb["🐰 RabbitMQ<br/>node 2"]
        end
        subgraph azc["Availability Zone C"]
            nc["🐰 RabbitMQ<br/>node 3"]
        end
    end

    na <-->|cluster| nb
    nb <-->|cluster| nc
    na <-->|cluster| nc

    style region fill:#fff5eb,stroke:#000,stroke-width:2px,color:#000
    style aza fill:#ffe0b2,stroke:#ff7a00,stroke-width:2px,color:#000
    style azb fill:#ffe0b2,stroke:#ff7a00,stroke-width:2px,color:#000
    style azc fill:#ffe0b2,stroke:#ff7a00,stroke-width:2px,color:#000
    style na fill:#ff7a00,stroke:#cc5500,stroke-width:2px,color:#fff
    style nb fill:#ff7a00,stroke:#cc5500,stroke-width:2px,color:#fff
    style nc fill:#ff7a00,stroke:#cc5500,stroke-width:2px,color:#fff
```

**Properties**

Once deployed the cluster will have the following properties :

<table><thead><tr><th width="249">Component</th><th>Value</th></tr></thead><tbody><tr><td>AMQP listening port</td><td><ul><li>5672 if TLS is disabled</li><li>5671 if TLS is enabled</li></ul></td></tr><tr><td>Prometheus endpoint</td><td>http://nodex.hosting.cegedim.cloud:15692/metrics</td></tr><tr><td>Administration URL</td><td>https://cluster-name.rmq.hosting.cegedim.cloud/</td></tr><tr><td>REST API endpoint</td><td>https://cluster-name.rmq.hosting.cegedim.cloud/api</td></tr></tbody></table>

### Quorum queues <a href="#rabbitmqarchitecture-quorumqueues" id="rabbitmqarchitecture-quorumqueues"></a>

Quorum queues are highly recommended with RabbitMQ clusters issued from the cegedim.cloud PaaS for maximum resiliency !

A quorum queue will natively be replicated to all nodes participating in the cluster.

{% embed url="<https://www.rabbitmq.com/quorum-queues.html>" %}

{% hint style="danger" %}
Classic mirroring is not advised on a RabbitMQ cluster since quorum queue is its natural enhancement.
{% endhint %}

## Features <a href="#rabbitmqarchitecture-features" id="rabbitmqarchitecture-features"></a>

This section is to list which feature / capabilities are available to customer, and how to request / perform them :

<table data-header-hidden><thead><tr><th width="184"></th><th></th></tr></thead><tbody><tr><td><strong>Self-service</strong></td><td>Customer can perform action autonomously.</td></tr><tr><td><strong>On Request</strong></td><td>Customer can request for the action to be done to cegedim.cloud support team.</td></tr></tbody></table>

<table data-full-width="true"><thead><tr><th width="357">Feature</th><th width="133" data-type="checkbox">Self-service</th><th width="136.5" data-type="checkbox">On Request</th><th>Comments</th></tr></thead><tbody><tr><td>SSH access</td><td>false</td><td>false</td><td>SSH access is disabled and reserved to cegedim.cloud administrators.</td></tr><tr><td>Settings management</td><td>false</td><td>true</td><td>Modification of rabbitmq.conf and other internal settings are performed by cegedim.cloud on request.</td></tr><tr><td>RabbitMQ Admin access</td><td>true</td><td>true</td><td><p>Customer can log in with an administrator account to the RabbitMQ Management UI (password defined by customer in the provisioning wizard).</p><p>Some objects are required and reserved to cegedim.cloud operations. Enforcements can be applied.</p></td></tr><tr><td>Export, Import RabbitMQ definitions</td><td>true</td><td>false</td><td>Available in Self-service using the Management UI or the API.</td></tr><tr><td>Manage RabbitMQ plugins</td><td>false</td><td>true</td><td>RabbitMQ plugins are managed by cegedim.cloud and can be installed on request by our support team.</td></tr></tbody></table>

## Security <a href="#rabbitmqarchitecture-security" id="rabbitmqarchitecture-security"></a>

### Authentication <a href="#rabbitmqarchitecture-authentication" id="rabbitmqarchitecture-authentication"></a>

Authentication uses RabbitMQ internal database.

### Authorization and passwords <a href="#rabbitmqarchitecture-authorizationandpasswords" id="rabbitmqarchitecture-authorizationandpasswords"></a>

This section list the password management for the PaaS RabbitMQ :

<table data-full-width="true"><thead><tr><th width="285">Account</th><th data-type="checkbox">Stored by cegedim.cloud</th><th width="198.2" data-type="checkbox">Stored by customer</th><th width="125" data-type="checkbox">Enforced</th><th>Hashing algorithm</th></tr></thead><tbody><tr><td><strong>admin</strong> account password</td><td>false</td><td>true</td><td>false</td><td>sha256</td></tr><tr><td><strong>ANY</strong> other account password</td><td>false</td><td>true</td><td>false</td><td>sha256</td></tr><tr><td><strong>cgdm_admin</strong> account password</td><td>true</td><td>false</td><td>true</td><td>sha256</td></tr><tr><td><strong>monitoring</strong> account password</td><td>true</td><td>false</td><td>true</td><td>sha256</td></tr></tbody></table>

### Secured Transport <a href="#rabbitmqarchitecture-securedtransport" id="rabbitmqarchitecture-securedtransport"></a>

TLS/SSL can be activated for AMQP protocol at provisioning or afterwards.

By default, it is disabled to avoid unnecessary overhead.

### Policies <a href="#rabbitmqarchitecture-policies" id="rabbitmqarchitecture-policies"></a>

This section list the policies management for the PaaS RabbitMQ :

<table><thead><tr><th width="121">Policies</th><th width="100" data-type="checkbox">Default</th><th width="109" data-type="checkbox">Enforced</th><th>Comments</th></tr></thead><tbody><tr><td><strong>TTL</strong></td><td>true</td><td>false</td><td>Queues left unused for 28 days are automatically deleted (queue TTL). This policy does not set a TTL on messages</td></tr><tr><td><strong>HA</strong></td><td>true</td><td>true</td><td>ha-mode configured to ALL (RabbitMQ 3.x only)</td></tr></tbody></table>

{% hint style="info" %}
**RabbitMQ 4.x - Important change:**

Starting from RabbitMQ 4.0, the HA policy is no longer applied as Quorum Queues natively provide data replication. Feature Flags are automatically enabled during provisioning.

For RabbitMQ 3.x versions, the HA policy remains active with ha-mode: ALL.
{% endhint %}

{% hint style="warning" %}
**RabbitMQ 4.3 - Important changes:**

* Mnesia is removed: Khepri is the only metadata store. In a cluster, a majority of nodes must be online at all times (2 out of 3, 3 out of 5).
* Deprecated features are refused by default, in particular queues that are neither durable nor exclusive. Declare your queues as durable.
* Classic queues version 1 are removed: declaring a queue with `x-queue-mode` or `x-queue-version = 1` fails.
  {% endhint %}

{% hint style="warning" %}
Please open a request ticket if you need these policies modified.
{% endhint %}

### Data location <a href="#rabbitmqarchitecture-datalocation" id="rabbitmqarchitecture-datalocation"></a>

Datas for cegedim.cloud's RabbitMQ PaaS are stored on the dedicated virtual machines created upon requesting a PaaS.

These virtual machines and the storage associated are hosted and managed in cegedim.cloud's own data centers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.cegedim.cloud/message-brokers/rabbitmq/rabbitmq-features.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
