To guarantee the stability and security of ApsaraDB for MySQL, certain limits are propose.
|Parameter modification||The RDS console or APIs must be used to modify database parameters. But some parameters cannot be modified. For more information, see Set parameters through RDS console.|
|Root permission||The root or sa permission is not provided.|
|MySQL storage engine||
|Replication||MySQL provides a dual-node cluster based on the master/slave replication architecture, so you manual deployment is not required. The slave instance in the architecture is invisible to you, and your application cannot access to the slave instance directly.|
|Restarting RDS instances||Instances must be restarted through the RDS console or APIs.|
|User, password, and database management||By default, RDS console is used to manage users, passwords, and databases, including operations such as instance creation, instance deletion, permission modification, and password modification. MySQL also allows you to create a master account for finer-grained management.|
|Network settings||If a MySQL 5.5/5.6 instance is in a classic network and its access mode is safe connection mode, do not enable net.ipv4.tcp_timestamps in SNAT mode.|