Help Center/ Relational Database Service/ FAQs/ Network Security/ What Are the Possible Causes for Data Corruption of an RDS Instance?

Updated on 2024-10-08 GMT+08:00

View PDF

What Are the Possible Causes for Data Corruption of an RDS Instance?

Data tampering
Lots of security measures are provided to ensure that only authenticated users have permissions to perform operations on database table records. Database tables can be accessed only through specific database ports.

Verifying package during primary/standby synchronization can prevent data tampering. RDS for MySQL uses the InnoDB storage engine to prevent data from being damaged.
DB instance servers may be powered off suddenly, causing database page corruption and database rebooting failures.
If a primary DB instance becomes faulty, RDS switches to the standby DB instance within 1 to 5 minutes to provide services for you. Databases cannot be accessed during a failover. You must configure automatic reconnection between your applications and RDS to make sure that your applications are available after the failover.

Parent topic: Network Security

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.