This topic describes the limits of RDS MySQL. To guarantee stability and security, you must understand the limits.
The following table describes the limits of common actions and configurations in RDS MySQL.
|Parameter modification||The RDS console or supported API actions must be used to modify database parameters. But For security parameters, some parameters cannot be modified. For more information, see Set parameters through the RDS console.|
|Database root permission||The root and sa permissions are not provided.|
|MySQL storage engine||Currently only InnoDB is supported.
|Database replication||MySQL provides a dual-node cluster based on the master/slave replication architecture(except for the basic edition). The slave instance in the architecture is invisible to you, and your application cannot access to the slave instance directly.|
|Instance restart||Instances must be restarted through the RDS console or supported API actions.|
|Network settings||If a MySQL 5.5/5.6 instance is in a classic network and the database proxy mode is enabled for it, do not enable net.ipv4.tcp_timestamps in SNAT mode.|
|Storage space||If the storage space usage for an RDS MySQL instance is abnormally high, the system locks the instance to prevent data loss that may occur due to misoperations. You can unlock the instance by upgrading the instance specifications.|
|Monitoring and alerting||The MySQL5.7 High-availability Edition (with standard SSDs) does not support the alerting function.|