ApsaraDB RDS:Create an ApsaraDB RDS for MariaDB instance

Prerequisites

The AliyunRDSFullAccess and AliyunBSSOrderAccess policies are attached to the RAM user that you use to create an RDS instance. For more information, see Use RAM for resource authorization.

Procedure

Step 1: Configure basic settings

1. Go to the ApsaraDB RDS buy page.

2. Configure the Billing Method parameter.

   Billing method	Description	Benefit
   Subscription	A subscription instance is an instance for which you pay an upfront fee. If you want to use an instance for a long period of time, we recommend that you select the Subscription billing method. If you select the subscription billing method, configure the Duration parameter in the lower part of the page.	The subscription billing method is more cost-effective than the pay-as-you-go billing method. You are offered lower prices for longer subscription durations.
   Pay-as-you-go	You are charged on an hourly basis for a pay-as-you-go RDS instance based on your actual resource usage. If you want to use an RDS instance for a short period of time, we recommend that you select the pay-as-you-go billing method. You can create a pay-as-you-go RDS instance. After you confirm that the created RDS instance meets your business requirements, you can change the billing method of the RDS instance to subscription.	You can release a pay-as-you-go RDS instance based on your business requirements. The billing cycle of a pay-as-you-go RDS instance immediately stops after you release the instance.

   Note

   You can view the price in the lower-right corner of the page. The price is displayed only after you configure all required parameters.

3. Configure the Region parameter.

   We recommend that you create the RDS instance in the same region as the Elastic Compute Service (ECS) instance on which your application is deployed. If the RDS instance and the ECS instance reside in different regions, these instances cannot communicate over an internal network. As a result, these instances cannot deliver optimal performance.

   Note

   • After an RDS instance is created, you cannot change the region of the RDS instance. If an ECS instance connects to an RDS instance over an internal network, make sure that the RDS instance and the ECS instance reside in the same region.

   • If your application is deployed on an on-premises server or computer, we recommend that you select a region that is near your on-premises server or computer. This way, you can use the public endpoint of the RDS instance to connect to the RDS instance from your application.

4. Configure the Database Engine and Storage Type parameters.

   Note

   • You can set the Edition parameter only to High-availability Edition. In RDS High-availability Edition, your database system consists of a primary RDS instance and a secondary RDS instance. These instances work in a high availability architecture. RDS High-availability Edition is suitable for more than 80% of production environments.

   • You can set the Product Type parameter only to Standard.

   1. Configure the Database Engine parameter.

      Select MariaDB.

      Only MariaDB 10.3 is supported.

   2. Configure the Storage Type parameter.

      Item	ESSD
      Scalability	You can increase the storage capacity up to 32 TB. No transient connections occur during storage capacity expansion. You can upgrade, downgrade, create, or release the RDS instance within minutes. Automatic storage expansion is supported.
      Performance	PL1<PL2<PL3 A performance level 2 (PL2) enhanced SSD (ESSD) delivers twice the IOPS and throughput of a PL1 ESSD. A PL3 ESSD delivers IOPS that is up to 20 times the IOPS delivered by a PL1 ESSD. A PL3 ESSD also delivers throughput that is up to 11 times the throughput delivered by a PL1 ESSD.
      Backup	A backup can be completed within minutes or seconds. The highest backup frequency is once every 15 minutes.

      Note

      • You can select Disk Encryption to ensure data security. For more information, see Configure cloud disk encryption.

      • For more information about storage types, see Storage types.

5. Select the zone in which the RDS instance resides.

   • Select a zone.

     • No significant differences exist between the zones in the same region.

     • If the RDS instance resides in the same zone as the ECS instance on which your application is deployed, these instances can deliver the optimal performance. If the RDS instance and the ECS instance reside in different zones in the same region, the performance of the RDS instance and the ECS instance is slightly lower than the performance of the RDS instance and the ECS instance that reside in the same zone.

   • Select a deployment method.

     • Multi-zone Deployment: This is the recommended deployment method. The primary RDS instance and the secondary RDS instance reside in different zones to provide zone-disaster recovery.

     • Single-zone Deployment: The RDS instance and the secondary RDS instance reside in the same zone.

