RDS for MySQL Constraints
The following tables list the constraints designed to ensure the stability and security of RDS for MySQL.
Specifications and Performance
Item | Constraints |
---|---|
Storage space |
|
Connections | A maximum of 100,000 |
IOPS |
|
Quotas
Item | Constraints | Description |
---|---|---|
Read replica | A maximum of five read replicas can be created for a DB instance. | For more information, see Introducing Read Replicas. |
Tags | A maximum of 20 tags can be added for a DB instance. | For more information, see RDS for MySQL Tags. |
Free backup space | RDS provides free backup space of the same size as your purchased storage space. | After you pay for the storage space of your DB instance, you will get a backup space of the same size for free. For more information, see How Is RDS Backup Data Billed? |
Retention period of automated backups | The default value is 7 days. The value ranges from 1 to 732 days. | For more information, see Configuring an Intra-Region Backup Policy. |
Log retention period |
| For more information, see Log Management. |
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 |
For more information, see Resetting the Administrator Password. |
Database port | 1024 to 65535 (excluding 12017, 33071, and 33062, which are occupied by the RDS system) For more information, see Changing a Database Port. |
Disk encryption | If you enable disk encryption during instance creation, the disk encryption status and the key cannot be changed later. For more information, see Performing a Server-Side Encryption. |
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. For more information, see Suggestions on RDS for MySQL Parameter Tuning. |
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. |
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. For more information, see Downloading a Backup File. |
Log management |
|
Recycle bin | RDS allows you to move 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 | Permission of running commands such as 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 | Permissions of event scheduler | |
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 |
- Specifications and Performance
- Quotas
- Naming
- Security
- Instance Operations
- root Permissions