This topic describes how to create ApsaraDB for MongoDB standalone instances. 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 standalone instances in the ApsaraDB for MongoDB console.

Prerequisites

  • You are registered with Alibaba Cloud. For more information, see Sign up with Alibaba Cloud.
  • If you want to create standalone instances that are charged based on the pay-as-you-go billing method, the balance in your Alibaba Cloud account is sufficient.

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 belong to the same region. You can view the region of a created ECS instance. For more information, see View instance information.
  • Optional:Your standalone instance and the ECS instance belong to the same zone. This reduces network latency. You can view the 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 an ECS instance 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: China (Hangzhou), China (Shanghai), China (Shenzhen), China (Qingdao), China (Beijing), and Singapore (Singapore).
    Note
    • For example, Hangzhou Zone F supports the single-zone deployment method, and Hangzhou Zones (B+E+F) supports the multi-zone deployment method.
    • In the China (Beijing) region, standalone instances can be created only in Zone A, Zone B, Zone C, Zone D, Zone E, Zone F, Zone G, and Zone H.
    • For more information about regions and zones, see Regions and zones.

Pricing

ApsaraDB for MongoDB supports the subscription billing method and the pay-as-you-go billing method. 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 configuration 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 standalone instances. No manual intervention is 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 the Replica Set (Subscription) tab or the Replica Set (Pay-as-you-go) tab.
  5. Configure the following parameters.
    Section Parameter Description
    Basic Configuration Region

    The region to which the standalone instances belong. For more information about the regions that are supported by standalone instances, see the "Limits" section of this topic.

    Note
    • After the standalone instances are created, you cannot change the region of the instances. Proceed with caution when you select a region.
    • If your application is deployed on an ECS instance, the standalone instances and the ECS instance must belong to the same region. If the standalone instances and the ECS instance belong to different regions, your application cannot communicate with the standalone instances over an internal network.
    Zone The zone to which the standalone instances belong.
    Note If your application is deployed on an ECS instance, we recommend that you make sure that the standalone instances and the ECS instance belong to the same zone. This helps you reduce network latency.
    Database Version The MongoDB version of the standalone instances. Valid values:
    • MongoDB 4.0
    • MongoDB 3.4
    Storage Engine

    The storage engine of the standalone instances. Select WiredTiger.

    Nodes The number of nodes in each standalone instance. Select Single Node.
    Network Type Network Type The type of network in which the standalone instances reside. Select 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 in a VPC. This ensures network connectivity between your application and the standalone instances.
    VPC ID The ID of the VPC to which the standalone instances belong. If no VPCs are available, you can create a VPC in the VPC console. For more information, see Work with VPCs.
    VSwitch ID The ID of the vSwitch to which the standalone instances belong. If no vSwitches are available, you can create a vSwitch in the VPC console. For more information, see Work with vSwitches.
    Specifications Specification The number of cores and memory capacity that are configured for each standalone instance. For more information about the specifications that are supported by standalone instances, see Instance types.
    Storage Space The storage capacity of each standalone instance.
    Note The storage capacity is used to store your data files, system files, and log files.
    Set Password Set Password The time when you want to set the password of the root account. Valid values:
    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 in compliance with the following rules in this step:
    • The password must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters. The password can contain the following special characters:

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

    • The password must be 8 to 32 characters in length.
    Purchase Quantity Duration The subscription period of the standalone instances. This parameter appears only for standalone instances that are charged based the subscription billing method. Valid monthly subscription periods range from one month to nine months. Valid yearly subscription periods range from one year to three years.
    Quantity The number of standalone instances that you want to create. All the created standalone instances have the same specifications. Valid values: 1 to 20.
  6. Confirm the order and complete the payment.
    1. Confirm the parameter settings and click Buy Now.
    2. On the Confirm Order page, confirm the parameter settings, read and select ApsaraDB for MongoDB Agreement of Service, and then complete the payment.
  7. Check whether the standalone instances are 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 instances belong.
    3. In the left-side navigation pane, click Replica Set Instances.
    4. In the instance list that appears, check whether the standalone instances that you created are displayed.
      • If the standalone instances are displayed, the instances are created. If the standalone instances are in the Running state, the instances are running.
      • If the standalone instances are not displayed, wait for 10 minutes to 15 minutes. Then, refresh the page. If the standalone instances are 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 instances are not displayed.
        Possible cause Solution
        The standalone instances do 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 instances belong.
        The standalone instances do not belong to the type of instance that you select. In the left-side navigation pane of the ApsaraDB for MongoDB console, click Replica Set Instances.
        The standalone instances are 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 Submit a ticket.

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 details about an ApsaraDB for MongoDB instance.

What to do next

After standalone instances are created, perform the following operations:
  • Optional:If you did not set the password of the root user for the standalone instances when you created the instances, set the password of the root user. For more information, see Reset the password.
  • Configure IP address whitelists for the standalone instances. The IP address whitelists of a standalone instance contain the IP addresses or CIDR blocks that are granted access to the standalone instance. For more information, see Configure a whitelist for an ApsaraDB for MongoDB instance.
  • Optional:If you want to connect to a standalone instance over the Internet, apply for a public endpoint for the standalone instance. For more information, see Apply for a public endpoint for an ApsaraDB for MongoDB instance.