Impact of AWS EC2 outage on RDS instance recovery - Need assistance

The recovery process you observed for your Amazon RDS instance on April 15, 2025, could indeed be related to the EC2 outage reported around the same time. When there are infrastructure issues or planned maintenance activities, RDS instances can undergo automatic recovery processes to ensure data integrity and service availability.

In this case, it appears that your RDS instance detected an issue and initiated a recovery process. The recovery started at 14:42 UTC+07:00 and completed by 14:49 UTC+07:00, lasting about 7 minutes. This is within the typical range for RDS failovers, which usually take between 60-120 seconds but can be longer depending on the database activity and recovery process complexity.

The recovery process likely involved the following steps:

1. Detecting the issue (possibly related to the EC2 outage)
2. Initiating the recovery process
3. Restarting the DB instance
4. Completing the recovery

Regarding the EC2 outage's impact on RDS, it's important to note that RDS uses EC2 instances under the hood. If there was a widespread EC2 issue, it could potentially affect RDS instances in the same region or availability zone.

As for the message about RDS Optimized Writes being incompatible with your storage configuration, this is something you should look into, but it's not necessarily an immediate critical issue. RDS Optimized Writes is a feature designed to improve write performance for certain database engines. The incompatibility message suggests that your current storage configuration doesn't support this feature. While addressing this might potentially improve your RDS performance, it's not causing an immediate problem with your database functionality.

To address the RDS Optimized Writes incompatibility:

1. Review your current storage configuration
2. Check the RDS Optimized Writes documentation for MariaDB
3. Consider modifying your instance to use a compatible storage configuration if the performance benefits are significant for your use case

In terms of the recovery process itself, it appears to have completed successfully, and your RDS instance should now be functioning normally. However, it's a good practice to:

1. Monitor your RDS instance closely for any unusual behavior in the coming days
2. Review any application logs for errors or unexpected behavior during the outage period
3. Consider implementing additional high availability measures, such as Multi-AZ deployments, if you haven't already, to minimize the impact of future outages

If you continue to experience issues or have concerns about your RDS instance's performance, it would be advisable to contact AWS Support for a more in-depth investigation of your specific setup and the root cause of the recovery event.

Sources
RDS connections dropping and then self-recover | AWS re:Post
Failing over a Multi-AZ DB instance for Amazon RDS - Amazon Relational Database Service
Related to the RDS - Recovery of the DB Instance has started | AWS re:Post