Help Center/ TaurusDB_TaurusDB for PostgreSQL/ User Guide/ Security and Encryption/ Database Account Security
Updated on 2025-11-14 GMT+08:00
View PDF
Share

Database Account Security

Password Strength Requirements

  • For information about the database password strength requirements on the Huawei Cloud TaurusDB for PostgreSQL console, see the database configuration table in Buying a TaurusDB for PostgreSQL Instance.
  • Huawei Cloud TaurusDB for PostgreSQL has a password security policy for user-created database accounts. Passwords must:
    • Consist of at least eight characters.
    • Contain letters, digits, and special characters.
    • Not contain the username.

SSL Encryption

SSL is enabled by default for TaurusDB for PostgreSQL instances and cannot be disabled.

Suggestions for Creating Users

When you run CREATE USER or CREATE ROLE, you are advised to specify a password expiration time with the VALID UNTIL 'timestamp' parameter (timestamp indicates the expiration time).

Suggestions for Accessing Databases

When you access a database object, you are advised to specify the schema name of the database object to prevent trojan-horse attacks.

Account Description

To provide O&M services, the system automatically creates system accounts when you create TaurusDB for PostgreSQL instances. These system accounts are unavailable to you.

Attempting to delete, rename, and change passwords or permissions for these accounts will result in an error.

  • rdsAdmin: management account, which has the superuser permissions and is used to query and modify DB instance information, rectify faults, migrate data, and restore data.
  • pg_execute_server_program: account that allows users who run the database to execute programs on the database server to cooperate with COPY and other functions that allow the execution of server programs.
  • pg_read_all_settings: account that reads all configuration variables, even those that are usually visible only to the super user.
  • pg_read_all_stats: account that reads all pg_stat_* views and uses various extension-related statistics, even those that are usually visible only to the super user.
  • pg_stat_scan_tables: account that executes a monitoring function that may obtain an ACCESS SHARE lock on the table (and may hold the lock for a long time).
  • pg_signal_backend: account that sends a signal (for example, a signal for canceling a query operation or an abortion signal) to another backend.
  • pg_read_server_files: account that allows a database user to use the COPY and other file access functions to read files from any accessible directory on a server.
  • pg_write_server_files: account that allows a database user to use the COPY and other file access functions to write files to any accessible directory on a server.
  • pg_monitor: account that reads and executes various monitoring views and functions. It is a member of pg_read_all_settings, pg_read_all_stats, and pg_stat_scan_tables.
  • rdsRepl: replication account, which is used to synchronize data from primary DB instances to standby DB instances.
  • rdsBackup: backup account, which is used for backend backup.
  • rdsMetric: metric monitoring account, which is used by watchdog to collect database status data.
Parent Topic: Security and Encryption