Connecting to a Cluster Instance Using Mongo Shell (Private Network)

For details about how to install a MongoDB client, see How Can I Install a MongoDB Client?

The following describes how to upload the certificate to a Linux and Window ECS:

• In Linux, run the following command:
  scp <IDENTITY_FILE><REMOTE_USER>@<REMOTE_ADDRESS>:<REMOTE_DIR>

  

  • IDENTITY_FILE is the directory where the root certificate resides. The file access permission is 600.
  • REMOTE_USER is the ECS OS user.
  • REMOTE_ADDRESS is the ECS address.
  • REMOTE_DIR is the directory of the ECS to which the root certificate is uploaded.
• In Windows, upload the root certificate using a remote connection tool.

Method 1: Using the private HA connection address (recommended)

DDS provides a private HA connection address that consists of IP addresses and ports of all dds mongos nodes in a cluster instance. You can use this address to connect to the cluster instance to improve availability of the cluster instance.

Example command:

./mongo <Private HA connection address> --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

Parameter description:

• Private HA Connection Address: On the Instances page, click the instance name. The Basic Information page is displayed. Choose Connections. Click the Private Connection tab and obtain the connection address of the current instance from the Private HA Connection Address field.
  Figure 1 Obtaining the private HA connection address
  

  The format of the private HA connection address is as follows. The database username rwuser and authentication database admin cannot be changed.

  mongodb://rwuser:<password>@192.168.xx.xx:8635,192.168.xx.xx:8635/test?authSource=admin

  Pay attention to the following parameters in the private HA address:

  Table 1 Parameter information

  Parameter	Description
  rwuser	Database username
  <password>	Password for the database username. Replace it with the actual password. If the password contains at signs (@), exclamation marks (!), dollar signs ($), or percent signs (%), replace them with hexadecimal URL codes (ASCII) %40, %21, %24, and %25 respectively. For example, if the password is ****@%***!$, the corresponding URL code is ****%40%25***%21%24.
  192.168.***.***:8635,192.168.***.***:8635	IP addresses and ports of the dds mongos nodes of the cluster instance to be connected.
  test	The name of the test database. You can set this parameter based on your service requirements.
  authSource=admin	The authentication database of user rwuser must be admin. authSource=admin is fixed in the command.

• FILE_PATH is the path for storing the root certificate.
• --sslAllowInvalidHostnames: To ensure that the internal communication of the cluster does not occupy resources such as the user IP address and bandwidth, the cluster certificate is generated using the internal management IP address. --sslAllowInvalidHostnames is needed for the SSL connection through a private network.

Command example:

./mongo mongodb://rwuser:<password>@192.168.xx.xx:8635,192.168.xx.xx:8635/test?authSource=admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

Method 2: Using the private HA connection address (user-defined database and account)

Example command:

./mongo <Private HA connection address> --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

Parameter description:

• Private HA Connection Address: On the Instances page, click the instance name. The Basic Information page is displayed. Choose Connections. Click the Private Connection tab and obtain the connection address of the current instance from the Private HA Connection Address field.
  Figure 2 Obtaining the private HA connection address
  

  The format of the obtained private HA connection address is as follows:

  mongodb://rwuser:<password>@192.168.xx.xx:8635,192.168.xx.xx:8635/test?authSource=admin

  The following table lists the required parameters in the private HA address.

  Table 2 Parameter information

  Parameter	Description
  rwuser	Database username. The default value is rwuser. You can change the value to the username based on your service requirements.
  <password>	Password for the database username. Replace it with the actual password. If the password contains at signs (@), exclamation marks (!), dollar signs ($), or percent signs (%), replace them with hexadecimal URL codes (ASCII) %40, %21, %24, and %25 respectively. For example, if the password is ****@%***!$, the corresponding URL code is ****%40%25***%21%24.
  192.168.***.***:8635,192.168.***.***:8635	IP addresses and ports of the dds mongos nodes of the cluster instance to be connected.
  test	The name of the test database. You can set this parameter based on your service requirements.
  authSource=admin	The authentication database of user rwuser is admin. NOTE: If you use a user-defined database for authentication, change the authentication database in the HA connection address to the name of the user-defined database. In addition, replace rwuser with the username created in the user-defined database.

