All Products
Search

This Product

    ApsaraDB for MongoDB:Release a shard or ConfigServer node endpoint

    Document Center

    ApsaraDB for MongoDB:Release a shard or ConfigServer node endpoint

    Last Updated:Jul 17, 2026

    Release the internal endpoint of a shard or ConfigServer node when direct access to the node is no longer required.

    Prerequisites

    The sharded cluster instance uses the MongoDB protocol.

    Considerations

    • ApsaraDB for MongoDB does not support releasing mongos node endpoints.

    • Before releasing the connection address of a shard or ConfigServer, securely save the node's Account Name and Account Password. If you forget the username and password, you can manually reset the password.

    • After an endpoint is released, all associated node endpoints and IP addresses are also released and can no longer be used to connect to the nodes. Proceed with caution.

    • This operation releases only the internal endpoint. To release a public endpoint, see Release a public endpoint.

    • ApsaraDB for MongoDB no longer supports requesting ConfigServer endpoints. Existing endpoints are not affected, but after a ConfigServer endpoint is released, you cannot request it again.

    Procedure

    1. Go to the Sharded Cluster Instances page. In the top navigation bar, select a resource group and region, then click the ID of the target instance.

    2. In the left-side navigation pane of the instance page, click Database Connections.

    3. In the Internal Connections - VPC section, find the target endpoint and click Release in the Actions column.

    4. In the Confirm Release dialog box, click Confirm.

      Wait for the instance status to change from Releasing Network Connection to Running. The endpoint is successfully released.