This topic describes how to create an ApsaraDB for MongoDB standalone instance. Standalone instances provide a high level of data fault tolerance and are suitable for database systems that do not store crucial data. For example, you can use standalone instances in scenarios such as development, testing, and training. This topic describes how to create a standalone instance in the ApsaraDB for MongoDB console.

Prerequisites

An Alibaba Cloud account is created. For more information, see Sign up with Alibaba Cloud.

Precautions

If your application is deployed on an Elastic Compute Service (ECS) instance, make sure that your standalone instance and the ECS instance meet the following requirements to ensure network connectivity:
  • Your standalone instance and the ECS instance reside in the same region, and preferably belong to the same zone. This reduces network latency. You can view the region and zone of a created ECS instance. For more information, see View instance information.
  • Your standalone instance and the ECS instance reside in virtual private clouds (VPCs). You can view the network type of a created ECS instance. For more information, see View instance information. If the ECS instance resides in the classic network, you can migrate the ECS instance from the classic network to a VPC. For more information, see Migrate ECS instances from the classic network to a VPC.

Limits

  • Standalone instances are supported only for MongoDB 4.0 and MongoDB 3.4.
  • Standalone instances do not support incremental data migration and synchronization or point-in-time data restoration.
  • Standalone instances support only the single-zone deployment method and can be created only in the following regions.
    Note
    • For example, Hangzhou Zone F supports the single-zone deployment method, and Hangzhou Zones (B + E + F) support the multi-zone deployment method.
    • For more information about regions and zones, see Regions and zones.
    Region Single-zone deployment
    China (Hangzhou) Hangzhou Zone G, H, I, or J
    China (Shanghai) Shanghai Zone B, D, or G
    China (Qingdao) Qingdao Zone B or C
    China (Beijing) Beijing Zone E, F, or H
    China (Shenzhen) Beijing Zone A, C, or E
    Singapore (Singapore) Singapore Zone A, B, or C

Billing

ApsaraDB for MongoDB supports the subscription and pay-as-you-go billing methods. You can select a billing method based on your business requirements.
  • 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 configurations of the instance. Fees are automatically deducted from your Alibaba Cloud account.

For more information, see Billable items and pricing.

Procedure

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

  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. On the Replica Set Instances page, click Create Instance.
  4. Click the Replica Set (Subscription) tab or the Replica Set (Pay-as-you-go) tab.
  5. Configure the following parameters.
    Parameter Description
    Region The region where the standalone instance is deployed. For more information about the regions that are supported by standalone instances, 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 when you select a region.
    • If your application is deployed on an ECS instance, the standalone instance and the ECS instance must belong to the same region. 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 the standalone instance is deployed. For more information about the zones that are supported by standalone instances, see the Limits section of this topic.
    Note If your application is deployed on an ECS instance, we recommend that you make sure that the standalone instance and the ECS instance belong to the same zone. This reduces network latency.
    Database Version The MongoDB version of the standalone instance. Valid values:
    • MongoDB 4.0
    • MongoDB 3.4
    Storage Engine The storage engine of the standalone instance. Set the value to WiredTiger.
    Nodes The number of nodes in the standalone instance. Set the value to Single Node.
    Read-only Nodes The number of read-only nodes in the standalone instance. Set the value to No Read-only Node.
    Network Type The network type of the standalone instance. Set the value to VPC.
    Note
    • A 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 resides within a VPC. This ensures network connectivity between your application and the standalone instance.
    VPC The ID of the VPC to which the standalone instance belongs. 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 belongs. If no vSwitches are available, you can create a vSwitch in the VPC console. For more information, see Work with vSwitches.
    Specification The number of cores and memory space of the standalone instance. For more information about the specifications that are supported by standalone instances, see Instance types.
    Storage Space The storage space of the standalone instance.
    Note The storage space stores the data, system, and log files of the standalone instance.
    Set Password The time at which you want to set the password of the root user. Valid values:
    • Set Now: You want to immediately set the password of the root user.
    • Set Later: You want to set the password of the root user after the standalone instance is created. For more information, see (Optional) Reset a password.
    Password The password of the root user. If you set the Set Password parameter to Set Now, you must set the password of the root user in compliance with the following rules:
    • The password must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters. Special characters include

      !@#$%^&*()_+-=

    • The password must be 8 to 32 characters in length.
    Duration The subscription period of the standalone instance. This parameter appears only when you specify to create a subscription instance. Valid monthly subscription periods range from one month to nine months. Valid yearly subscription periods range 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. Purchase the standalone instance based on the billing method of the instance.
    Billing method Procedure
    Subscription
    1. Confirm the parameter settings and click Buy Now.
    2. 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.
    3. 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
    1. Confirm the parameter settings and click Buy Now.
    2. 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.
    3. Click Activate Now. The system collects the amount due within the next hour.
  7. Check whether the standalone instance has been created.
    1. After you complete the payment, click Console to go to the ApsaraDB for MongoDB console.
    2. In the top navigation bar, select the resource group and region to which the standalone 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 minutes 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.
        Possible cause Solution
        The standalone instance does not belong to the region that you select. In the top navigation bar 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 architecture of instance 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 a refund.

        After you confirm the refund, perform one of the following operations:
        • Select a different zone and try again.
        • Submit a ticket. To submit a ticket, go to the New Ticket page.

Pay for orders in the cart

If you want to purchase a subscription standalone instance, you can also click Add to Cart to pay for orders in the cart in a lump sum after you complete the parameter settings. You can perform the following steps to pay for orders in the cart:
  1. In the lower-right corner of the page, click the Cart icon.
  2. In the Cart panel, select the products that you want to buy and click Proceed to Checkout.
  3. On the Cart page, check whether the products that you want to buy are selected.
    Note You can also re-specify the Subscription Cycle and Quantity parameters.
    • If the products that you want to buy are selected, click Buy Now.
    • If the products that you want to buy are not selected, select them and click Buy Now.
  4. On the Confirm Order page, read MongoDB Replica Set (Subscription) Service Agreement, select I have read and agreed to the terms, and then click Confirm Purchase.
  5. On the Purchase page, complete the payment as instructed.

Related API operations

Operation Description
CreateDBInstance
  • Creates an ApsaraDB for MongoDB standalone instance or replica set instance.
  • Clones an ApsaraDB for MongoDB standalone instance or replica set instance.
DescribeInstanceAutoRenewalAttribute Queries whether auto-renewal is enabled for an ApsaraDB for MongoDB instance.
DescribeDBInstanceAttribute Queries the detailed information of an ApsaraDB for MongoDB instance.

What to do next

After the standalone instance is created, perform the following operations: