Low
Recover
Regional
RabbitMQ brokers should use cluster deployment mode
NIST 800-53
Description
This control verifies that an Amazon MQ RabbitMQ broker's deployment mode is set to cluster deployment. It fails if a single-instance broker (which is the default) is used. Cluster deployment offers high availability by grouping three RabbitMQ broker nodes, each with its own Amazon Elastic Block Store (EBS) volume and a shared state, ensuring data replication and reduced downtime.
Remediation
To remediate RabbitMQ brokers not using cluster deployment mode, you need to modify the broker to use cluster deployment mode.
Steps
- Navigate to the Amazon MQ console
- Select the RabbitMQ broker that needs remediation
- Click on 'Edit' or 'Modify' broker
- Go to 'Configuration' settings
- Change 'Deployment mode' to 'Cluster'
- Configure cluster settings and node count
- Set up EBS volumes for each node
- Configure shared state settings
- Review the cluster configuration
- Apply the changes and verify cluster mode is working
Compliance
NIST 800-53