ApsaraDB for MongoDB:Create a single-node instance

Usage notes

• Single-node instances have a longer 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 for network connectivity. For information about how to view ECS instance details, see View instance information.

  • They are in the same region.

  • They use the same network type.

    Note

    • To reduce network latency, place the instances in the same availability zone.

    • A VPC is recommended for its higher security.

    • If you use a VPC, both instances must be in the same VPC.

    • If you want to use a VPC but your ECS instance is in the classic network, you can migrate the ECS instance to a VPC. For more information, see Migrate an ECS instance from the classic network to a VPC.

Limitations

• Not all regions and zones support single-node instances. For supported regions, see Supported regions and availability zones.

• ApsaraDB for MongoDB versions 3.4 and 4.0 support single-node instances by default.

• Single-node instances do not support incremental data migration and 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: A prepaid billing method where you pay for the instance upon creation.

• Pay-as-you-go: a postpaid billing method where you are billed hourly based on the instance configuration. Fees are automatically deducted from your account balance.

Procedure

ApsaraDB for MongoDB automatically provisions the database after you complete these steps. No manual installation 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 Replica Set (Subscription) or Replica Set (Pay-as-you-go).

5. Configure the following parameters for the single-node instance.

   Parameter	Description
   Region	Select the region for the instance. For supported regions, see Limitations. Note The region cannot be changed after creation. If your application runs on ECS, select the same region to enable internal network connectivity.
   Zone	Select the zone for the instance. For supported zones, see Limitations. Note If your application runs on ECS, select the same zone to reduce latency.
   Database Version	Select a database version.
   Active-standby Nodes	Select Single node.
   Read-only Nodes	Fixed at No Read-only Node.
   Storage Engine	Fixed at WiredTiger.
   StorageType	Fixed at ESSD PL1.
   Network type	Fixed at VPC. Note A VPC is an isolated network that provides better security and performance than the classic network. If your application runs on ECS, ensure its network type is VPC for connectivity.
   VPC	Select the VPC. If no VPC is available, create one in the VPC console. Create and manage a VPC.
   vSwitch	Select the vSwitch. If no vSwitch is available, create one in the VPC console. Create and manage a vSwitch.
   Specifications	Select the instance specifications. For supported types, see Instance types.
   Capacity	Select the storage capacity. Note Storage includes data, system, and log files.
   Username	Fixed at root. Note This is the root account for the admin database. For information about the permissions of the root account, see What permissions does the root account that is specified during instance creation have?.
   Password Settings	Set the password for the root account: Set Now: Set the password immediately. Set Later: Set the password after the instance is running. (Optional) Reset the password.
   Password	Password requirements: Must contain at least three of: uppercase letters, lowercase letters, digits, and special characters. Supported special characters: !@#$%^&*()_+-= Must be 8–32 characters.
   Purchase Duration	For subscription instances, select a duration from 1–9 months, or select 1 Year, 2 Years, 3 Years, or 5 Years. Note To auto-renew upon expiration, select Auto-Renewal. Ensure sufficient account balance before expiration.
   Quantity	Select the number of instances with the same configuration. The allowed number of instances varies based on the product type: Subscription: 1 to 20 Pay-as-you-go: 1 to 10

6. Complete the purchase.

   Billing method	Procedure
   Subscription	Click Buy Now. Review the configuration and terms of service on the Confirm Order page. Click Payment and complete the payment on the Pay page. Note To pay with other products, click Add to Cart. Check out with the shopping cart.
   Pay-as-you-go	Click Buy Now. Review the configuration and terms of service on the Confirm Order page. Click Activate Now. Fees are automatically deducted within the next hour.

7. Verify that the instance was created. Creating an ApsaraDB for MongoDB instance can take a long time. If the creation progress in the console does not change or appears stuck for a long time (for example, stuck at 30%), refresh the browser page to obtain the latest status. In most cases, the instance has already been created, and its running status is displayed after you refresh the page.

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

   2. Select the resource group and region of the instance.

   3. Check whether the new instance appears in the replica set instance list.

      • If the instance appears, it is created. It is ready when its status changes to Running.

      • If not, wait 10–15 minutes and refresh. If still missing, check the following causes. Contact technical support if the issue persists.

        Possible causes and solutions:

        Possible cause	Solution
        Incorrect region selected	Select the correct resource group and region in the console.
        Incorrect instance list selected	In the navigation pane on the left of the ApsaraDB for MongoDB console, click Replica Set Instances.
        Insufficient resources	Creation may fail due to insufficient resources, triggering an automatic refund. After confirming the refund, retry in a different availability zone.

Check out with the shopping cart

Related APIs