By default, Redis Enterprise Software databases expose a single endpoint, e.g. cluster.com (FQDN).

When you create a cluster via the UI, you can configure it to expose private and public endpoints. This is common for environments such as cloud platforms and enterprises.

When doing so, the cluster creates an additional FQDN, e.g. internal.cluster.com for private network (e.g. VPC or an internal network), while the cluster.com FQDN can be used by a public network (e.g. the internet).

You can enable public and private endpoints during cluster creation only. However, you can still add an additional FQDN in a different domain (cluster.io, for example) after cluster creation.

To enable private and public endpoints:

  1. Verify the IP addresses are bound to the server or instance.

  2. During cluster setup, turn on Enable public endpoints support in the Cluster screen’s Configuration section.

    The endpoint support setting appears in the **Configuration section** of the **Cluster** setup screen.

    If this setting is not enabled when the cluster is created, databases on the cluster support only a single endpoint.

  3. Select Next to proceed to Node configuration.

  4. In the Network configuration section:

    1. Configure the machine’s public IP address for external traffic.

    2. Configure the private IP address for both internal and external traffic so it can be used for private database endpoints.

After cluster creation, both sets of endpoints are available for databases in the cluster.

To view and copy public and private endpoints for a database in the cluster, see the database’s Configuration > General section.

View public and private endpoints from the General section of the database's Configuration screen.