Updated at: 2022-05-07 GMT+08:00

Step 1: Buy a DB Instance

Scenarios

This section describes how to create a DB instance on the RDS console.

Currently, RDS for PostgreSQL supports the yearly/monthly and pay-per-use billing modes. RDS allows you to tailor your computing resources and storage space to your business needs.

Prerequisites

  • You have registered a HUAWEI CLOUD account.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Database > Relational Database Service. The RDS console is displayed.
  4. On the Instance Management page, click Buy DB Instance.
  5. On the displayed page, configure information about your DB instance. Then, click Next.

    RDS provides the following billing modes:

    Yearly/Monthly

    If you select this billing mode, skip 6 and go to 7.

    Pay-per-use

    If you select this billing mode, go to 6.

    Table 1 Basic information

    Parameter

    Description

    Region

    Region where the tenant is located.

    NOTE:

    Products in different regions cannot communicate with each other through a private network and you cannot change the region of a DB instance after creating the instance. Therefore, exercise caution when selecting a region.

    DB Instance Name

    Different DB instances can have the same name. The instance name must start with a letter and consist of 4 to 64 bytes. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.

    • If you intend to create multiple DB instances, the allowed length for each instance name will change.
    • If you buy multiple DB instances at a time, they will be named instance-0001, instance-0002, and so on. (instance indicates the DB instance name you specify.)

    DB Engine

    Set to PostgreSQL.

    DB Engine Version

    For details, see DB Engines and Versions.

    Different DB engine versions are supported in different regions.

    You are advised to select the latest available version because it is more stable, reliable, and secure.

    DB Instance Type

    • Primary/Standby: uses an HA architecture with a primary DB instance and a synchronous standby DB instance. It is suitable for production databases of large- and medium-sized enterprises in Internet, Internet of Things (IoT), retail e-commerce sales, logistics, gaming, and other sectors. The standby DB instance improves instance reliability and is invisible to you after being created.

      An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network. Some regions support both single AZs and multiple AZs and some only support single AZs.

      To achieve higher reliability, RDS will automatically deploy your primary and standby instances in different physical servers even if you deploy primary/standby DB instances in the same AZ. If you attempt to create primary/standby DB instances in the same AZ in a Dedicated Computing Cluster (DCC) and there is only one physical server available, the creation will fail.

      You can deploy primary and standby DB instances in a single AZ or across AZs to achieve failover and high availability.

    • Single: uses a single-node architecture, which is more cost-effective than primary/standby DB instances. It is suitable for development and testing of microsites, and small- and medium-sized enterprises, or for learning about RDS.

    Storage Type

    Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

    • Ultra-high I/O: supports a maximum throughput of 350 MB/s.
    • Cloud SSD: stores data in cloud SSDs to achieve decoupled compute and storage.
    • Extreme SSD: uses the 25GE network and RDMA technology to provide you with up to 1 million random read/write performance per disk and low latency per channel.
    NOTE:
    • The cloud SSD storage type is supported only with general-purpose and dedicated DB instances.
    • The extreme SSD storage type is supported only with dedicated DB instances.
    • To use extreme SSDs, contact customer service to apply for the required permissions.
    • If you have purchased the Dedicated Distributed Storage Service (DSS), only the storage type that you have selected when you buy the DSS service is displayed.

    Time Zone

    You need to select a time zone for your instance based on the region hosting your instance. You can select a time zone during instance creation and change it later.

    Table 2 Instance specifications

    Parameter

    Description

    Instance Class

    Refers to the CPU and memory of a DB instance. Different instance classes have different numbers of database connections and different maximum IOPS.

    After a DB instance is created, you can change its CPU and memory. For details, see Changing a DB Instance Class.

    NOTE:

    DB instances in a DCC only support the general-enhanced instance class.

    Resource Type

    • EVS
    • DSS
      NOTE:

      This option is displayed only when you buy the DSS service.

    Storage Pool

    Displayed only when you select DSS for Resource Type. The storage pool is secure because it is physically isolated from other pools.

    Storage Space (GB)

    Contains the file system overhead required for inode, reserved block, and database operation. Storage space can range in size from 40 GB to 4,000 GB and can be scaled up only by a multiple of 10 GB.

    After a DB instance is created, you can scale up its storage space. For details, see Scaling up Storage Space.

    Disk Encryption

    • Disable: indicates the encryption function is disabled.
    • Enable: indicates the encryption function is enabled, improving data security but affecting system performance.

      Key Name: indicates the tenant key. You can create or select a key.

      NOTE:
      • Once the DB instance is created, you cannot modify the disk encryption status or change the key. The backup data stored in OBS is not encrypted.
      • After an instance is created, do not disable or delete the key that is being used. Otherwise, the database will be unavailable and data cannot be restored.
      • For details about how to create a key, see Creating a CMK in the Data Encryption Workshop User Guide.
    Table 3 Network

    Parameter

    Description

    VPC

    A dedicated virtual network in which your RDS DB instances are located. A VPC can isolate networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.

    If no VPC is available, RDS allocates a VPC to you by default.

    NOTICE:

    After the DB instance is created, the VPC cannot be changed.

    Subnet

    Improves network security by providing dedicated network resources that are logically isolated from other networks. Subnets take effect only within an AZ. The Dynamic Host Configuration Protocol (DHCP) function is enabled by default for subnets in which you plan to create RDS DB instances and cannot be disabled.

    A floating IP address is automatically assigned when you create a DB instance. You can also enter an unused floating IP address in the subnet CIDR block. After the DB instance is created, you can change the floating IP address.

    Security Group

    Controls the access that traffic has in and out of a DB instance. By default, the security group associated with the DB instance is authorized.

    Enhances security by controlling access to RDS from other services. You need to add inbound rules to a security group so that you can connect to your DB instance.

    If no security group is available, RDS allocates a security group to you by default.

    Table 4 Database configuration

    Parameter

    Description

    Password

    • Configure (default setting): Configure a password for your DB instance during the creation process.
    • Skip: Configure a password later after the DB instance is created.
      NOTICE:

      To log in, you will have to reset a password for the DB instance.

      After a DB instance is created, you can reset the password. For details, see Resetting the Administrator Password.

    Administrator

    The default login name for the database is root.

    Administrator Password

    Must consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?,). Enter a strong password and periodically change it for security reasons.

    Keep this password secure. The system cannot retrieve it.

    After a DB instance is created, you can reset this password. For details, see Resetting the Administrator Password.

    Confirm Password

    Must be the same as Administrator Password.

    Parameter Template

    Contains engine configuration values that can be applied to one or more DB instances. If you intend to create primary/standby DB instances, they use the same parameter template.

    NOTICE:

    If you use a custom parameter template when creating a DB instance, the following specification-related parameters in the custom template are not delivered. Instead, the default values are used.

    • maintenance_work_mem
    • shared_buffers
    • max_connections
    • effective_cache_size

    You can modify the instance parameters as required after the DB instance is created. For details, see section Modifying Parameters in a Parameter Template.

    Enterprise Project

    If your account has been associated with an enterprise project, select the target project from the Enterprise Project drop-down list.

    You can also go to the ProjectMan console to create a project. For details about how to create a project, see the ProjectMan User Guide.

    Table 5 Tags

    Parameter

    Description

    Tag

    Tags an RDS DB instance. This configuration is optional. Adding tags to RDS DB instances helps you better identify and manage the DB instances. A maximum of 10 tags can be added for each DB instance.

    After a DB instance is created, you can view its tag details on the Tags page. For details, see Managing Tags.

    Table 6 Purchase period

    Parameter

    Description

    Required Duration

    This option is available only for yearly/monthly DB instances. The system will automatically calculate the configuration fee based on the selected required duration. The longer the required duration is, the larger discount you will enjoy.

    Auto-renew

    • This option is available only for yearly/monthly DB instances and is not selected by default.
    • If you select this option, the auto-renew cycle is determined by the selected required duration.

    Quantity

    RDS supports batch creation of DB instances. If you intend to create primary/standby DB instances and set Quantity to 1, a primary DB instance and a synchronous standby DB instance will be created.

    If you have any questions about the price, click Pricing details at the bottom of the page.

    The performance of your DB instance depends on its configurations. Hardware configuration items include the instance specifications, storage type, and storage space.

  6. Confirm the specifications for pay-per-use DB instances.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.

    Skip 7 and 8 and go to 9.

  7. Confirm the order for yearly/monthly DB instances.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Pay Now.

  8. Select a payment method and complete the payment.

    This operation applies only to the yearly/monthly billing mode.

  9. To view and manage the DB instance, go to the Instance Management page.

    • During the creation process, the DB instance status is Creating. When the creation process is complete, the instance status will change to Available.
    • The automated backup policy is enabled by default. After the DB instance is created, you can modify the policy as needed. An automated full backup is immediately triggered after a DB instance is created.
    • After a DB instance is created, you can enter a description for it.
    • The default database port is 5432. After a DB instance is created, you can change the database port.

      You are advised to change the database port in a timely manner.

      For details, see Changing a Database Port.

close