Neptune DB clusters should be deployed across multiple Availability Zones
Description
This control checks if an Amazon Neptune DB cluster has read-replica instances in multiple Availability Zones (AZs). The control fails if the cluster is deployed in only one AZ. Read-replicas act as failover targets for the primary instance during AZ unavailability or maintenance. If the primary instance fails, Neptune promotes a read-replica to become the new primary. Without read-replicas, the DB cluster remains unavailable until the primary instance is re-created, which takes significantly longer. To ensure high availability, it's recommended to create one or more read-replica instances with the same DB instance class as the primary, located in different AZs.
Remediation
To remediate Neptune DB clusters not deployed across multiple Availability Zones, you need to create read-replica instances in different AZs.
Steps
- Navigate to the Amazon Neptune console
- Select the DB cluster that needs remediation
- Click on 'Actions' and select 'Create read replica'
- Choose a different Availability Zone for the read replica
- Select the same DB instance class as the primary instance
- Configure any additional settings as needed
- Review the read replica configuration
- Click 'Create read replica' to deploy
- Verify that the read replica is created in a different AZ
- Test failover functionality to ensure high availability