• FILE_PATH is the path for storing the root certificate.
• --sslAllowInvalidHostnames: To ensure that the internal communication of the cluster does not occupy resources such as the user IP address and bandwidth, the cluster certificate is generated using the internal management IP address. --sslAllowInvalidHostnames is needed for the SSL connection through a private network.

For example, if you create a user-defined database Database and user test1 in the database, the connection command is as follows:

./mongo mongodb://test1:<password>@192.168.xx.xx:8635,192.168.xx.xx:8635/Database?authSource=Database --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

Method 3: Using a private IP address

Example command:

./mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin --ssl --sslCAFile <FILE_PATH> --sslAllowInvalidHostnames

Parameter description:

• DB_HOST is the IP address of the dds mongos node of the cluster instance to be connected.

  Click the instance name. On the Basic Information page, choose Connections > Private Connection, obtain the private IP address of the dds mongos node on the dds mongos tab in the Node Information area.

  Figure 3 Obtaining the private IP address
  
• DB_PORT is the port of the instance to be connected. The default port is 8635.

  Click the instance name. On the Basic Information page, choose Connections. On the Private Connection tab, obtain the database port information in the Database Port field in the Basic Information area.

  Figure 4 Obtaining the port
  
• DB_USER is the database user. The default value is rwuser.
• FILE_PATH is the path for storing the root certificate.
• --sslAllowInvalidHostnames: To ensure that the internal communication of the cluster does not occupy resources such as the user IP address and bandwidth, the cluster certificate is generated using the internal management IP address. --sslAllowInvalidHostnames is needed for the SSL connection through a private network.

Enter the database account password when prompted:

Enter password:

Command example:

./mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin --ssl --sslCAFile /tmp/ca.crt --sslAllowInvalidHostnames

mongos>

Method 1: Private HA connection address (recommended)

Example command:

./mongo "<Private HA Connection Address>"

Private HA Connection Address: On the Instances page, click the instance name. The Basic Information page is displayed. Choose Connections. Click the Private Connection tab and obtain the connection address of the current instance from the Private HA Connection Address field.

Figure 5 Obtaining the private HA connection address

The format of the private HA connection address is as follows. The database username rwuser and authentication database admin cannot be changed.

mongodb://rwuser:<password>@192.168.xx.xx:8635,192.168.xx.xx:8635/test?authSource=admin

The following table lists the required parameters in the private HA address.

Command example:

./mongo mongodb://rwuser:<password>@192.168.xx.xx:8635,192.168.xx.xx:8635/test?authSource=admin

Method 2: Private HA connection (user-defined database and account)

Example command:

./mongo "<Private HA Connection Address>"

Private HA Connection Address: On the Instances page, click the instance name. The Basic Information page is displayed. Choose Connections. Click the Private Connection tab and obtain the connection address of the current instance from the Private HA Connection Address field.

Figure 6 Obtaining the private HA connection address

The format of the obtained private HA connection address is as follows:

mongodb://rwuser:<password>@192.168.xx.xx:8635,192.168.xx.xx:8635/test?authSource=admin

The following table lists the required parameters in the private HA address.

For example, if you create a user-defined database Database and user test1 in the database, the connection command is as follows:

./mongo mongodb://test1:<password>@192.168.xx.xx:8635,192.168.xx.xx:8635/Database?authSource=Database

Method 3: Using a private IP address

Example command:

./mongo --host <DB_HOST> --port <DB_PORT> -u <DB_USER> -p --authenticationDatabase admin

Parameter description:

• DB_HOST is the IP address of the dds mongos node of the cluster instance to be connected.

  Click the instance name. On the Basic Information page, choose Connections > Private Connection, obtain the private IP address of the dds mongos node on the dds mongos tab in the Node Information area.

  Figure 7 Obtaining the private IP address
  
• DB_PORT is the port of the instance to be connected. The default port is 8635.

  Click the instance name. On the Basic Information page, choose Connections. On the Private Connection tab, obtain the database port information in the Database Port field in the Basic Information area.

  Figure 8 Obtaining the port
  
• DB_USER is the database user. The default value is rwuser.

Enter password:

Command example:

./mongo --host 192.168.1.6 --port 8635 -u rwuser -p --authenticationDatabase admin

mongos>