proposalbot 228d6e6791 Changes to gaussdb_mysql_umn from docs/doc-exports#545 (gaussdb UMN 20221230 ver
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com>
Co-authored-by: proposalbot <proposalbot@otc-service.com>
Co-committed-by: proposalbot <proposalbot@otc-service.com>
2023-07-19 12:30:39 +00:00

5.7 KiB

original_name

gaussdb_01_0008.html

Constraints

Table 1 <gaussdb_01_0008__en-us_topic_0171122409_table60364850123535> shows the constraints designed to ensure the stability and security of GaussDB(for MySQL).

Table 1 Function constraints
Function Constraints
GaussDB(for MySQL) access
  • If GaussDB(for MySQL) DB instances are not bound with EIPs, the DB instances must be in the same VPC subnet as the ECSs associated with these instances.

  • Security group rules must be added to allow ECSs to access GaussDB(for MySQL) DB instances.

    By default, a GaussDB(for MySQL) DB instance cannot be accessed by an ECS in a different security group. To allow it, you must add an inbound rule to the GaussDB(for MySQL) security group.

  • The default GaussDB(for MySQL) DB instance port is 3306. You can change it if you want to access GaussDB(for MySQL) through another port.

Deployment ECSs in which GaussDB(for MySQL) DB instances are deployed are not visible to users. You can access GaussDB(for MySQL) DB instances only over an IP address and a port.
Administrator root permission Only the root user permissions are available on the instance creation page.
Database parameter modification Most parameters can be modified on the GaussDB(for MySQL) console.
Data migration The mysqldump tool is used to migrate data to GaussDB(for MySQL).
GaussDB(for MySQL) instance reboot GaussDB(for MySQL) instances cannot be rebooted through commands. They must be rebooted on the GaussDB(for MySQL) console.
GaussDB(for MySQL) backup files GaussDB(for MySQL) backup files are stored in OBS buckets and are not visible to users.