Amazon Neptune now supports custom endpoints to access your workload
You can now create custom endpoints for Amazon Neptune to access your workload. Custom endpoints allow you to distribute your workload across a designated set of instances within a Neptune cluster.
With custom endpoints, you can specify which instances an endpoint refers to within a cluster and you choose what purpose the endpoint serves. For example, you can use a custom endpoint to route workloads that require higher processing power to a dedicated set of high-memory instances. This keeps other instances in the cluster isolated from these workloads.
When you create a custom endpoint, you choose the instances to include in the endpoint. You can also configure whether newly created replicas in the cluster are added to your custom endpoint. You can add or delete instances from the custom endpoint at any time. You can continue to use the reader endpoint to distribute your read workload to all the replicas in the cluster, the cluster endpoint to connect to the writer instance, and instance endpoints to connect to a specific instance in your cluster. You can create up to five custom endpoints per Neptune cluster, and each endpoint must be associated with at least one database instance.
Custom endpoints are available in regions where Neptune is available. To create custom endpoints, visit the AWS Management Console for Neptune or use the latest AWS SDK or CLI. To learn more about custom endpoints for Amazon Neptune, refer to the Amazon Neptune User Guide.