All Products
Search
Document Center

ApsaraDB for Redis:Release a private endpoint for an ApsaraDB for Redis instance

Last Updated:Dec 15, 2023

If you no longer need a private endpoint or if you want to perform operations that are not supported in direct connection mode, you can release the private endpoint to disable the direct connection mode. For example, you can release the private endpoint to disable the direct connection mode before you change configurations or upgrade a major version.

Prerequisites

  • The instance uses local disks.

  • The instance uses the cluster architecture.

  • The instance has the direct connection mode enabled. For more information, see Enable the direct connection mode.

  • The private endpoint for the ApsaraDB for Redis instance configured in your application is changed to another available endpoint, such as the internal endpoint in proxy mode. For more information, see View endpoints.

    Warning

    After a private endpoint is released, the client cannot use it to connect to the ApsaraDB for Redis instance. We recommend that you change the connection configuration in your application before you release the private endpoint.

Procedure

  1. Log on to the ApsaraDB for Redis console and go to the Instances page. In the top navigation bar, select the region in which the instance that you want to manage resides. Then, find the instance and click the instance ID.

  2. In the Connection Information section, click Release Endpoint to the right of Private Endpoint.

  3. In the panel that appears, click OK.

Related API operations

API operation

Description

AllocateDirectConnection

Applies for a private endpoint for an ApsaraDB for Redis cluster instance.

ReleaseDirectConnection

Releases a private endpoint for an ApsaraDB for Redis cluster instance.