All Products
Search
Document Center

ApsaraDB for MongoDB:Create a standalone instance

Last Updated:Nov 26, 2025

A standalone instance of ApsaraDB for MongoDB is a cost-effective solution for storing non-core data. It is ideal for development, testing, learning, and training purposes. This topic describes how to create a standalone instance.

Prerequisites

You have created an Alibaba Cloud account. For more information, see Step 1: Create an Alibaba Cloud account.

Important

  • Standalone instances have a long fault recovery time and are not covered by a Service-Level Agreement (SLA).

  • If your application is deployed on an ECS instance, ensure that the ApsaraDB for MongoDB instance and the ECS instance meet the following conditions to maintain 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.

    • Your ApsaraDB for MongoDB instance and ECS instance use the same network type.

      Note
      • The same zone is recommended because the same zone reduces network latency.

      • 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 the VPC network type, 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

  • Not all regions and zones support standalone instances. For more information about the supported regions and zones, see Supported regions and zones.

  • To use standalone instances that run MongoDB 4.2 or later, you must submit a ticket to request access.

  • ApsaraDB for MongoDB 3.4 and 4.0 support the creation of standalone instances by default.

    Important Instances that run MongoDB 3.4 have been unavailable as of January 1, 2023. For more information, see [Notice] End of sale for MongoDB 3.4 instances as of January 1, 2023.
  • Standalone instances do not support incremental data migration, data synchronization, or point-in-time recovery.

Billing

You have an Alibaba Cloud account. For more information, see Sign up for an Alibaba Cloud account.

  • 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 billed per hour based on the configuration of the instance. Fees are automatically deducted from your Alibaba Cloud account.

Note

For more information about billing, see Billing items and pricing.

Procedure

