ApsaraDB for MongoDB:Create an ApsaraDB for MongoDB standalone instance

Usage notes

• Standalone instances take a long time to recover from failures and cannot be covered by a Service Level Agreement (SLA).

• If your application is deployed on an Elastic Compute Service (ECS) instance, make sure that your ApsaraDB for MongoDB instance and the ECS instance meet the following requirements to ensure network connectivity. For more information about how to view the information of an ECS instance, 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 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 deployed only in specific regions and zones. For more information about the supported regions and zones, see Available regions and zones.

• Standalone instances can run only MongoDB 4.0.

  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, incremental data synchronization, or point-in-time data restoration by creating an instance.

Billing rules

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

• 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. On the page that appears, set Product Type to Replica Set (Subscription) or Replica Set (Pay-as-you-go).

5. Configure the parameters described in the following table.

   Parameter	Description
   Region	The region in which you want to deploy the standalone instance. For more information about the regions in which you can create standalone instances, see Limits. Note After you create the standalone instance, you cannot change the region of the instance. Proceed with caution. If your application is deployed on an 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 reside in different regions, your application cannot communicate with the standalone instance over an internal network.
   Zone Type	Select Single-zone.
   Zone	The zone in which you want to deploy the standalone instance. For more information about the zones in which you can create standalone instances, see Limits. 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. Note Standalone instances can run only MongoDB 4.0.
   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. Set the value to No Read-only Node.
   Storage Engine	The storage engine of the standalone instance. Set the value to WiredTiger.
   Storage Type	Select the storage type that is used for the new RDS instance.
   Network Type	The type of network in which you want to deploy the standalone instance. Set the value 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 deployed in a VPC. This ensures network connectivity between your application and the standalone instance.
   VPC	The ID of the VPC in which 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 is connected. If no vSwitches are available, you can create a vSwitch in the VPC console. For more information, see Create and manage a vSwitch.
   Category	The category of the standalone instance. You can set this parameter only to General-purpose for the standalone instance.
   Specifications	The number of 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	Set the value to root. Note For more information about the root account of the admin database and the permissions of the root account, see What permissions are the root account granted when an instance is created? in which the RDS instance resides.
   Set Password	The time when you want to set the password of the root account. Valid values: Set Now: specifies to set the password of the root account immediately. Set Later: specifies 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. The following special characters are supported: !@#$%^&*()_+-= The password must be 8 to 32 characters in length.
   Tag	The tag that you want to add to the standalone instance.
   Duration	The subscription duration of the standalone instance. This parameter is displayed only when you create a subscription instance. 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 with the current specifications. The valid values of this parameter vary with the billing method of the instances. Valid values for subscription instances: 1 to 20. Valid values for pay-as-you-go instances: 1 to 10.

6. Pay for the standalone instance based on the billing method of the instance.

   Billing method	Operation
   Subscription	After you complete the parameter settings, 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 the "Pay for orders in the cart" section in the Create a standalone instance topic.
   Pay-as-you-go	After you complete the parameter settings, 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 has been 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 runs as expected.

      • 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.

        Possible 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 use 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 standalone instance due to insufficient resources. In this case, your payment is refunded. After you confirm that the payment is refunded, you can create an instance in another zone.

Pay for the orders in the cart

Related API operations