Instance actions

The Connect button allows you to connect your instance to one of the tools; Query, Bloom, or Dashboards, or to the Developer hub. This is possible from both Aura instances as well as self-managed deployments (see Self-managed instances), as long as the instance/deployment is running.

Pausing a Neo4j instance temporarily stops the database, which means:

When you pause an instance, Aura performs a backup operation behind the scenes. It can take a while to pause, depending on your instance size, because Aura is creating the backup.

When you resume an instance, Aura restarts the instance and restores it from the backup. After confirming, the instance begins resuming. Resuming the instance can take a few minutes to a few hours, depending on its size.

Deleting an instance removes all associated snapshots, so they cannot be used to backup and restore data.

You can clear all data in an instance using the Reset to blank action.

Select Reset to blank from the (…​) more menu on the instance card. You need to confirm your intention since this action cannot be undone.

You can reset an instance from the Aura console only.

Return details about a specific Aura instance.

Snapshots are taken at regular intervals and can be used to download or dump your data to a new instance. You can also restore backups of 4GB or less. See Backup, export, restore, and upload for more information

You can clone data from an Aura instance to another existing instance or a new instance.

Note that you have to use the Aura console to clone, it is not supported via Aura API.

The time it takes depends on the amount of data (and factors such as number of indexes and constraints, or the capacity of the destination instance).

You can clone from a Neo4j version 4 instance to an instance running the latest Neo4j version. You cannot clone from latest Neo4j version to Neo4j version 4.

Different tiers serve different operational needs. Should your needs change, you can upgrade. Tiers and prices are described at Neo4j.com/pricing

An upgrade does not change the original instance ID, meaning that your application strings remain valid.

GDS plugin removal: If your AuraDB Professional instance uses the GDS plugin, it is removed during the upgrade. The GDS plugin is not supported in AuraDB Business Critical.

Minimum instance size: If you try to upgrade a 1GB Professional instance, you need to resize it to at least 2GB of storage, because this is the minimum supported size in AuraDB Business Critical.

Admins can mark a database instance as production in AuraDB Virtual Dedicated Cloud and AuraDB Business Critical.

When Neo4j updates Aura Database versions, instances marked as production are last to have the Aura Database version updated. Because updates are applied to these database instances after other database instances receive updates, you can monitor any potential impact on less critical instances first.

After marking the instance as production the label is applied immediately, and all instance actions (such as pause or clone) are temporarily unavailable while the instance is set to production in the Neo4j backend.

Use the more menu (…​) on the instance card to mark it as production.

Secondaries are read-only copies of your database used for scaling. You can edit the number of secondary copies on applicable instances. See Secondaries for more information.

Resizing an instance means adjusting memory, CPU, and storage size. Memory and CPU are configured together, since each instance size pairs a specific amount of memory with a corresponding number of CPUs. A base allocation of storage is also included with each configuration. If you change the memory and CPU, the storage allowance also changes. However, you can also change the storage size independently.

An instance remains available during the resize operation.

Note that this option is not available for Free instances.

You can change the size of an existing instance using the Configure button on the instance you want to resize. From the Configure Instance settings, go to Sizing and then select the preferred sizes from the dropdown.

You select the amount of resources you need when you create your AuraDB instance, but this can be adjusted at any time if your needs change.

To adjust memory and CPU, use the Configure button on the instance card and select a new value. Note that the included storage value changes automatically when you change the memory and CPU value, but this can be adjusted (see below).

You may reduce your memory and CPU, provided that the new value is equal to or greater than your current usage.

Adjust the storage size of your instance at any time. Each AuraDB instance includes a standard storage allocation and configuration; additional storage is chargeable.

To select the storage size during instance creation, select the desired value in the Storage (Adjustable) column.

To adjust an existing instance’s storage, use the Configure button on the instance card and select a new value for the storage size.

You may reduce your storage allocation, provided the new size is equal to or greater than your current usage. For example, if you are using 8GB of data, the minimum selectable option will be 8GB. Selecting a size smaller than your current usage is not permitted. This store size policy also applies to general instance downsizing.

Custom endpoints are used for database management and migration. You set up endpoints in the Project settings. See Custom endpoints for more information.

On the bottom of the instance card you can find a selection of collapsible metrics. Use the View all metrics button to see more. See View metrics for more information.