Instance details

From the instance card, select the more menu (…) then select instance details. Apart from viewing the instance details, you can also rename your instance using the pen icon next to the instance name.

Table 1. Instance details
Detail	Description
Region	Where servers are located
Version	The version of the Aura database
Connection URI	Use this to connect to an instance
Private URI	Applicable if you have a private link set up
ID	Every instance has with an ID which is a unique identifier. It means multiple instances can have the same instance name, because they are distinguishable by their unique ID.
Memory	The capacity of your instance.
CPU	Aura provides database as a service through public cloud providers. It runs on container technology and this allows for the AuraDB Instance to allocate dedicated CPU resources.
Storage	Neo4j Aura automates the backup process (you can also create your own on-demand snapshots), storing your data securely in the cloud. Backups are saved in the storage bucket of the cloud provider in the same region as your Neo4j Aura instance.
Encryption key	Neo4j Managed Key encrypts your data

Snapshots

The data in your instance can be backed up, exported, and restored using snapshots. A snapshot is a copy of the data in an instance at a specific point in time.

Neo4j regularly takes snapshots of your instance, and you can also take a snapshot on demand. These snapshots can be used to restore data to a different Neo4j instance.

Vector optimization

AuraDB Professional AuraDB Business Critical AuraDB Virtual Dedicated Cloud

Vector optimization reserves memory for vector indexes, enhancing performance for vector-based operations. It is available for AuraDB instances with more than 4GB of memory and across all supported cloud providers and regions.

This configuration re-allocates memory from the graph database to the vector index. If this has an impact on your application, consider resizing to a larger Aura instance.

To enable vector optimization during instance creation, select Instance details > Additional settings > Vector-optimized configuration.

To enable vector optimization on existing instances, from the instance card, use Inspect from the more menu (…) to access the instance details. You can view the current vector configuration status from the instance details.

If you lower the instance size below 4GB, vector optimization is disabled automatically.

If you clone your instance to a new instance, the new instance inherits the vector optimization settings of the original instance. But if you clone to an existing instance, its vector optimization setting remains unchanged.

To learn more about how to use vector indexes, see Cypher Manual → Vector indexes.

Instance sizing guide

The vector optimized configuration is intended to allow an Aura instances' available storage to be completely filled and still provide consistent vector search performance. The table below shows the theoretical maximum GiB of vectors for each instance size, and the equivalent number of 768 dimension float-32 vectors.

Aura Instance Size	GiB vectors	Million vectors (768 dimensions)
4GB	2.8	0.9
8GB	5.6	1.8
16GB	11.2	3.6
32GB	22.4	7.3
64GB	44.9	14.6
128GB	89.8	29.2
256GB	179.6	58.4
512GB	359.3	116.9

GiB vectors is limited by available storage. As larger stores become available, we can increase the vector capacity for these instances.