Amazon Neptune
User Guide (API Version 2017-11-29)

High Availability for Neptune

Neptune stores copies of the data in a DB cluster across multiple Availability Zones in a single AWS Region, regardless of whether the instances in the DB cluster span multiple Availability Zones.

When you create Neptune Replicas across Availability Zones, Neptune automatically provisions and maintains them synchronously. The primary DB instance is synchronously replicated across Availability Zones to Neptune Replicas to provide data redundancy, eliminate I/O freezes, and minimize latency spikes during system backups. Running a DB instance with high availability can enhance availability during planned system maintenance, and help protect your databases against failure and Availability Zone disruption.

Using the console, you can create a Multi-AZ deployment by simply specifying Multi-AZ when creating a DB cluster. If a DB cluster is in a single Availability Zone, you can make it a Multi-AZ DB cluster adding a Neptune Replica in a different Availability Zone.

After you create the primary instance for a DB cluster, you can create up to 15 Neptune Replicas in your DB cluster to support read-only queries. We recommend that you distribute the primary instance and Aurora Replicas in your DB cluster over multiple Availability Zones to improve the availability of your DB cluster. Call the create-db-instance AWS CLI command to create a Read Replica in your DB cluster. Include the name of the DB cluster as the --db-cluster-identifier parameter value. You can optionally specify an Availability Zone for the Neptune Replica using the --availability-zone parameter.

For more information about failover to Neptune Replicas, see Amazon Neptune Endpoints. For more information about creating a DB cluster, see Launching a Neptune DB Cluster.