RDS for MySQL Constraints
The following tables list the constraints designed to ensure the stability and security of RDS for MySQL.
Naming
Item |
Constraints |
---|---|
Instance name |
|
Database name |
|
Account name |
|
Backup name |
|
Parameter template name |
|
Security
Item |
Constraints |
---|---|
root permissions |
Only the administrator account root is provided on the instance creation page. For details about the supported permissions, see root Permissions.
NOTE:
Running revoke, drop user, or rename user on root may cause service interruption. Exercise caution when running any of these statements. |
root password |
|
Database port |
1024 to 65535 (excluding 12017 and 33071, which are occupied by the RDS system) |
Disk encryption |
If you enable disk encryption during instance creation, the disk encryption status and the key cannot be changed later. |
VPC |
The VPC where a DB instance is located cannot be changed after the instance is created. |
Security group |
|
System account |
To provide O&M services, the system automatically creates system accounts when you create RDS for MySQL DB instances. These system accounts are unavailable to you.
|
Instance parameter |
To ensure optimal performance of RDS, you can modify parameters in the parameter template you created as needed. |
Instance Operations
Item |
Constraints |
---|---|
RDS for MySQL storage engine |
Only the InnoDB storage engine is supported. MyISAM, FEDERATED, and MEMORY are not supported. |
Instance deployment |
ECSs where DB instances are deployed are not directly visible to you. You can only access the DB instances through IP addresses and database ports. |
Data migration |
You can migrate data from DDM, GaussDB, GaussDB(for MySQL), self-managed MySQL databases, self-managed Oracle databases, or MySQL databases built on other clouds to RDS for MySQL, or from one RDS for MySQL instance to another RDS for MySQL instance. Data migration tools include Data Replication Service (DRS), mysqldump, and Data Admin Service (DAS). You are advised to use DRS because it is easy to use and can complete a migration task in minutes. DRS facilitates data transfer between databases, helping you reduce DBA labor costs and hardware costs. |
Primary/Standby replication |
RDS for MySQL uses a primary/standby dual-node replication cluster. You do not need to set up replication additionally. The standby DB instance is not visible to you and therefore you cannot access it directly. |
Rebooting a DB instance |
DB instances cannot be rebooted through commands. They must be rebooted through the RDS console. |
Viewing backups |
You can download automated and manual backups for local storage. To download a backup, you can use OBS Browser+, the current browser, or the download URL. |
Log management |
|
Recycle bin |
RDS allows you to move unsubscribed yearly/monthly DB instances and deleted pay-per-use DB instances to the recycle bin. You can rebuild a DB instance that was deleted up to 7 days ago from the recycle bin. |
root Permissions
Permission |
Level |
Description |
Supported |
---|---|---|---|
Select |
Table |
Query permissions |
Yes |
Insert |
Table |
Insert permissions |
|
Update |
Table |
Update permissions |
|
Delete |
Table |
Delete permissions |
|
Create |
Database, table, or index |
Permissions of creating databases, tables, or indexes |
|
Drop |
Database or table |
Permissions of deleting databases or tables |
|
Reload |
Server management |
Permissions of running the following commands: flush-hosts, flush-logs, flush-privileges, flush-status, flush-tables, flush-threads, refresh, and reload |
|
Process |
Server management |
Permissions of viewing processes |
|
Grant |
Database, table, or stored program |
Permissions of granting access control |
|
References |
Database or table |
Foreign key operation permissions |
|
Index |
Table |
Index permissions |
|
Alter |
Table |
Permissions of altering tables, such as adding fields or indexes |
|
Show_db |
Server management |
Permissions of viewing database connections |
|
Create_tmp_table |
Server management |
Permissions of creating temporary tables |
|
Lock_tables |
Server management |
Permissions of locking tables |
|
Execute |
Stored procedure |
Permissions of executing storage procedures |
|
Repl_slave |
Server management |
Replication permissions |
|
Repl_client |
Server management |
Replication permissions |
|
Create_view |
View |
Permissions of creating views |
|
Show_view |
View |
Permissions of viewing views |
|
Create_routine |
Stored procedure |
Permissions of creating storage procedures |
|
Alter_routine |
Stored procedure |
Permissions of altering storage procedures |
|
Create_user |
Server management |
Permissions of creating users |
|
Event |
Database |
Event triggers |
|
Trigger |
Database |
Triggers |
|
Super |
Server management |
Permissions of killing threads |
No |
File |
File on the server |
Permissions of accessing files on database server nodes |
No |
Shutdown |
Server management |
Permissions of shutting down databases |
|
Create_tablespace |
Server management |
Permissions of creating tablespaces |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.