To ensure the stability and security of RDS for MySQL, certain restrictions to database and management properties apply.
The RDS console or API must be used to modify database parameters, however, some parameters cannot be modified. For details, see Setting parameters.
The root or sa permission is not provided.
Restoration and backup
The command line or graphical interface can be used to perform logical backup.
For physical backup, the RDS console or OPEN API must be used.
The command line or graphical interface can be used to perform logical import.
You can use mysql command line tool or DTS (Data Transmission Service) to perform data migration.
RDS for MySQL provides a dual-node cluster of master/slave MySQL replications architecture, so there is no 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.
MySQL storage engine
Currently only InnoDB and TokuDB are supported.
The InnoDB storage engine is recommended for performance and security requirements.
The Memory engine is not supported. Due to the defects inherent to the MyISAM engine, data may be lost. Therefore, any new instances generated with MyISAM engine will be automatically converted to InnoDB table.
Restarting the RDS instance
Instance must be restarted through the RDS console or API.
User, password and database management
By default, RDS for MySQL use the RDS management console to perform user, password and database management such as creating or deleting an instance, modifying privileges and changing password. RDS for MySQL also supports creating a master account for finer-grained management controls.
Does not support custom authorization.
The account management and database management interfaces exist on the RDS console.
The instance with ordinary accounts can create a master account.
MySQL 5.7 instance does not support ordinary account.
Support custom authorization.
The account management and database management interfaces disappear from the RDS console. You need to manage the accounts or databases through SQL statements.
The account cannot be rolled back to the ordinary account.
MySQL 5.7 instance creates master account by default.
If the access mode of MySQL 5.5/5.6 instance is safe connection mode, do not enable net.ipv4.tcp_timestamps in SNAT mode.