Buying a TaurusDB for PostgreSQL Instance

Scenarios

You can on the TaurusDB for PostgreSQL console.

TaurusDB for PostgreSQL only supports the pay-per-use billing mode. You can tailor your compute resources and storage space to your business needs.

Prerequisites

• You have created a Huawei ID and enabled Huawei Cloud services.
• You can create an IAM user or user group on the IAM console and grant it specific operation permissions, to perform refined management on Huawei Cloud. For details, see Creating a User and Granting TaurusDB for PostgreSQL Permissions.

Procedure

1. Go to the Buy DB Instance page.
2. On that page, click the Custom Config tab, select a billing mode, configure parameters about your instance, and click Next.
   • Basic configuration

     Only pay-per-use billing is supported.

   • Resource selection
     Figure 1 Resource selection
     

     Table 1 Basic information

     Parameter	Description
     Region	Region where your resources are located. NOTE: Products in different regions cannot communicate with each other through a private network. After a DB instance is created, the region cannot be changed. Therefore, exercise caution when selecting a region.
     Compatible DB Engine	TaurusDB for PostgreSQL
     Kernel Version	TaurusDB for PostgreSQL 16
     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 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 high reliability, TaurusDB for PostgreSQL will automatically deploy your primary and standby DB instances in different physical servers even if you deploy them in the same AZ. 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 less expensive than primary/standby DB instances. It is suitable for development and testing of microsites, and small- and medium-sized enterprises, or for learning about TaurusDB for PostgreSQL.
     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. Cloud SSD: cloud disks used to decouple storage from compute. Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency. NOTE: The cloud SSD and extreme SSD storage types are supported with general-purpose, dedicated, and Kunpeng general-enhanced DB instances. The IOPS supported by cloud SSDs depends on the I/O performance of Elastic Volume Service (EVS) disks. For details, see the description about ultra-high I/O in Disk Types and Performance of Elastic Volume Service Service Overview. The IOPS supported by extreme SSDs depends on the I/O performance of Elastic Volume Service (EVS) disks. For details, see the description about extreme SSDs in Disk Types and Performance of Elastic Volume Service Service Overview.

   • Instance options
     Figure 2 Specifications and storage
     

     Table 2 Specifications and storage

     Parameter	Description
     Instance Specifications	Refers to the vCPU and memory of a DB instance. Different instance specifications support different numbers of database connections and maximum IOPS.
     Storage Space (GB)	Contains the system overhead required for inodes, reserved blocks, 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.

   • Basic settings and connectivity
     Figure 3 Basic settings and connectivity
     

     Table 3 Network

     Parameter	Description
     DB Instance Name	The instance name must start with a letter and consist of 4 to 64 characters. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.
     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: If you select Skip for Password, you need to reset the password before you can log in to the instance. After a DB instance is created, you can reset the password. For details, see section Resetting the Administrator Password to Restore root Access.
     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. If the password you provide is regarded as a weak password by the system, you will be prompted to enter a stronger password. 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 to Restore root Access.
     Confirm Password	Must be the same as Administrator Password.
     VPC	The virtual network in which your TaurusDB for PostgreSQL instance is located. A VPC can isolate networks for different workloads. 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, TaurusDB for PostgreSQL allocates a VPC to you by default. To use a shared VPC, select a VPC that another account shares with the current account from the drop-down list. VPC owners can share the subnets in a VPC with one or multiple accounts through Resource Access Manager (RAM). Through VPC sharing, you can easily configure, operate, and manage multiple accounts' resources at low costs. For more information about VPC and subnet sharing, see VPC Sharing. NOTICE: After a TaurusDB for PostgreSQL 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 are only valid within a specific AZ. Dynamic Host Configuration Protocol (DHCP) is enabled by default for subnets where you plan to create DB instances and cannot be disabled. A private IPv4 address is automatically assigned when you create a DB instance. You can also enter an idle private IPv4 address within the subnet CIDR block. After the DB instance is created, you can change the private 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. In addition, a network access control list (ACL) can help control inbound and outbound traffic of subnets in your VPC. A security group enhances security by controlling access to TaurusDB for PostgreSQL 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, TaurusDB for PostgreSQL allocates a security group to you by default.

   • Advanced settings
     Figure 4 Advanced settings
     

     Table 4 Advanced settings

     Parameter	Description
     Enterprise Project	If your account has been associated with an enterprise project, select the target project from the Enterprise Project drop-down list. For more information about enterprise projects, see Enterprise Management User Guide.
     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. You can modify the instance parameters as required after the DB instance is created. 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 Modifying Parameters of a TaurusDB for PostgreSQL Instance.
     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 as needed.
     Babelfish	Provides a SQL Server syntax compatibility layer, enabling Transact-SQL (T-SQL) applications to run seamlessly in a PostgreSQL environment. This option is enabled by default. Currently, it cannot be disabled.
     Babelfish Migration Mode	Babelfish supports Single-DB and Multi-DB migration modes. Single-DB: Only one T-SQL database can be created in Babelfish, and the T-SQL schema is created as a regular PostgreSQL schema in the Babelfish database. Multi-DB: Multiple T-SQL databases can be created in Babelfish (each database has its own schema). The T-SQL schema is created as a PostgreSQL schema (<database_name>_<schema_name>) to avoid name conflicts. CAUTION: After an instance with Babelfish enabled is created, to ensure access to all previously created SQL objects, you are advised not to change the migration mode. If you need to change the migration mode, create a new instance.
     Tag	Tags a DB instance. This parameter is optional. Adding tags helps you better identify and manage your DB instances. Up to 20 tags can be added for each DB instance. If your organization has configured tag policies for TaurusDB for PostgreSQL, add tags to DB instances based on the policies. If a tag does not comply with the policies, DB instance creation may fail. Contact your organization administrator to learn more about tag policies.

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

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

4. To view and manage DB instances, go to the Instances page.
   • When your DB instance is being created, the status is Creating. The status changes to Available after the instance is created.
   • The automated backup policy is enabled by default. You can change it after the DB instance is created. An automated full backup is immediately triggered once your DB instance is created.
   • After a DB instance is created, you can enter a description for it.
   • The default database port is 5432. You can change it after the DB instance is created. For details, see Changing a Database Port.