ApsaraDB for MongoDB:Create a standalone instance

Precautions

• Standalone instances take a long time to recover from failures and have no Service Level Agreement (SLA) guarantees.
• If your application is deployed on an Elastic Compute Service (ECS) instance, make sure that your ApsaraDB for MongoDB instance and ECS instance meet the following requirements to ensure network connectivity: For more information about how to view ECS instance information, see View instance information.
  • Your ApsaraDB for MongoDB instance and ECS instance are deployed in the same region, and preferably belong to the same zone. This reduces network latency.
  • Your ApsaraDB for MongoDB instance and ECS instance use the same network type.
    Note

    • VPC is recommended because VPC provides higher security.
    • If the network type is VPC, you must ensure that they use the same VPC ID.
    • If you want to use VPC, but the network type of the ECS instance is classic network, you can change the network type of the ECS instance to VPC. For more information, see Migrate ECS instances from the classic network to a VPC.

Limits

• Standalone instances can be created only in the regions and zones listed in the following section for single-zone deployment.
  • China (Hangzhou): Hangzhou Zone G, H, or I
  • China (Shanghai): Shanghai Zone B or G
  • China (Qingdao): Qingdao Zone C
  • China (Beijing): Beijing Zone F or H
  • China (Shenzhen): Shenzhen Zone E
  • Singapore (Singapore): Singapore Zone A, B, or C
• Standalone instances support only MongoDB 3.4 and 4.0.
• Standalone instances do not support incremental data migration, incremental data synchronization, or point-in-time data restoration by creating a new instance.

Billing

• Subscription: If you purchase a subscription instance, you must pay an upfront fee for the instance.
• Pay-as-you-go: A pay-as-you-go instance is charged per hour based on the configuration of the instance. Fees are automatically deducted from your Alibaba Cloud account.

Procedure

After you perform the following steps, ApsaraDB for MongoDB automatically creates one or more standalone instances. No manual operations are required.

1. Log on to the ApsaraDB for MongoDB console.
2. In the left-side navigation pane, click Replica Set Instances.
3. On the Replica Set Instances page, click Create Instance.
4. Click Replica Set (Subscription) or Replica Set (Pay-as-you-go) based on your needs.
5. Configure the parameters described in the following table.

   Parameter	Description
   Region	The region where you want to deploy the standalone instance. For more information about the regions where standalone instances can be created, see the "Limits" section of this topic. Note After the standalone instance is created, you cannot change the region of the instance. Proceed with caution. If your application is deployed on an Elastic Compute Service (ECS) instance, we recommend that you deploy the standalone instance in the region where the ECS instance resides. If the standalone instance and the ECS instance belong to different regions, your application cannot communicate with the standalone instance over an internal network.
   Zone	The zone where you want to deploy the standalone instance. For more information about the zones where standalone instances can be created, see the "Limits" section of this topic. Note If your application is deployed on an ECS instance, we recommend that you deploy the standalone instance in the zone where the ECS instance resides to reduce network latency.
   Engine Version	The MongoDB version of the standalone instance. Valid values: MongoDB 4.0 MongoDB 3.4
   Active-standby Nodes	The number of active-standby nodes in the standalone instance. Select Standalone.
   Read-only Nodes	The number of read-only nodes in the standalone instance. This parameter can be set only to No Read-only Node.
   Storage Engine	The storage engine of the standalone instance. This parameter can be set only to WiredTiger.
   Storage Type	This parameter can be set only to Local SSD.
   Network Type	The type of network where you want to deploy the standalone instance. This parameter can be set only to VPC. Note A virtual private cloud (VPC) is an isolated network that provides higher security and higher performance than the classic network. If your application is deployed on an ECS instance, you must make sure that the ECS instance is in a VPC. This ensures network connectivity between your application and the standalone instance.
   VPC	The ID of the VPC where you want to deploy the standalone instance. If no VPCs are available, you can create a VPC in the VPC console. For more information, see Create and manage a VPC.
   vSwitch	The ID of the vSwitch to which the standalone instance connects. If no vSwitches are available, you can create a vSwitch in the VPC console. For more information, see Create and manage a vSwitch.
   Specifications	The number of CPU cores and memory capacity that are configured for the standalone instance. For more information about the specifications that are supported by standalone instances, see Instance types.
   Storage	The storage capacity of the standalone instance. Note The storage capacity is used to store your data, system, and log files.
   Username	This parameter can be set only to root. Note This value indicates the root account of the admin database.
   Set Password	The time when you want to set the password of the root account. Valid values: Set Now: You want to immediately set the password of the root account. Set Later: You want to set the password of the root account after the standalone instance is created. For more information, see (Optional) Reset a password.
   Password	The password of the root account. If you set the Set Password parameter to Set Now, you must set the password of the root account when you create the standalone instance. You must set the password in compliance with the following rules: The password must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and specific special characters. These special characters include !@#$%^&*()_+-= The password must be 8 to 32 characters in length.
   Duration	The subscription duration of the standalone instance. This parameter is displayed only when you specify to create a subscription instance. A valid monthly subscription duration ranges from one month to nine months. A valid yearly subscription duration ranges from one year to five years. Note If you want to enable auto-renewal for the standalone instance, select Auto-renewal and make sure that you have sufficient balance within your account before the system automatically renews the instance.
   Quantity	The number of standalone instances that you want to create. All the created standalone instances have the same specifications. Valid values: 1 to 10.

6. Complete the payment based on the billing method of the instance.

   Billing method	Procedure
   Subscription	Complete the parameter settings and click Buy Now. On the Confirm Order page, check the parameter settings. Then, read MongoDB Replica Set (Subscription) Agreement of Service and select I have read and agree to MongoDB Replica Set (Subscription) Agreement of Service. Click Pay. On the Purchase page, complete the payment. Note You can also click Add to Cart to pay for orders in the cart in a lump sum. For more information, see Pay for orders in the cart.
   Pay-as-you-go	Complete the parameter settings and click Buy Now. On the Confirm Order page, check the parameter settings. Then, read MongoDB Replica Set (Pay-as-you-go) Agreement of Service and select I have read and agree to MongoDB Replica Set (Pay-as-you-go) Agreement of Service. Click Activate Now.The system collects the amount due within the next hour.

7. Check whether the standalone instance is created.
   1. After you complete the payment, click Console to go to the ApsaraDB for MongoDB console.
   2. In the upper-left corner of the page, select the resource group and region to which the instance belongs.
   3. In the instance list that appears, check whether the standalone instance that you created is displayed.
      • If the standalone instance is displayed, the instance is created. If the standalone instance is in the Running state, the instance is running.
      • If the standalone instance is not displayed, wait for 10 to 15 minutes. Then, refresh the page. If the standalone instance is still not displayed, check whether the issues that are described in the following table occur. If none of the issues occur, contact Alibaba Cloud technical support.
        The following table describes the possible causes of and solutions to the issues due to which the created standalone instance is not displayed.

        Cause	Solution
        The standalone instance does not belong to the region that you select.	In the upper-left corner of the ApsaraDB for MongoDB console, select the resource group and region to which the standalone instance belongs.
        The standalone instance does not belong to the instance architecture that you select.	In the left-side navigation pane of the ApsaraDB for MongoDB console, click Replica Set Instances.
        The standalone instance is not created due to insufficient resources.	The system may fail to create the instance due to insufficient resources. In this case, your payment is refunded. Go to the Billing Management console and open the Orders page to check whether you receive refunds. After you confirm the refunds, perform one of the following operations: Select a different zone and try again. Submit a ticket. For more information, see New Ticket.

Pay for orders in the cart

Related API operations