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

rds-incompatible-network-sherin

My RDS instance is in the incompatible-network state. What does this mean, and how can I fix it?

The incompatible-network state indicates one or more of the following is true of the RDS instance:

The incompatible-network state might be displayed on an RDS instance after modifying the instance’s class, modifying the instance to use a Multi-AZ deployment, or after a host replacement due to a maintenance event. The Events pane in the RDS management console should have more details about why your instance is in the incompatible-network state.

The incompatible-network state means the instance might still be accessible at the database level, but you won’t be able to modify or reboot the instance. In order to prevent your RDS instances from moving into the incompatible-network state while performing instance scaling, Multi-AZ conversion, or during a host replacement, before launching a replacement RDS instance or restoring from a snapshot backup, check the following:

  1. Begin by signing in to the RDS console, accessing the DB subnet group pane, and taking note of the RDS instance’s subnet groups, as well as the subnet groups’ associated VPC(s).
    Note: RDS resources, like most AWS resources, are located in a particular AWS region. If you don’t see the subnet groups associated with your RDS instance, check any other AWS regions you might have used.
  2. Open the Details pane for the DB Subnet Group associated with the RDS instance and take note of the subnet ID(s) associated with the subnet group.
  3. Open the VPC console. Select the VPC you noted before, choose Actions, and select DNS Hostnames. If the DNS Hostnames option is disabled, enable it.
  4. In the VPC console, make sure that the subnets you noted before from the RDS DB subnet group exist and have available IP addresses.
  5. Open the EC2 console and check that you have available, free ENIs. Request a service limit increase if needed.
    Note: The default ENI service limit per region is 350.

To fix an instance that's already in the incompatible-network state, if you previously enabled automated backups for your instance, temporarily stop any writes to the database and perform a point-in-time recovery (PITR). If you haven’t previously enabled 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 Amazon Database Migration Service (DMS).


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