Migrate DataStax Enterprise (DSE) downloads to Fix Central

Beginning January 2026, DataStax Enterprise (DSE) and tarball and package downloads will no longer be available from DataStax’s public repositories. You must set up a local repository mirror that hosts DSE packages downloaded from IBM Fix Central.

The Fix Central download approach affects the following installation methods and locations:

Tarball downloads: URLs and access methods for downloading DSE tarball files use Fix Central.
Package downloads: URLs and access methods for downloading DSE RPM and Debian packages use Fix Central.
Authentication: Access methods and authentication requirements use Fix Central.

For information about installation options, see Which install method should I use?.

Prerequisites

An active DSE 5.1 license.
An IBMid.
- If you are an existing IBM customer with an IBMid, you can continue to use your established account.
- If you don’t have an IBMid, you can create one.
- If your company uses Enterprise Federation (EF) for authentication with corporate credentials, see the EF documentation.

Migrate tarball downloads

Follow these steps to migrate to the Fix Central downloads approach:

Identify all places where you download DSE components.

Look for commands that use downloads.datastax.com URLs like the following example:
```
curl -L -O https://downloads.datastax.com/enterprise/dse-6.9.12-bin.tar.gz
```
Download and install DSE binaries from Fix Central, as explained in Install with a tarball.

Migrate package downloads and repositories

DataStax removed Debian and RPM package repositories (rpm.datastax.com and debian.datastax.com).

You can find public repository keys in the .zip files (dse-rpm-signing.pub.key and dse-deb-signing.pub.key) for each release version.

Identify all places where you download DSE components.
Download packages from Fix Central to your own local repository, as explained in Install a RHEL package and Install a Debian package.
Verify that the migration succeeded.

Update automation and configuration management

If you use automation tools or configuration management systems, do the following:

Update repository configuration templates or manifests.
Update any hardcoded repository URLs in your playbooks, recipes, or modules.
Test the configurations in a non-production environment before deploying to production.
Update any documentation or runbooks that reference the previous repository URLs.

Update tool downloads

If you download any of the following tools separately, you must also update those download locations:

cqlsh: See Install the cqlsh standalone tool for download instructions.