Rabbitmq: Migrating RabbitMQ Package Repositories from Cloudsmith to *.rabbitmq.com Mirrors

Products

• VMware Tanzu RabbitMQ

Issue/Introduction

Team RabbitMQ has deprecated direct public access to its package repositories hosted on Cloudsmith for dnf, yum, and apt package managers.

This change does not impact the availability or licensing of open-source RabbitMQ binary packages. Packages remain freely available on the official RabbitMQ mirror infrastructure.

Cause

 

• Bandwidth & Quota Limits: Direct public traffic to Cloudsmith consistently exhausted monthly bandwidth quotas.

• Official Mirror Infrastructure: The *.rabbitmq.com mirror network has significantly higher bandwidth quotas and is designed to handle high-volume public traffic.

• Upstream Role: Cloudsmith will now strictly serve as an internal upstream sync repository for RPM packages rather than a direct client-facing endpoint.

 

Resolution

To ensure continuous access to security updates and patch releases, update your repository configuration files on affected servers.

A. Debian / Ubuntu (apt)

1. Remove or disable legacy Cloudsmith references in /etc/apt/sources.list or /etc/apt/sources.list.d/rabbitmq.list.

2. Update your sources configuration to use deb*.rabbitmq.com as described in the Official RabbitMQ Debian Installation Guide.

3. Import the official Team RabbitMQ GPG signing key if not already present.

4. Run apt-get update.

B. RHEL / CentOS / Fedora / Rocky (dnf / yum)

1. Update your .repo file (typically located at /etc/yum.repos.d/rabbitmq.repo) to replace Cloudsmith URLs with yum*.rabbitmq.com mirror endpoints as outlined in the Official RabbitMQ RPM Installation Guide.

2. Existing GPG keys do not need to be modified for RPM mirrors.

3. Run dnf clean all (or yum clean all) followed by dnf makecache.