Function Module | Product Function | Function Description |
Billing Mode | Payment by Volume | The billing method is Payment by Volume, which is billed by hour. |
Package Cycle | The billing method is Package Cycle, which is billed by month | |
Deployment Mode | Across Availability Zones | MySQL provides a solution for disaster recovery instances across availability zones (AZ) to further improve data reliability. |
Specifications | Single Instance | It deploys the architecture with a single database node, which is cost-effective. |
Primary/Standby Instance | Use a high availability (HA) architecture with one master node and one standby node, which is highly available in the event of a fault. This allows for automatic master-slave switching after a short period of service interruption. | |
Read-Only Instance | Use a single-node architecture to synchronize the data of the primary instance. | |
Instance Management | Specification Scaling | The backup space can be expanded as required. |
Storage Space Scaling | The storage space can be expanded as required. | |
Automatic Storage Space Scaling | Automatic Storage Space Scaling can be selected during ordering. | |
Automatic Performance Scaling | When the CPU usage of the instance reaches a certain threshold, the background initiates automatic performance scaling during the maintainable time period set by you. | |
Series Upgrade | The product series supports upgrading to one master and one slave for a single server. | |
Parameter Template | The parameters in the parameter template created by the user can be adjusted based on the service requirements. | |
Label Management | You can create labels for instances to facilitate category management. Labels can be edited and modified. | |
Master-Slave Switching | In case of primary instance unavailability, an automatic master-slave switching is triggered. The access address of the instance remains unchanged after the switching. Additionally, manual triggering of the master-slave switching is supported for special service requirements. | |
Modify Data Replication Mode | Support the data replication mode for switching primary/standby instances, thus catering to different service requirements. You can select Asynchronous or Semi-synchronous. By default, the one-master-and-one-slave instance uses the asynchronous replication mode. | |
Restart Instance | Instances can be restarted in the event of a fault. | |
Modify Database Port | RDS for MySQL allows you to modify the database port of the primary instance. For primary/standby instances, modifying the database port of the primary instance will cause the database port of the standby instance to be modified synchronously. | |
Set the Maintainable Time Period | RDS for MySQL supports the setting of the maintainable time period, automatic performance scaling, upgrading minor versions, and other functions. However, these operations may cause service interruption for a short time. Please perform these operations in the maintainable time period set by you. | |
Renew Instance | You can renew instances before expiration. | |
Release Instance | You can release instances when they are no longer required. | |
Modify Instance Name | You can modify the instance names. | |
Enable/Disable Instance Release Protection | You can enable instance release protection to prevent the instance from being unsubscribed due to misoperation; you can disable this feature when you need to unsubscribe the instance. | |
Instance Recycle Bin | Once an RDS for MySQL instance is moved to the recycle bin, you can rebuild, renew, or destroy it in the recycle bin. | |
Instance Version | Upgrade Minor Kernel Version | The system will upgrade your database kernel version to the current latest version within the maintainable time period you set. |
Password Settings | Custom Password Policy | After you enable and set the customize password policy on the Console, the passwords of all new users and the changed passwords must conform to the set password policy. The existing passwords are not affected. |
Change Password | In case of a potential leak of the instance administrator password, you can quickly modify the password on the Console. | |
Account Management | Create Account | Users with other permissions can be created on the console according to service requirements. |
Modify Account Permissions | Modify the database permissions for the created account, including the permissions to change read-only to read/write, read/write to read-only, and recycle the database. | |
Reset High-Permission Account | Reset the permissions for high-permission account | |
Database Management | Create Database | After a MySQL database instance is successfully created, you can create more databases according to service requirements. |
Delete Database | You can delete unused databases as needed. | |
Monitoring Alarms | View Monitoring Indicators | The Console allows you to visually view various monitoring indicators of RDS for MySQL. |
Set the Frequency for Viewing Monitoring Indicators | The frequency can be set to | |
SQL Audit | When the SQL audit function is enabled, the system will record all SQL operations and save them in the audit log file. | |
Intercept SQL | Sensitive SQL statements can be intercepted to prevent database faults caused by high-risk operations. It is recommended that you enable this function and add relevant intercepted SQL statements. | |
SSL Encryption | SSL ensures integrity and privacy through mutual verification, digital signatures, and encryption, respectively, thus building safe communication between the clients and servers. | |
IP Trustlist | Support the adding of the required IP to the IP trustlist. Only the IP in the IP trustlist can access the instance, thereby improving security. | |
Log Records | Slow Log | By viewing and analyzing slow logs, you can find statements with low execution efficiency to facilitate optimization. |
Error Log | The error log function allows you to view the logs at the database level, including errors and warnings generated when the database is running. You can analyze issues in your system through error logs. | |
Historical Event | Historical events record the relevant operation of the instance, allowing for troubleshooting, traceability, and so on. | |
Backup | Automatic Backup | Support automatic backup of instances, which can be retained for three days by default. The retention period can be changed based on the backup policy. |
Manual Backup | Allow you to create manual backups of a running primary instance. You can use these backups to restore data, thus ensuring data reliability. | |
High-Frequency Physical Backup | Support physical backups at a higher frequency for better real-time performance. | |
Restore | Restore to a New Instance | You can use the backup files to a new instance. |
Use a Single Table in a Single Database for Restoration | Support restoring backup files by the database or by table. | |
Access | Elastic IP | RDS for MySQL allows you to bind EIP and access database instances on the public network. After that, you can unbind the instance as needed. |
Overview of Product Features
2024-06-19 02:05:14