6. Configure the Instance Type parameter.

   1. Configure the Category parameter. You can select General-purpose or Dedicated.

      Category	Description	Benefit
      General-purpose instance family	A general-purpose RDS instance occupies all the allocated memory and I/O resources. A general-purpose RDS instance shares CPU and storage resources with the other general-purpose RDS instances that are deployed on the same host.	General-purpose RDS instances are cost-effective.
      Dedicated instance family	A dedicated RDS instance occupies all the allocated CPU, memory, storage, and I/O resources. Note The dedicated host instance family is the highest configuration of the dedicated instance family. A dedicated host RDS instance exclusively occupies all the CPU, memory, storage, and I/O resources of the host on which the RDS instance is deployed.	A dedicated RDS instance provides higher performance and higher stability. Note An RDS instance that runs RDS Basic Edition does not support the dedicated instance family.

   2. Configure detailed specifications, including cores and memory capacity.

      Note

      For more information, see Instance types.

7. Configure the Capacity parameter.

   The value range varies based on the instance type and storage type that you select.

   You can adjust the storage capacity at a step size of 5 GB.

8. Optional. If you set the Billing Method parameter to Subscription, configure the Duration parameter based on your business requirements.

9. In the lower-right corner of the page, click Next: Instance Configuration.

Step 2: Configure advanced settings

1. Configure the Network Type parameter.

   1. This parameter is fixed as VPC.

   2. Configure the VPC and vSwitch of Primary Node parameters.

      We recommend that you select the virtual private cloud (VPC) in which your ECS instance resides for the RDS instance. If the RDS instance and the ECS instance reside in different VPCs, these instances cannot communicate over an internal network.

      Note

      If you set the Deployment Method parameter to Multi-zone Deployment in the Basic Configurations step, you must also configure the vSwitch of Secondary Node parameter.

   3. Configure the Add to Whitelist parameter to specify whether to add the CIDR block of the selected VPC to a whitelist of the RDS instance.

      If you select Yes for the Add to Whitelist parameter, the ECS instances that reside in the selected VPC can access the RDS instance.

      Note

      If you select No for the Add to Whitelist parameter, you can configure a whitelist after the RDS instance is created. For more information, see Configure an IP address whitelist.

   4. Configure the Port parameter.

      Valid values: 1000 to 5999. You can initialize the port when you create an RDS instance.

2. Configure the Release Protection parameter.

   If you set the Billing Method parameter to Pay-As-You-Go, you can select Release Protection for the RDS instance to prevent the RDS instance from being released due to unintended operations. For more information, see Enable or disable the release protection feature for an ApsaraDB RDS for MySQL instance.

3. Configure the Resource Group parameter.

   The resource group to which the RDS instance belongs. You can retain the default resource group or select a custom resource group based on your business requirements.

4. Configure the Privileged Account parameter.

   You can create a privileged account when you create the RDS instance. If you select Later, you can create a privileged account after the RDS instance is created.

   Note

   • Each RDS instance can have only one privileged account. The privileged account cannot be deleted.

   • For more information about privileged accounts and how to create privileged accounts, see Create a database and an account on an ApsaraDB RDS for MariaDB instance.

5. In the lower-right corner of the page, click Next: Confirm Order.

Step 3: Confirm the order

1. Confirm the configuration of the RDS instance in the Parameters section, configure the Purchase Plan and Duration parameters, read and select Terms of Service, and then click Pay Now. You must configure the Duration parameter only when you select the subscription billing method for the RDS instance.

   Note

   If you select the subscription billing method for the RDS instance, we recommend that you select Auto-Renew Enabled. This prevents interruptions on your workloads even if you forget to renew the RDS instance.

   The Congratulations. or "The service is activated message is displayed in the ApsaraDB RDS console.

2. View the new RDS instance.

   Go to the Instances page. In the top navigation bar, select the region in which your RDS instance resides. Then, find the RDS instance based on the Creation Time parameter.

   Note

   The system requires 1 to 10 minutes to create an RDS instance. You can refresh the page to view the RDS instance that you created.

What to do next

• Configure an IP address whitelist

• Create a database and an account on an ApsaraDB RDS for MariaDB instance

• Apply for or release a public endpoint

• Connect to an ApsaraDB RDS for MariaDB instance

FAQ

After I create an RDS instance, why does the ApsaraDB RDS console not respond and why am I unable to find the RDS instance?

References

• For more information about how to create an RDS instance by calling an operation, see Create an instance.

• For more information about how to create an RDS instance that runs a different database engine, see the following topics:

  • Create an ApsaraDB RDS for MySQL instance

  • Create an ApsaraDB RDS for SQL Server instance

  • Create an ApsaraDB RDS for PostgreSQL instance