To guarantee the stability and security of ApsaraDB for MySQL, certain limits to database and management properties apply.
|Parameter modification||The RDS console or API 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 of master/slave MySQL replications architecture, so you do not need to build them manually. The slave instance in the architecture is invisible to you, and your application cannot access to the slave instance directly.|
|Restarting the RDS instance||Instance must be restarted through the RDS console or API.|
|User, password, and database management||By default, you use the RDS console to perform user, password, and database management such as creating or deleting an instance, modifying privileges and changing password. MySQL also allows you to create a master account for finer-grained management controls.|
|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.|