To ensure data security, you can release public endpoints that are no longer needed in the console.

Precautions

  • After a public endpoint is released for an instance or a node, you cannot connect to the instance or node by using that endpoint.
  • After a public endpoint is released, we recommend that you delete the corresponding public IP addresses from the whitelist to ensure data security. For more information, see Configure a whitelist.

Procedure

  1. Log on to the ApsaraDB for MongoDB console.
  2. In the upper-left corner of the page, select the resource group and the region of the target instance.
  3. In the left-side navigation pane, click Replica Set Instances or Sharded Cluster Instances.
  4. Find the target instance and click its ID.
  5. In the left-side navigation pane, click Database Connections.
  6. Perform the corresponding operations based on the instance category.
    • Standalone or replica set instances
      Note After the public endpoint of a replica set instance is released, the public endpoints of the primary and secondary nodes are released.
      1. In the Public Connections section, click Release Public Connection String. Release a public endpoint
      2. In the Release Public Connection String message, click OK.
    • Sharded cluster instances
      Note
      • You can release one or more public endpoints of the mongos, shard, and Configserver nodes for a sharded cluster instance. The nodes whose endpoints are not released can still be connected. For more information about the node types of sharded cluster instances, see Architecture of sharded cluster instances.
      • After the public endpoint of a shard or Configserver node is released, the public endpoints of the primary and secondary nodes are released.
      1. In the Public Connections section, click Release in the Actions column corresponding to the node whose endpoint you want to release. Release the public endpoint of a node
        Node type Description
        mongos The mongos node.
        db The shard node.
        cs The Configserver node.
      2. In the Release Public Connection String message, click OK.
      3. Optional:If you want to release the public endpoints of multiple nodes in a sharded cluster instance, repeat the preceding steps.
        Note To release the public endpoint of another node in the instance, you must wait until the state of the instance becomes Running.
  7. Optional:After the public endpoint of an instance or a node is released, remove the corresponding public IP addresses from the whitelist to ensure data security. For more information, see Configure a whitelist or an ECS security group for an ApsaraDB for MongoDB instance.