All Products
Search
Document Center

Tair (Redis® OSS-Compatible):View endpoints

Last Updated:Mar 28, 2026

Before connecting to a Tair (Redis OSS-compatible) instance, get its endpoint from the console. The virtual IP address (VIP) of an instance can change during maintenance, upgrades, or downgrades — always use the instance endpoint (for example, r-2vcl6xcftp1nu7****.com) in your application code.

Prerequisites

Before you begin, ensure that you have:

The endpoint is hidden in the console until a whitelist is configured. If you don't see the endpoint, configure the whitelist first.

Find your endpoint

  1. Log on to the console and go to the Instances page. In the top navigation bar, select the region where your instance resides, then click the instance ID.

  2. In the Connection Information section, view the available endpoints and port numbers.

The following table describes the fields in the Connection Information section:

FieldDescription
Proxy EndpointConnects through the Alibaba Cloud-developed proxy. Supports connection aggregation, load balancing, mode switching, and failover. Available for all architectures that support proxy mode.
Private EndpointDirect connection to the instance over VPC. For standard architecture instances, connects directly to the primary node. For cluster architecture instances, load balancing is handled by the native Redis Cluster.
Public AccessConnects over the Internet. Requires a public endpoint — click Apply For Endpoint to request one. Not available for cloud-native cluster instances in direct connection mode.

After getting the endpoint, connect to your instance. See Use redis-cli to connect to an instance.

Which endpoint to use

Choose based on your instance architecture and network type:

ArchitectureConnection typeVPCInternet
Cloud-native — standardDirect connection modeYesYes
Cloud-native — cluster¹Direct connection modeYesNo
Cloud-native — cluster¹Proxy modeYesYes
Cloud-native — read/write splittingProxy modeYesYes
Classic — standardDirect connection modeYesYes
Classic — cluster²Proxy mode or direct connection modeYesYes
Classic — read/write splittingProxy modeYesYes

¹ A cloud-native cluster instance supports only one connection type: direct connection or proxy. The mode is selected at creation and cannot be changed afterward.

² A classic cluster instance supports both direct connection mode and proxy mode.

Use VPC whenever possible. You are not charged for the traffic to connect to Tair instances over the Internet, but VPC provides lower latency and higher security. Reserve Internet access for clients outside Alibaba Cloud (on-premises devices, ECS instances in a different VPC, or third-party cloud services).

Proxy mode and direct connection mode

  • Proxy Endpoint: Traffic passes through an Alibaba Cloud-developed proxy that handles routing, load balancing, mode switching, and failover. The proxy also supports Alibaba Cloud's proprietary proxy commands. For details, see Tair Proxy features.

  • Private Endpoint: Traffic goes directly to the instance without a proxy. For standard architecture instances, this means a direct connection to the primary node. For cluster architecture instances, the native Redis Cluster handles routing — the same behavior as connecting to an open-source Redis Cluster.

FAQ

Why isn't the endpoint displayed?

The endpoint only appears after you configure a whitelist for the instance. See Configure a whitelist.

Why can't I find the option to apply for a public endpoint?

Two reasons:

  • No VPC endpoint shown: This means no whitelist is configured. Configure the whitelist first — the public endpoint option appears after the VPC endpoint is visible.

  • Cloud-native cluster in direct connection mode: Public endpoints are not supported for this combination. Connect over VPC instead. To check whether your instance is a cloud-native cluster in direct connection mode, go to the Instance Information page and verify the deployment mode and connection type. In the Connection Information section, look for Private Endpoint — its presence confirms direct connection mode. If you need Internet access or your application runs outside the instance's VPC, switch to proxy mode. You cannot change the connection mode after creation — use the Restore Instance feature to restore a backup to a new instance and select Proxy Mode during setup. See Restore data from a backup set.

    Warning

    After creating the new instance, update your connection code to use the new endpoint and connection mode. Failing to do so will prevent the application from connecting.

    image

    image

How do I enable a proxy endpoint?

It depends on the instance type:

  • Read/write splitting and classic cluster instances: Proxy endpoints are provided by default. No action needed.

  • Cloud-native cluster instances: Select proxy mode or direct connection mode when creating the instance. The mode cannot be changed after creation.

  • Standard architecture instances: Proxy mode is not available. Standard architecture uses a primary-secondary setup, and direct connection to the primary node is the only connection type.

Can I connect to a secondary node?

No. Secondary nodes provide high availability (HA) for primary/secondary failover and are not directly accessible.

What's next