Sherin walks you through
resolving incompatible-network errors
with RDS DB instances


My Amazon Relational Database Service (Amazon RDS) 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 instance:

The incompatible-network state of your instance could be caused by one of the following actions: modifying the instance’s class, modifying the instance to use a Multi-AZ deployment, replacing a host due to a maintenance event, performing instance scaling, launching a replacement RDS instance, or restoring from a snapshot backup. For more details about why your instance is in an incompatible-network state, see Viewing Amazon RDS Events.

The incompatible-network state means that the instance might still be accessible at the database level, but you won’t be able to modify or reboot the instance. 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 instance, in case your instance enters an incompatible-network state.

  1. Open the Amazon RDS console, and choose Subnet group from the navigation pane.
  2. Note the RDS DB instance’s subnet groups and any VPCs that are associated with the subnet groups.
    Note: Amazon RDS resources are located in a particular AWS Region. If you don’t see the subnet groups associated with your RDS DB instance, check other AWS Regions that you might have used.
  3. Choose the subnet group name, and note the Subnet ID listed in the Subnets pane.
  4. Open the Amazon VPC console, and choose Subnets from the navigation pane.
  5. Select the VPC you noted previously, choose Actions, and select Edit DNS hostnames. If the DNS hostnames is disabled, enable it.
  6. Select the VPC, choose Actions, and choose Edit DNS resolution. If the DNS resolution is disabled, enable it.
  7. In the Amazon VPC console, be sure that the subnets you noted previously from the Amazon RDS DB subnet group are listed and have available IP addresses.
  8. Open the Amazon EC2 console, and then confirm that you have available, free elastic network interfaces. Request a service limit increase if needed.
    Note: The default network interface service limit per region is 350.

To fix an instance that is already in an incompatible-network state, and if you previously enabled automated backups for your 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 instance and 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 instance might not be accessible at the DB level to perform a logical backup. 

Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2016-11-11

Updated: 2019-01-28