How do I resolve issues with an Amazon RDS database that is in an incompatible-network state?
Last updated: 2020-05-13
My Amazon Relational Database Service (Amazon RDS) DB instance is in an incompatible-network state. What does this mean, and how can I fix it?
An incompatible-network state indicates one or more of the following is true of the Amazon RDS DB instance:
- There are no available IP addresses in the subnet that the RDS DB instance was launched into.
- The subnet mentioned in the Amazon RDS DB subnet group no longer exists in the Amazon Virtual Private Cloud (Amazon VPC).
- The RDS DB instance is publicly accessible, but the DNS hostnames and the DNS resolution options are disabled. Both options must be enabled for an RDS DB instance to be publicly accessible.
- You reached your service quota for Elastic Network Interfaces in the AWS Region that you’re using, and need to request a service quota increase.
- The original elastic network interface of the RDS DB instance was deleted while the instance was stopped. When the RDS DB instance was restarted, the elastic network interface wasn't found.
The incompatible-network state of your RDS DB instance could be the result of performing one of the following actions:
- Modifying the RDS DB instance's class.
- Modifying the RDS DB instance to use a Multi-AZ deployment.
- Replacing a host due to a maintenance event.
- Launching a replacement RDS DB instance.
Creating a new RDS DB instance after the quota for the elastic network interfaces has been reached.
- Restoring from a snapshot backup.
- Starting an RDS DB instance that was stopped.
For more details about why your RDS DB instance is in an incompatible-network state, see Viewing Amazon RDS Events.
The incompatible-network state means that the RDS DB instance might still be accessible at the database level, but you can't modify or reboot it. For this reason, it's a best practice to always have a backup (snapshot or logical) to be sure that you can restore the data to another RDS DB instance, in case your RDS DB instance enters an incompatible-network state.
- Open the Amazon RDS console, and then choose Databases from the navigation pane.
- Choose the RDS DB instance that is in an incompatible-network state, and then note the VPC ID and subnet IDs from the Connectivity & Security pane.
- Open the Amazon VPC console, and then choose Your VPCs from the navigation pane.
- Select the VPC that you noted previously, choose Actions, and then choose Edit DNS hostnames. If DNS hostnames is not enabled, check the box for enable.
- From Your VPCs, select the VPC that you noted previously, choose Actions, and then choose Edit DNS resolution. If the DNS resolution is not enabled, check the box for enable.
- Choose Subnets from the navigation pane, and then confirm that all subnets noted previously from the RDS DB instance details section are listed and have available IP addresses.
- Open the Amazon Elastic Compute Cloud (Amazon EC2) console, and then confirm that you haven't reached the quota for elastic network interfaces. Request a service quota increase if needed.
Note: The quota for network interfaces per AWS Region is 350 by default, or the quota is your RDS DB On-Demand Instance quota multiplied by five, whichever is greater. For more information, see Network Interfaces.
To fix an RDS DB instance that is already in an incompatible-network state, and if you previously enabled automated backups for your RDS DB instance, temporarily stop any writes to the database, and then perform a point-in-time recovery (PITR).
If you didn't already enable automated backups, create a new RDS DB instance. Then, migrate the data by using your preferred backup and restore tool (for example, mysqldump, pg_dump, expdp / impdp), or by using AWS Database Migration Service (AWS DMS).
Important: After an instance enters an incompatible-network state, the RDS DB instance might not be accessible at the DB level to perform a logical backup.