ApsaraDB for MongoDB automatically configures the database after you complete these steps. No manual installation or deployment is required.

  1. Log on to the ApsaraDB for MongoDB console.

  2. In the navigation pane on the left, click Replica Set Instances.

  3. On the Replica Set Instances page, click Create Instance.

  4. In the Product Type section, select either Replica Set (Subscription) or Replica Set (Pay-as-you-go).

  5. Configure the following parameters for the standalone instance.

    Parameter

    Description

    Region

    Select the region where the instance resides. For information about the regions that support standalone instances, see Limits.

    Note
    • You cannot change the region after the instance is created. Select a region with care.

    • If your application is deployed on an ECS instance, select the same region as the ECS instance. Otherwise, the instances cannot communicate over the internal network.

    Zone

    Select the zone where the instance resides. For information about the zones that support standalone instances, see Limits.

    Note

    If your application is deployed on an ECS instance, select the same zone as the ECS instance to reduce network latency.

    Engine Version

    Select a database version as needed.

    Active-standby Nodes

    Select Single Node.

    Read-only Nodes

    This is fixed at No Read-only Nodes.

    Storage Engine

    This is fixed at WiredTiger.

    Storage Type

    This is fixed at PL1 ESSD.

    Network Type

    This is fixed at VPC.

    Note
    • A virtual private cloud (VPC) is an isolated network environment that provides higher security and better performance than the classic network.

    • If your application is deployed on an ECS instance, make sure that the network type of the ECS instance is VPC to ensure network connectivity.

    VPC

    Select the VPC where the instance resides. If you do not have a VPC available, you can create one in the VPC console. For more information, see Create and manage a VPC.

    vSwitch

    Select the vSwitch to which the instance belongs. If you do not have a vSwitch available, you can create one in the VPC console. For more information, see Create and manage a vSwitch.

    Instance Type

    Select the CPU and memory specifications for the instance. For information about the instance types supported by standalone instances, see Instance types.

    Storage

    Select the storage space for the instance.

    Note

    The storage space includes your data files, system files, and log files.

    user_name

    This is fixed at root.

    Note

    This is the root account for the admin database. For more information about the permissions of the root account, see What permissions does the root account have?.

    Set Password

    Set the password for the root account. You can select one of the following methods:

    • Set Now: Set the password immediately.

    • Set After Creation: Set the password after the instance is running. For more information, see (Optional) Reset a password.

    Password

    If you choose to set the password now, set the password based on 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 are:

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

    • The password must be 8 to 32 characters in length.

    Duration

    If you create a subscription instance, select a subscription duration. You can select a duration from 1 to 9 months, or 1 Year, 2 Years, 3 Years, or 5 Years.

    Note

    If you want the instance to be automatically renewed upon expiration, select Auto-renewal and make sure that your account has a sufficient balance before the instance expires.

    Quantity

    Select the number of instances with the same configuration. The supported integer range varies based on the product type:

    • Subscription: 1 to 20

    • Pay-as-you-go: 1 to 10

  6. Complete the purchase based on the selected billing method.

    Billing Method

    Procedure

    Subscription

    1. After you complete the configuration, click Buy Now.

    2. On the Confirm Order page, check the configuration details and read the Terms of Service.

    3. Click Pay and complete the payment process on the Payment page.

    Note

    You can also click Add To Cart to pay for the instance along with other products. For more information, see Check out with the shopping cart.

    Pay-as-you-go

    1. After you complete the configuration, click Buy Now.

    2. On the Confirm Order page, check the configuration details and read the Terms of Service.

    3. Click Activate Now. The system automatically deducts the fees in the next hour.

  7. Verify that the instance is created.

    1. After the payment is complete, click Management Console to go to the ApsaraDB for MongoDB console.

    2. In the upper-left corner of the page, select the resource group and region where the instance resides.

    3. Verify that the created instance appears in the replica set instance list.

      • If the instance is listed and its status is Running, it has been created successfully.

      • If the instance is not listed, wait 10 to 15 minutes and then refresh the page. If the instance still does not appear, check for the possible causes in the following table. If the issue persists, contact Alibaba Cloud technical support.

        The following table describes possible causes and solutions.

        Possible Cause

        Solution

        Incorrect region selected

        In the upper-left corner of the ApsaraDB for MongoDB console, select the resource group and region where the instance resides.

        Incorrect instance list selected

        In the navigation pane on the left of the ApsaraDB for MongoDB console, select Replica Set Instances.

        Insufficient resources

        The newly created instance may be refunded due to insufficient resources.

        After you confirm the refund, try to purchase the instance again in a different zone.

Check out with the shopping cart

If you purchase a subscription instance, you can click Add To Cart after you complete the configuration to add it to your shopping cart and pay for it with other products. The procedure is as follows.

  1. Click Shopping Cart on the right side of the page.

  2. In the Shopping Cart panel, select the products that you want to purchase and click Proceed To Checkout.

  3. On the Shopping Cart page, confirm that your selected products are correct.

    Note

    You can also adjust the Subscription Duration and Quantity for the ApsaraDB for MongoDB instance.

    • If the order is correct, click Buy Now.

    • If the order is incorrect, make the necessary corrections and then click Buy Now.

  4. On the Confirm Order page, read the Terms of Service, and click Pay.

  5. On the Payment page, follow the prompts to complete the payment process.

Related API operations

API operation

Description

CreateDBInstance

  • Create an ApsaraDB for MongoDB standalone or replica set instance.

  • Clone an ApsaraDB for MongoDB standalone or replica set instance.

DescribeInstanceAutoRenewalAttribute

Query whether auto-renewal is enabled for an ApsaraDB for MongoDB instance.

DescribeDBInstanceAttribute

Query the details of an ApsaraDB for MongoDB instance.

What to do next

After the instance is created, you must also perform the following operations.

  • Configure a whitelist for the instance to allow external devices to access it. For more information, see Configure a whitelist.

  • Optional: If you did not set a password when you created the instance, set a password. For more information, see (Optional) Reset a password.

  • Optional: To connect to the instance over the Internet, you must first apply for a public endpoint. For more information, see (Optional) Apply for a public endpoint.