Repository: neo4j/docs-aura
Pull request #622: Aura CLI usage guide
Author: login: rsill-neo4j
Created: 2025-03-04T17:08:10Z | Merged: 2025-03-14T15:33:40Z

content from here:
https://github.com/neo4j/aura-cli/blob/main/docs/usageGuide/A%20Guide%20To%20The%20New%20Aura%20CLI.md

converted to asciidoc + split to multiple files


Diff:
diff --git a/modules/ROOT/content-nav.adoc b/modules/ROOT/content-nav.adoc
index 1394cf000..e036efc16 100644
--- a/modules/ROOT/content-nav.adoc
+++ b/modules/ROOT/content-nav.adoc
@@ -75,6 +75,15 @@ Generic Start
 ** xref:query/operations.adoc[Query operations]
 ** xref:query/apoc.adoc[APOC support]
 
+* Aura CLI
+** xref:aura-cli/index.adoc[Introduction]
+** xref:aura-cli/installation.adoc[Installation]
+** xref:aura-cli/initial-configuration.adoc[Initial configuration]
+** xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants]
+** xref:aura-cli/auradb-instances.adoc[Managing AuraDB instances]
+** xref:aura-cli/configuration.adoc[Configuration]
+** xref:aura-cli/migration.adoc[Migration]
+
 * Metrics
 ** xref:metrics/view-metrics.adoc[View metrics]
 
diff --git a/modules/ROOT/images/aura-cli/console-classic-api-keys.png b/modules/ROOT/images/aura-cli/console-classic-api-keys.png
new file mode 100644
index 000000000..e7b7ecffd
Binary files /dev/null and b/modules/ROOT/images/aura-cli/console-classic-api-keys.png differ
diff --git a/modules/ROOT/images/aura-cli/console-classic-home.png b/modules/ROOT/images/aura-cli/console-classic-home.png
new file mode 100644
index 000000000..e43c629ba
Binary files /dev/null and b/modules/ROOT/images/aura-cli/console-classic-home.png differ
diff --git a/modules/ROOT/images/aura-cli/unified-console-account-dropdown.png b/modules/ROOT/images/aura-cli/unified-console-account-dropdown.png
new file mode 100644
index 000000000..1b0b885a2
Binary files /dev/null and b/modules/ROOT/images/aura-cli/unified-console-account-dropdown.png differ
diff --git a/modules/ROOT/images/aura-cli/unified-console-api-keys.png b/modules/ROOT/images/aura-cli/unified-console-api-keys.png
new file mode 100644
index 000000000..78dd64592
Binary files /dev/null and b/modules/ROOT/images/aura-cli/unified-console-api-keys.png differ
diff --git a/modules/ROOT/images/aura-cli/unified-console-create-api-key.png b/modules/ROOT/images/aura-cli/unified-console-create-api-key.png
new file mode 100644
index 000000000..be651accf
Binary files /dev/null and b/modules/ROOT/images/aura-cli/unified-console-create-api-key.png differ
diff --git a/modules/ROOT/pages/aura-cli/auradb-instances.adoc b/modules/ROOT/pages/aura-cli/auradb-instances.adoc
new file mode 100644
index 000000000..dc70f700f
--- /dev/null
+++ b/modules/ROOT/pages/aura-cli/auradb-instances.adoc
@@ -0,0 +1,298 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword `tenant`.
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead, which is the xref:new-console.adoc#_topology[topological evolution] of "tenant".
+====
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a project where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura plans, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response provides the connection details for the request AuraDB and contains authentication details, the username and password.
+Make sure to record these safely and securely as they are only shown once.
+
+
+== List
+
+To see a list of AuraDB instances, use:
+
+[source, shell]
+----
+aura-cli instance list
+----
+
+Use the table format output option to improve readability:
+
+[source, shell]
+----
+aura-cli instance list --output table 
+----
+
+From the list, you can then use the ID for an AuraDB instance to get detailed information about it, including the URL to use for metrics:
+
+[source, shell]
+----
+aura-cli instance get YOUR_INSTANCE_ID
+----
+
+
+== Update
+
+You can change name, memory, or both for a deployed AuraDB instance:
+
+[source, shell]
+----
+aura-cli instance update YOUR_INSTANCE_ID --name NEW_NAME --memory NEW_MEMORY
+----
+
+You may omit `--name` and `--memory` as needed but at least one must be present.
+
+
+== Delete
+
+If you want to delete an instance, keep in mind that the operation starts immediately and without requiring confirmation.
+Therefore, use with caution:
+
+[source, shell]
+----
+aura-cli instance delete YOUR_INSTANCE_ID
+----
+
+
+== Pause and resume
+
+A paused AuraDB instance incurs a lower cost per hour than when it is running.
+Pausing AuraDB instances when they are not in use and resuming them when needed is an effective mechanism for cost control.
+
+
+=== Pause
+
+[source, shell]
+----
+aura-cli instance pause YOUR_INSTANCE_ID
+----
+
+
+=== Resume
+
+[source, shell]
+----
+aura-cli instance resume YOUR_INSTANCE_ID
+----
+
+
+== Snapshots
+
+A snapshot is a copy of an AuraDB instances data at a specific point in time.
+It can then be restored with the `overwrite` command of the Aura CLI.
+
+
+=== Create
+
+An instance must be running for a snapshot to be created:
+
+[source, shell]
+----
+aura-cli instance snapshot create --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== List
+
+All of the snapshots for an AuraDB instance are returned in the response.
+
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== Get
+
+To obtain the details for a single snapshot, use the `get` command:
+
+[source, shell]
+----
+aura-cli instance snapshot SNAPSHOT_ID --instance-id YOUR_INSTANCE_ID
+----
+
+
+## Overwrite
+
+You can overwrite the content of one AuraDB instance with the content of another while leaving the configuration as is.
+This requires that the destination storage is large enough.
+You use a snapshot of the source AuraDB instance for this operation.
+Overwrites can be used for restoration of an AuraDB instance databases, for duplication, moving between regions or any situation where you want to use the content of one AuraDB with another AuraDB.
+Keep in mind that the content of the destination AuraDB is **completely overwritten** and the operation does not require confirmation.
+Therefore, use with caution.
+
+The steps to overwrite an existing AuraDB with the snapshot from another differs for a historical snapshot and the latest snapshot, as described in the following sections.
+
+In both cases, the destination AuraDB instance must be running.
+
+
+=== Steps for a historical snapshot
+
+. Obtain the ID of the AuraDB instance that has the desired snapshot you wish to use, referred to as the "source instance.
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Decide which of its snapshots to use and note the snapshot ID, referred to as source snapshot:
++
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id SOURCE_INSTANCE_ID
+----
++
+. Locate the destination AuraDB instance and obtain its ID, referred to as the destination instance:
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Perform the overwrite:
++
+[source, shell]
+----
+aura-cli instance overwrite DESTINATION_INSTANCE_ID --source-instance-id SOURCE_INSTANCE_ID --source-snapshot-id SOURCE_SNAPSHOT_ID
+----
++
+If you receive a response that looks like the following, select a different snapshot:
++
+[source, shell]
+----
+Error: [Source snapshot SOURCE_SNAPSHOT_ID is not exportable ]
+----
++
+It is not possible at this time for the Aura CLI to indicate which snapshots are exportable.
+See xref:managing-instances/backup-restore-export.adoc#export-create[Export / Create] for more information about exportable snapshots.
++
+. The destination AuraDB instance content will now be overwritten.
+  Depending on the size, this will take several minutes to complete.
+  You can check the status with:
++
+[source, shell]
+----
+aura-cli instance get DESTINATION_INSTANCE_ID 
+----
+
+When the status is "Running" the overwrite is completed.
+
+
+=== Steps for the latest snapshot
+
+. Locate the destination AuraDB instance and obtain its ID, referred to as the destination instance:
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Perform the overwrite:
++
+[source, shell]
+----
+aura-cli instance overwrite DESTINATION_INSTANCE_ID --source-instance-id SOURCE_INSTANCE_ID
+----
++
+. The destination AuraDB instance content will now be overwritten.
+  Depending on the size, this will take several minutes to complete.
+  You can check the status with:
++
+[source, shell]
+----
+aura-cli instance get DESTINATION_INSTANCE_ID 
+----
+
+When the status is "Running" the overwrite is completed.
+
+
+== Customer-managed keys
+
+Encryption of data at REST is a standard feature of AuraDB and uses keys from a supported cloud key management service (KMS).
+AuraDB Virtual Dedicated Cloud customers may wish to use their own encryption keys, a capability that is referred to as Customer-Managed Encryption Keys (CMEK).
+For more information about Customer Managed Keys, see xref:security/encryption.adoc#customer-managed-keys/[Encryption].
+It is recommended to familiarize yourself with this before proceeding.
+The Aura CLI allows management of this feature with these commands:
+
+* `create` - allows Aura to use the key defined in your Cloud Key Management System.
+* `delete` - removes the permission for Aura to use a key. This makes all data encrypted with that key inaccessible.
+* `list` - lists already defined CMEKs.
+* `get` - detailed information about an individual CMEK.
+
+
+=== Create
+
+To use this command, you must have created your custom managed key in your cloud provider's Key Management System (KMS) and configured its permissions correctly.
+For more information, see xref:security/encryption.adoc[Encryption].
+
+[source, shell]
+----
+aura-cli customer-managed-key create --tenant-id YOUR_TENANT_ID --type AURADB_TYPE --region CLOUD_REGION_OF_THE_AURADB_INSTANCE --name YOUR_CUSTOM_KEY_NAME  --key-id YOUR_CUSTOM_KEY_ARN --cloud-provider YOUR_CLOUD_PROVIDE_THAT_HAS_THE_CUSTOM_KEY
+----
+
+
+=== Delete
+
+Keep in mind that this command executes immediately, resulting in a loss of data access by any AuraDB which is using the CMEK.
+Therefore, use with caution:
+
+[source, shell]
+----
+aura-cli customer-managed-key delete YOUR\_AURA\_CMEK\_ID
+----
+
+
+=== List
+
+List all configured CMEKs:
+
+[source, shell]
+----
+aura-cli customer-managed-key list --tenant-id YOUR\_TENANT\_ID --output table
+----
+
+=== Get
+
+Provide detailed information for a particular CMEK:
+
+[source, shell]
+----
+aura-cli customer-managed-key get YOUR\_CMEK\_ID
+----
\ No newline at end of file
diff --git a/modules/ROOT/pages/aura-cli/auradb-tenants.adoc b/modules/ROOT/pages/aura-cli/auradb-tenants.adoc
new file mode 100644
index 000000000..03dc52609
--- /dev/null
+++ b/modules/ROOT/pages/aura-cli/auradb-tenants.adoc
@@ -0,0 +1,33 @@
+= Working with AuraDB tenants
+:description: Work with AuraDB tenants in the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword `tenant`.
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead, which is the xref:new-console.adoc#_topology[topological evolution] of "tenant".
+====
+
+Aura CLI allows you to list the Aura tenants you can access and then obtain the available AuraDB instance for each one.
+To list the tenants:
+
+[source, shell]
+----
+aura-cli tenant list
+----
+
+To get available AuraDB instances for an individual tenant, change `TENANT-ID` to the one you are interested in.
+The output is substantial as all available AuraDB instance configurations are returned.
+Consider filtering the output, for example by using the link:https://jqlang.org/[jq] utility.
+
+[source, shell]
+----
+aura-cli tenant get TENANT-ID 
+----
+
+If you have a single tenant or one that you use most frequently, it is recommended that you set it as the default to avoid repetition with other Aura CLI commands.
+Do this with:
+
+[source, shell]
+----
+aura-cli config set default-tenant TENANT-ID 
+----
\ No newline at end of file
diff --git a/modules/ROOT/pages/aura-cli/configuration.adoc b/modules/ROOT/pages/aura-cli/configuration.adoc
new file mode 100644
index 000000000..6961b383e
--- /dev/null
+++ b/modules/ROOT/pages/aura-cli/configuration.adoc
@@ -0,0 +1,85 @@
+= Configuration of Aura CLI
+:description: Configure the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword `tenant`.
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead, which is the xref:new-console.adoc#_topology[topological evolution] of "tenant".
+====
+
+Aura CLI has two commands for its own configuration:
+
+* `credential` - sets of client IDs and client secrets that are used to authenticate with the Aura API that the Aura CLI uses to perform its own operations.
+* `config` - addtional configuration options for the Aura CLI, such as turning Beta features on or off.
+
+
+== Credential
+
+
+=== Add
+
+Adds a set of credentials, client ID and client secret, that were obtained from the Aura Console:
+
+[source, shell]
+----
+aura-cli credential add --name YOUR_LABEL --client-id YOUR_CLIENT_ID --client-secret YOUR_CLIENT_SECRET
+----
+
+=== List
+
+Show all configured credentials that can be used by the Aura CLI:
+
+[source, shell]
+----
+aura-cli credential list
+----
+
+=== Remove
+
+Remove a set of credentials:
+
+[source, shell]
+----
+aura-cli credential list --name NAME_TO_REMOVE
+----
+
+=== Use
+
+Set the default credentials for the Aura CLI to use:
+
+[source, shell]
+----
+aura-cli credential use --name NAME_TO_USE
+----
+
+== Config
+
+There are various configuration settings that can be controlled by this command, for example, enabling beta features.
+
+
+=== List
+
+Show the current configuration settings:
+
+[source, shell]
+----
+aura-cli config list
+----
+
+=== Get
+
+Show the value of a selected setting:
+
+[source, shell]
+----
+aura-cli config set SETTING\_NAME
+----
+
+=== Set
+
+Set the value for a selected setting:
+
+[source, shell]
+----
+aura-cli config set SETTING_NAME SETTING_VALUE
+----
\ No newline at end of file
diff --git a/modules/ROOT/pages/aura-cli/index.adoc b/modules/ROOT/pages/aura-cli/index.adoc
new file mode 100644
index 000000000..d22a9eacf
--- /dev/null
+++ b/modules/ROOT/pages/aura-cli/index.adoc
@@ -0,0 +1,19 @@
+= Aura CLI
+:description: A guide to the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword `tenant`.
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead, which is the xref:new-console.adoc#_topology[topological evolution] of "tenant".
+====
+
+The Neo4j Aura Command Line Interface (CLI) is a powerful tool designed to simplify and streamline the management of your Neo4j Aura resources from the command line.
+Neo4j Aura CLI can be used to provision new databases as well as scaling existing ones.
+It offers flexibility, speed, and efficiency, and is suitable for both developers and operations teams.
+Built with ease of use in mind, this CLI bridges the gap between automation and hands-on control, enabling you to integrate Neo4j Aura seamlessly into your workflows.
+
+
+== Feedback
+
+Report feedback via link:https://github.com/neo4j/aura-cli/issues[GitHub issues].
+This covers requested enhancements, defects that you may encounter and general feedback.
\ No newline at end of file
diff --git a/modules/ROOT/pages/aura-cli/initial-configuration.adoc b/modules/ROOT/pages/aura-cli/initial-configuration.adoc
new file mode 100644
index 000000000..acbf0680e
--- /dev/null
+++ b/modules/ROOT/pages/aura-cli/initial-configuration.adoc
@@ -0,0 +1,72 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword `tenant`.
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead, which is the xref:new-console.adoc#_topology[topological evolution] of "tenant".
+====
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura Console
+
+. Log in to the link:https://console.neo4j.io/[Neo4j Aura Console].
+  Navigate to the top right where your account name is displayed and use the down arrow to access the account menu.
++
+image::/aura-cli/unified-console-account-dropdown.png[]
++
+. Use **Create** from **API Keys** in the menu to create a new key.
++
+image::/aura-cli/unified-console-api-keys.png[]
++
+. In the pop-up window, enter a name for the client and then **Create**.
++
+image::/aura-cli/unified-console-create-api-key.png[]
++
+. Make sure to securely save the generated client ID and client secret as they are required to use the Aura CLI and they are not shown again.
+
+
+=== Aura Console classic
+
+. Log in to the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and use the down arrow to access the account menu.
++
+image::/aura-cli/console-classic-home.png[]
++
+. Navigate to **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a name for the client and then **Create**.
+. Make sure to securely save the generated client ID and client secret as they are required to use the Aura CLI. 
+
+
+== Configure the Aura CLI with an Aura API key
+
+Configure the Aura CLI with the Aura API client ID and client secret you obtained earlier.
+The Aura CLI refers to these as "credentials".
+You can have several sets of credentials and select which one to use.
+
+. At the command prompt, enter the following, using your own values:
++
+[source, shell]
+----
+aura-cli credential add --name YOUR\_LABEL --client-id YOUR\_CLIENT\_ID --client-secret YOUR\_CLIENT\_SECRET
+----
++
+. To confirm the credentials are working, list your Aura instances:
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
\ No newline at end of file
diff --git a/modules/ROOT/pages/aura-cli/installation.adoc b/modules/ROOT/pages/aura-cli/installation.adoc
new file mode 100644
index 000000000..d23362241
--- /dev/null
+++ b/modules/ROOT/pages/aura-cli/installation.adoc
@@ -0,0 +1,50 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword `tenant`.
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead, which is the xref:new-console.adoc#_topology[topological evolution] of "tenant".
+====
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub] and works with all versions onf the Aura API.
+Select the latest release and download the archive suitable for your platform and architecture of choice.
+The CLI is fully compatible with Mac, Linux and Windows.
+
+. Navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+. Download the compressed file that matches your OS.
+  Make a note of the folder where the file is located.
+. Once the file is downloaded, extract the contents.
+. Open a command prompt and move to the location where you extracted the files.
+. Complete the installation by moving the aura-cli executable file into the file path.
++
+Mac users:
++
+[source, shell]
+----
+sudo mv aura-cli /usr/local/bin
+----
++
+Windows users:
++
+[source, shell]
+----
+move aura-cli c:\windows\system32
+----
+
+Check the installation with:
+
+[source, shell]
+----
+aura-cli -v
+----
+
+You should see the version of the Aura CLI displayed.
+
+[NOTE]
+====
+If you are using a Mac, you may receive a warning from Apple that aura-cli could not be verified.
+If this happens, open **System Settings**, select **Privacy & Security** on the left, and scroll down on the right.
+Select **Open Anyway**.
+This is temporary and will be resolved shortly.
+====
\ No newline at end of file
diff --git a/modules/ROOT/pages/aura-cli/migration.adoc b/modules/ROOT/pages/aura-cli/migration.adoc
new file mode 100644
index 000000000..5510d666d
--- /dev/null
+++ b/modules/ROOT/pages/aura-cli/migration.adoc
@@ -0,0 +1,101 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword `tenant`.
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead, which is the xref:new-console.adoc#_topology[topological evolution] of "tenant".
+====
+
+The Aura CLI has evolved from link:https://neo4j.com/labs/aura-cli/[Neo4j Labs] to a supported Neo4j product.
+The Neo4j Labs Aura CLI continues to be available for installation for the foreseeable future, but without any further development.
+It is recommended that you move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now `aura-cli`.
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer Managed keys
+* Beta of GraphQL Data APIs
+
+
+== Installation
+
+Download the Aura CLI from link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+It is available as a native binary for Windows, Linux and Mac platforms.
+After downloading the relevant file and extracting the executable, the Aura CLI can be run immediately as there are no dependencies.
+
+
+== Commands
+
+[cols="3,^1,3", options="header"]
+|====
+| Labs Aura CLI                      | maps to | Aura CLI
+| config                             | →       | config
+| credentials                        | →       | credential       
+| instances                          | →       | instance         
+| snapshots                          | →       | instance → snapshot               
+| tenants                            | →       | tenant            
+| tenants → get-metrics-integration  | →       | instance get `<InstanceID>` returns the URL for metrics integration
+|                                    |         | **NEW**: customer-managed-key
+|                                    |         | **NEW**: data-api (beta)
+|====
+
+
+== Command and flag changes with Aura CLI
+
+As far as was possible, the Aura CLI commands and their flags are the same as for the Labs based Aura CLI.
+However, there are some changes as outlined in the following sections.
+
+
+== Config
+
+It is not possible to remove a setting and its value although the value itself can be changed.
+If deletion is wanted, then remove it from the JSON configuration file, either `$HOME/Library/Preferences/neo4j/cli/config.json` (MAC) or `%LOCALAPPDATA%\neo4j\cli\config.json` (Windows).
+
+
+== Create a new AuraDB
+
+When creating an Aura instance with the Aura CLI, the memory size is specified with an integer appended with "GB" e.g. "8GB".
+Previously, this was just the integer.
+
+
+== Delete an AuraDB
+
+The Aura CLI does not prompt for confirmation when deleting an AuraDB and starts the operation immediately.
+
+
+== Update an AuraDB
+
+Only the ID can be used to identify the AuraDB to update.
+The same properties can be changed as previously: its name and memory size.
+
+
+== Get AuraDB instance details
+
+This now includes the URL to obtain metrics.
+
+
+== Tenants
+
+This command no longer includes a flag to obtain metric integration information.
+It is also now part of the details returned for an individual AuraDB.
+See Get AuraDB instance details.
+
+
+== Snapshots
+
+Management of snapshots is now a sub-command of instance and allows for their creation, listing and obtaining their details.
+Restoration of a snapshot is performed by using the aura-cli instance overwrite command.
\ No newline at end of file


Reviews:
user: login: LackOfMorals
body: Looks good to me
state: APPROVED
author_association: MEMBER
submitted_at: 2025-03-05T10:15:34Z
user: login: LackOfMorals
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-05T21:39:14Z
user: login: LackOfMorals
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-05T21:41:34Z
user: login: LackOfMorals
body: Re-read and noticed a few items for corrective actions. 
state: CHANGES_REQUESTED
author_association: MEMBER
submitted_at: 2025-03-05T21:42:09Z
user: login: AlexicaWright
body: Loads of comments.. Could also be worth to check that all mentions of Aura CLI follow the same format.
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-06T13:10:25Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-06T14:29:00Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-06T14:31:45Z
user: login: fiquick
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-07T15:00:21Z
user: login: fiquick
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-07T15:00:48Z
user: login: fiquick
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-07T15:02:03Z
user: login: fiquick
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-07T15:04:09Z
user: login: fiquick
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-07T15:04:58Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T17:22:28Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T17:23:44Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T17:24:13Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T17:25:07Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T17:26:23Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T17:26:48Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-12T10:48:14Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-12T10:50:27Z
user: login: rsill-neo4j
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-12T10:50:44Z
user: login: AlexicaWright
body: Just a few more comments.
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-13T15:24:19Z

Review comments:
diff_hunk: @@ -0,0 +1,44 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub].
+Choose the latest release and download the archive suitable for your platform and architecture of choice.
+The CLI is fully compatible with Mac, Linux and Windows.
+
+. Using your browser, navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+. Download the compressed file that matches your computer.
+  Make a note of the folder where the file is located.
+. After the file has been downloaded, extract the contents.
+. Open a command prompt and move to the location where you extracted the files.
+. Complete the installation by moving the aura-cli executable file into the file path.
+  - Mac users:
++
+[source, shell]
+----
+sudo mv aura-cli /usr/local/bin
+----
++
+  - Windows users:
++
+[source, shell]
+----
+move aura-cli c:\windows\system32
+----
+
+Check the installation with:
+
+[source, shell]
+----
+aura-cli -v
+----
+
+You should see `aura version v1.0.0`.
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: LackOfMorals
body: Realised that we would need to update this every time we do a CLI release.   Suggest we change to 

You should see the version of the Aura CLI displayed. 
created_at: 2025-03-05T21:39:14Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,44 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub].
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: LackOfMorals
body: Add information about  Aura so people know what version of Aura the CLi works with.

Suggested to add at the end of the sentence 

_and works with all versions of the Aura API_
created_at: 2025-03-05T21:41:34Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,12 @@
+= Aura CLI
+:description: A guide to the Neo4j Aura command line interface.
+
+The Neo4j Aura CLI is a powerful tool designed to simplify and streamline the management of your Neo4j Aura resources directly from the command line.
+Whether you're provisioning new databases or scaling existing ones, the Neo4j Aura CLI empowers developers and operations teams with greater flexibility, speed, and efficiency.
+Built with ease of use in mind, this CLI bridges the gap between automation and hands-on control, enabling you to integrate Neo4j Aura seamlessly into your workflows.
path: modules/ROOT/pages/aura-cli/index.adoc
user: login: AlexicaWright
body: ```suggestion
The Neo4j Aura Command Line Interface (CLI) is a powerful tool designed to simplify and streamline the management of your Neo4j Aura resources from the command line.
Neo4j Aura CLI can be used to provision new databases as well as scaling existing ones.
It offers flexibility, speed, and efficiency, and is suitable for both developers and operations teams.
Built with ease of use in mind, this CLI bridges the gap between automation and hands-on control, enabling you to integrate Neo4j Aura seamlessly into your workflows.
```
created_at: 2025-03-06T08:37:22Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,12 @@
+= Aura CLI
+:description: A guide to the Neo4j Aura command line interface.
+
+The Neo4j Aura CLI is a powerful tool designed to simplify and streamline the management of your Neo4j Aura resources directly from the command line.
+Whether you're provisioning new databases or scaling existing ones, the Neo4j Aura CLI empowers developers and operations teams with greater flexibility, speed, and efficiency.
+Built with ease of use in mind, this CLI bridges the gap between automation and hands-on control, enabling you to integrate Neo4j Aura seamlessly into your workflows.
+
+
+== Feedback
+
+Report feedback via [GitHub issues](https://github.com/neo4j/aura-cli/issues).
path: modules/ROOT/pages/aura-cli/index.adoc
user: login: AlexicaWright
body: ```suggestion
Report feedback via link:https://github.com/neo4j/aura-cli/issues[GitHub issues].
```
created_at: 2025-03-06T08:39:26Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,44 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub] and works with all versions onf the Aura API.
+Choose the latest release and download the archive suitable for your platform and architecture of choice.
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: AlexicaWright
body: ```suggestion
Select the latest release and download the archive suitable for your platform and architecture of choice.
```
created_at: 2025-03-06T08:40:12Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,44 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub] and works with all versions onf the Aura API.
+Choose the latest release and download the archive suitable for your platform and architecture of choice.
+The CLI is fully compatible with Mac, Linux and Windows.
+
+. Using your browser, navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: AlexicaWright
body: ```suggestion
. In your browser, navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
```
created_at: 2025-03-06T08:43:58Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,44 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub] and works with all versions onf the Aura API.
+Choose the latest release and download the archive suitable for your platform and architecture of choice.
+The CLI is fully compatible with Mac, Linux and Windows.
+
+. Using your browser, navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+. Download the compressed file that matches your computer.
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: AlexicaWright
body: ```suggestion
. Download the compressed file that matches your OS.
```
created_at: 2025-03-06T08:44:26Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,44 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub] and works with all versions onf the Aura API.
+Choose the latest release and download the archive suitable for your platform and architecture of choice.
+The CLI is fully compatible with Mac, Linux and Windows.
+
+. Using your browser, navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+. Download the compressed file that matches your computer.
+  Make a note of the folder where the file is located.
+. After the file has been downloaded, extract the contents.
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: AlexicaWright
body: ```suggestion
. Once the file is downloaded, extract the contents.
```
created_at: 2025-03-06T08:44:57Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,44 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub] and works with all versions onf the Aura API.
+Choose the latest release and download the archive suitable for your platform and architecture of choice.
+The CLI is fully compatible with Mac, Linux and Windows.
+
+. Using your browser, navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+. Download the compressed file that matches your computer.
+  Make a note of the folder where the file is located.
+. After the file has been downloaded, extract the contents.
+. Open a command prompt and move to the location where you extracted the files.
+. Complete the installation by moving the aura-cli executable file into the file path.
+  - Mac users:
++
+[source, shell]
+----
+sudo mv aura-cli /usr/local/bin
+----
++
+  - Windows users:
++
+[source, shell]
+----
+move aura-cli c:\windows\system32
+----
+
+Check the installation with:
+
+[source, shell]
+----
+aura-cli -v
+----
+
+You should see the version of the Aura CLI displayed.
+
+[NOTE]
+====
+If you are using a Mac, you may receive a warning from Apple that aura-cli could not be verified.
+If this happens, open **System Settings**, select **Privacy & Security** on the left, and scroll down on the right.
+Select **Open Anyway**.
+This should not happen again.
+The aura-cli has been through the Apple certification process but it can take time to trickle down through the Apple ecosystem.
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: AlexicaWright
body: ```suggestion
This is temporary and will be resolved shortly.
The Aura CLI has completed the Apple certification process.
```
Please double-check with legal if we are really allowed to say this.
created_at: 2025-03-06T09:03:56Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
You must have payment information in your account to access this functionality.
```
Maybe explain why you need a MOP for Aura Free?
created_at: 2025-03-06T09:04:45Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
. Navigate to the top right where your account name is displayed and use the down arrow to access the account menu.
```
created_at: 2025-03-06T09:07:12Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
. Navigate to **Account Details**.
```
As a rule, we don't tell users how to click buttons. 
created_at: 2025-03-06T09:07:49Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: Should we not put the UPX instructions first?
created_at: 2025-03-06T09:11:36Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
. In the pop-up window, enter a name for the client and then **Create**.
. Make sure to securely save the generated client ID and client secret as they are required to use the Aura CLI. 
```
created_at: 2025-03-06T09:31:15Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
=== New unified Aura Console experience
```
This should be the default experience.
created_at: 2025-03-06T09:32:19Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
. Log in to the link:https://console.neo4j.io/[Neo4j Aura Console].
```
created_at: 2025-03-06T09:32:36Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
. Log in to the link:https://console.neo4j.io/[Neo4j Aura Console].
```
created_at: 2025-03-06T09:32:52Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
 Navigate to the top right where your account name is displayed and use the down arrow to access the account menu.
```
created_at: 2025-03-06T09:35:09Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
++
+image::/aura-cli/unified-console-home.png[]
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: The image is outdated
created_at: 2025-03-06T09:35:20Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
++
+image::/aura-cli/unified-console-home.png[]
++
+. In the menu, click **API Keys**.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
. Use *Create** from **API Keys** in the menu to create a new key.
```
created_at: 2025-03-06T09:36:55Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
++
+image::/aura-cli/unified-console-home.png[]
++
+. In the menu, click **API Keys**.
++
+image::/aura-cli/unified-console-account-dropdown.png[]
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: It is possible to capture the relevant information in both unified-console-home and unified-console-account-dropdown in one updated image.
created_at: 2025-03-06T09:38:37Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
++
+image::/aura-cli/unified-console-home.png[]
++
+. In the menu, click **API Keys**.
++
+image::/aura-cli/unified-console-account-dropdown.png[]
++
+. In the **API Keys** window, click **Create**.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion

```
Provided that you accept the suggestion above. Our users are quite capable and we should treat them as such.
created_at: 2025-03-06T09:40:08Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
++
+image::/aura-cli/unified-console-home.png[]
++
+. In the menu, click **API Keys**.
++
+image::/aura-cli/unified-console-account-dropdown.png[]
++
+. In the **API Keys** window, click **Create**.
++
+image::/aura-cli/unified-console-api-keys.png[]
++
+. In the pop-up window, enter a name for the API key and click **Create**.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
. In the pop-up window, enter a name for the client and then **Create**.
```
created_at: 2025-03-06T09:44:26Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
++
+image::/aura-cli/unified-console-home.png[]
++
+. In the menu, click **API Keys**.
++
+image::/aura-cli/unified-console-account-dropdown.png[]
++
+. In the **API Keys** window, click **Create**.
++
+image::/aura-cli/unified-console-api-keys.png[]
++
+. In the pop-up window, enter a name for the API key and click **Create**.
++
+image::/aura-cli/unified-console-create-api-key.png[]
++
+. You will be shown the client ID and client secret.
+  Make a note as the client secret will not be shown again and you need both.
+  If you download them, keep them safe.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
. Make sure to securely save the generated client ID and client secret as they are required to use the Aura CLI and they are not shown again.
```
created_at: 2025-03-06T09:44:59Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
++
+image::/aura-cli/unified-console-home.png[]
++
+. In the menu, click **API Keys**.
++
+image::/aura-cli/unified-console-account-dropdown.png[]
++
+. In the **API Keys** window, click **Create**.
++
+image::/aura-cli/unified-console-api-keys.png[]
++
+. In the pop-up window, enter a name for the API key and click **Create**.
++
+image::/aura-cli/unified-console-create-api-key.png[]
++
+. You will be shown the client ID and client secret.
+  Make a note as the client secret will not be shown again and you need both.
+  If you download them, keep them safe.
+
+
+== Configure the Aura CLI with an Aura API key
+
+Configure the Aura CLI with the Aura API client ID and client secret you obtained earlier.
+The Aura CLI refers to these as "credentials".
+You can have several sets of credentials and  choose which one to use.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
You can have several sets of credentials and select which one to use.
```
created_at: 2025-03-06T09:45:27Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
++
+image::/aura-cli/unified-console-home.png[]
++
+. In the menu, click **API Keys**.
++
+image::/aura-cli/unified-console-account-dropdown.png[]
++
+. In the **API Keys** window, click **Create**.
++
+image::/aura-cli/unified-console-api-keys.png[]
++
+. In the pop-up window, enter a name for the API key and click **Create**.
++
+image::/aura-cli/unified-console-create-api-key.png[]
++
+. You will be shown the client ID and client secret.
+  Make a note as the client secret will not be shown again and you need both.
+  If you download them, keep them safe.
+
+
+== Configure the Aura CLI with an Aura API key
+
+Configure the Aura CLI with the Aura API client ID and client secret you obtained earlier.
+The Aura CLI refers to these as "credentials".
+You can have several sets of credentials and  choose which one to use.
+
+. At the command prompt, enter the following, using your values for the items in CAPITALS:
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: AlexicaWright
body: ```suggestion
. At the command prompt, enter the following, using your own values:
```
Let's assume that the users can grasp this implicitly.
created_at: 2025-03-06T09:46:51Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+= Working with AuraDB tenants
path: modules/ROOT/pages/aura-cli/auradb-tenants.adoc
user: login: AlexicaWright
body: ```suggestion
= Working with projects and AuraDB instances
```
You can have both AuraDB and AuraDS instances within the same project. I'm only assuming that this is what is meant. Please verify.
Also, the file should be renamed not to include outdated terminology, ie use _projects_ instead of _tenants_.
created_at: 2025-03-06T09:48:34Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+= Working with AuraDB tenants
+:description: Work with AuraDB tenants in the Neo4j Aura command line interface.
path: modules/ROOT/pages/aura-cli/auradb-tenants.adoc
user: login: AlexicaWright
body: ```suggestion
:description: Work with AuraDB instances in projects in the Neo4j Aura command line interface.
```
As above.
created_at: 2025-03-06T09:48:46Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+= Working with AuraDB tenants
+:description: Work with AuraDB tenants in the Neo4j Aura command line interface.
+
+Aura CLI allows you to list the Aura tenants you can access and then obtain the available AuraDB instance for each one.
path: modules/ROOT/pages/aura-cli/auradb-tenants.adoc
user: login: AlexicaWright
body: ```suggestion
Aura CLI allows you to list the Aura projects you can access and then obtain the available AuraDB instance for each one.
```
created_at: 2025-03-06T09:51:54Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+= Working with AuraDB tenants
+:description: Work with AuraDB tenants in the Neo4j Aura command line interface.
+
+Aura CLI allows you to list the Aura tenants you can access and then obtain the available AuraDB instance for each one.
+To list the tenants:
path: modules/ROOT/pages/aura-cli/auradb-tenants.adoc
user: login: AlexicaWright
body: ```suggestion
To list the projects:
```
If the word "tenant" is actually still used in the command, you'd need a disclaimer to explain this. I think we have something like that in the API docs.
created_at: 2025-03-06T09:52:47Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+= Working with AuraDB tenants
+:description: Work with AuraDB tenants in the Neo4j Aura command line interface.
+
+Aura CLI allows you to list the Aura tenants you can access and then obtain the available AuraDB instance for each one.
+To list the tenants:
+
+[source, shell]
+----
+aura-cli tenant list
+----
+
+To get available AuraDB instances for an individual tenant, change `TENANT-ID` to the one you are interested in.
path: modules/ROOT/pages/aura-cli/auradb-tenants.adoc
user: login: AlexicaWright
body: ```suggestion
To get available AuraDB instances for an individual project, change `TENANT-ID` to the one you are interested in.
```
As above.
created_at: 2025-03-06T09:53:05Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+= Working with AuraDB tenants
+:description: Work with AuraDB tenants in the Neo4j Aura command line interface.
+
+Aura CLI allows you to list the Aura tenants you can access and then obtain the available AuraDB instance for each one.
+To list the tenants:
+
+[source, shell]
+----
+aura-cli tenant list
+----
+
+To get available AuraDB instances for an individual tenant, change `TENANT-ID` to the one you are interested in.
+The output is substantial as all available AuraDB instance configurations are returned.
+Consider filtering the output, for example by using the link:https://jqlang.org/[jq] utility.
+
+[source, shell]
+----
+aura-cli tenant get TENANT-ID 
path: modules/ROOT/pages/aura-cli/auradb-tenants.adoc
user: login: AlexicaWright
body: As above
created_at: 2025-03-06T09:53:22Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+= Working with AuraDB tenants
+:description: Work with AuraDB tenants in the Neo4j Aura command line interface.
+
+Aura CLI allows you to list the Aura tenants you can access and then obtain the available AuraDB instance for each one.
+To list the tenants:
+
+[source, shell]
+----
+aura-cli tenant list
+----
+
+To get available AuraDB instances for an individual tenant, change `TENANT-ID` to the one you are interested in.
+The output is substantial as all available AuraDB instance configurations are returned.
+Consider filtering the output, for example by using the link:https://jqlang.org/[jq] utility.
+
+[source, shell]
+----
+aura-cli tenant get TENANT-ID 
+----
+
+If you have a single tenant or one that you use most frequently, it is recommended that you set it as the default to avoid repetition with other Aura CLI commands.
path: modules/ROOT/pages/aura-cli/auradb-tenants.adoc
user: login: AlexicaWright
body: ```suggestion
If you have a single project or one that you use most frequently, it is recommended that you set it as the default to avoid repetition with other Aura CLI commands.
```
created_at: 2025-03-06T09:53:37Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+= Working with AuraDB tenants
+:description: Work with AuraDB tenants in the Neo4j Aura command line interface.
+
+Aura CLI allows you to list the Aura tenants you can access and then obtain the available AuraDB instance for each one.
+To list the tenants:
+
+[source, shell]
+----
+aura-cli tenant list
+----
+
+To get available AuraDB instances for an individual tenant, change `TENANT-ID` to the one you are interested in.
+The output is substantial as all available AuraDB instance configurations are returned.
+Consider filtering the output, for example by using the link:https://jqlang.org/[jq] utility.
+
+[source, shell]
+----
+aura-cli tenant get TENANT-ID 
+----
+
+If you have a single tenant or one that you use most frequently, it is recommended that you set it as the default to avoid repetition with other Aura CLI commands.
+Do this with:
+
+[source, shell]
+----
+aura-cli config set default-tenant TENANT-ID 
path: modules/ROOT/pages/aura-cli/auradb-tenants.adoc
user: login: AlexicaWright
body: As above
created_at: 2025-03-06T09:53:44Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
Before you can create an AuraDB instance, make sure that your desired configuration is available in a project where the AuraDB will reside.
```
created_at: 2025-03-06T09:55:33Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
Get these by using the project command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB projects].
```
As mentioned elsewhere, we need to clarify that tenant=project and if the old terminology is used in the command, this needs to be called out.
created_at: 2025-03-06T09:56:35Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
For other Aura plans, provide the following:
```
created_at: 2025-03-06T12:15:08Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: Again with "tenant".
created_at: 2025-03-06T12:15:41Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: Yep, again.
created_at: 2025-03-06T12:15:53Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
The response provides the connection details for the request AuraDB and contains authentication details, the username and password.
```
created_at: 2025-03-06T12:17:03Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
+They are only shown once.
+Make sure to record these safely and securely.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
Make sure to record these safely and securely as they are only shown once.
```
created_at: 2025-03-06T12:17:32Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
+They are only shown once.
+Make sure to record these safely and securely.
+
+
+== List
+
+Viewing AuraDB instances is achieved by using:
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
To see a list of AuraDB instances, use:
```
created_at: 2025-03-06T12:18:15Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
+They are only shown once.
+Make sure to record these safely and securely.
+
+
+== List
+
+Viewing AuraDB instances is achieved by using:
+
+[source, shell]
+----
+aura-cli instance list
+----
+
+Use the table format output option to improve readability:
+
+[source, shell]
+----
+aura-cli instance list --output table 
+----
+
+From the list, you can then use the ID for an AuraDB instance to get detailed information about it, including the URL to use for metrics:
+
+[source, shell]
+----
+aura-cli instance get YOUR_INSTANCE_ID
+----
+
+
+== Update
+
+A deployed AuraDB instance can have its name, memory or both changed.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
You can change name, memory, or both for a deployed AuraDB instance:
```
created_at: 2025-03-06T12:19:22Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
+They are only shown once.
+Make sure to record these safely and securely.
+
+
+== List
+
+Viewing AuraDB instances is achieved by using:
+
+[source, shell]
+----
+aura-cli instance list
+----
+
+Use the table format output option to improve readability:
+
+[source, shell]
+----
+aura-cli instance list --output table 
+----
+
+From the list, you can then use the ID for an AuraDB instance to get detailed information about it, including the URL to use for metrics:
+
+[source, shell]
+----
+aura-cli instance get YOUR_INSTANCE_ID
+----
+
+
+== Update
+
+A deployed AuraDB instance can have its name, memory or both changed.
+
+[source, shell]
+----
+aura-cli instance update YOUR_INSTANCE_ID --name NEW_NAME --memory NEW_MEMORY
+----
+
+You may omit `--name` and `--memory` as needed but at least one must be present.
+
+
+== Delete
+
+There's no confirmation required when using the aura-cli for deletion and the operation starts immediately.
+Use with caution:
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
If you want to delete an instance, keep in mind that the operation starts immediately and without requiring confirmation.
Therefore, use with caution:
```
created_at: 2025-03-06T12:39:18Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
+They are only shown once.
+Make sure to record these safely and securely.
+
+
+== List
+
+Viewing AuraDB instances is achieved by using:
+
+[source, shell]
+----
+aura-cli instance list
+----
+
+Use the table format output option to improve readability:
+
+[source, shell]
+----
+aura-cli instance list --output table 
+----
+
+From the list, you can then use the ID for an AuraDB instance to get detailed information about it, including the URL to use for metrics:
+
+[source, shell]
+----
+aura-cli instance get YOUR_INSTANCE_ID
+----
+
+
+== Update
+
+A deployed AuraDB instance can have its name, memory or both changed.
+
+[source, shell]
+----
+aura-cli instance update YOUR_INSTANCE_ID --name NEW_NAME --memory NEW_MEMORY
+----
+
+You may omit `--name` and `--memory` as needed but at least one must be present.
+
+
+== Delete
+
+There's no confirmation required when using the aura-cli for deletion and the operation starts immediately.
+Use with caution:
+
+[source, shell]
+----
+aura-cli instance delete YOUR_INSTANCE_ID
+----
+
+
+== Pause and resume
+
+A paused AuraDB instance incurs a lower cost per hour than when it is running.
+Pausing AuraDB instances when they are not in use and resuming them when needed is an effective mechanism for cost control.
+
+
+=== Pause
+
+[source, shell]
+----
+aura-cli instance pause YOUR_INSTANCE_ID
+----
+
+
+=== Resume
+
+[source, shell]
+----
+aura-cli instance resume YOUR_INSTANCE_ID
+----
+
+
+== Snapshots
+
+A snapshot is a copy of an AuraDB instances data at a specific point in time.
+It can then be restored with the `overwrite` command of the Aura CLI.
+
+
+=== Create
+
+An instance must be running for a snapshot to be created:
+
+[source, shell]
+----
+aura-cli instance snapshot create --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== List
+
+All of the snapshots for an AuraDB instance are returned in the response.
+
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== Get
+
+To obtain the details for a single snapshot, use the `get` command:
+
+[source, shell]
+----
+aura-cli instance snapshot SNAPSHOT_ID --instance-id YOUR_INSTANCE_ID
+----
+
+
+## Overwrite
+
+You can overwrite the content of one AuraDB instance with the content of another while leaving the configuration as is.
+However, the destination storage must be large enough.
+Use a snapshot of the source AuraDB instance.
+Overwrites can be used for restoration of an AuraDB instance databases, for duplication, moving between regions or any situation where you want to use the content of one AuraDB with another AuraDB.
+Note that the content of the destination AuraDB instance is completely overwritten.
+
+There is no confirmation for an overwrite.
+Proceed with caution.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
Keep in mind that the content of the destination AuraDB is **completely overwritten** and the operation does not require confirmation.
Therefore, use with caution.
```
created_at: 2025-03-06T12:43:47Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
+They are only shown once.
+Make sure to record these safely and securely.
+
+
+== List
+
+Viewing AuraDB instances is achieved by using:
+
+[source, shell]
+----
+aura-cli instance list
+----
+
+Use the table format output option to improve readability:
+
+[source, shell]
+----
+aura-cli instance list --output table 
+----
+
+From the list, you can then use the ID for an AuraDB instance to get detailed information about it, including the URL to use for metrics:
+
+[source, shell]
+----
+aura-cli instance get YOUR_INSTANCE_ID
+----
+
+
+== Update
+
+A deployed AuraDB instance can have its name, memory or both changed.
+
+[source, shell]
+----
+aura-cli instance update YOUR_INSTANCE_ID --name NEW_NAME --memory NEW_MEMORY
+----
+
+You may omit `--name` and `--memory` as needed but at least one must be present.
+
+
+== Delete
+
+There's no confirmation required when using the aura-cli for deletion and the operation starts immediately.
+Use with caution:
+
+[source, shell]
+----
+aura-cli instance delete YOUR_INSTANCE_ID
+----
+
+
+== Pause and resume
+
+A paused AuraDB instance incurs a lower cost per hour than when it is running.
+Pausing AuraDB instances when they are not in use and resuming them when needed is an effective mechanism for cost control.
+
+
+=== Pause
+
+[source, shell]
+----
+aura-cli instance pause YOUR_INSTANCE_ID
+----
+
+
+=== Resume
+
+[source, shell]
+----
+aura-cli instance resume YOUR_INSTANCE_ID
+----
+
+
+== Snapshots
+
+A snapshot is a copy of an AuraDB instances data at a specific point in time.
+It can then be restored with the `overwrite` command of the Aura CLI.
+
+
+=== Create
+
+An instance must be running for a snapshot to be created:
+
+[source, shell]
+----
+aura-cli instance snapshot create --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== List
+
+All of the snapshots for an AuraDB instance are returned in the response.
+
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== Get
+
+To obtain the details for a single snapshot, use the `get` command:
+
+[source, shell]
+----
+aura-cli instance snapshot SNAPSHOT_ID --instance-id YOUR_INSTANCE_ID
+----
+
+
+## Overwrite
+
+You can overwrite the content of one AuraDB instance with the content of another while leaving the configuration as is.
+However, the destination storage must be large enough.
+Use a snapshot of the source AuraDB instance.
+Overwrites can be used for restoration of an AuraDB instance databases, for duplication, moving between regions or any situation where you want to use the content of one AuraDB with another AuraDB.
+Note that the content of the destination AuraDB instance is completely overwritten.
+
+There is no confirmation for an overwrite.
+Proceed with caution.
+
+The steps to overwrite an existing AuraDB with the snapshot from another differs for a historical snapshot and the latest snapshot.
+See the following sections.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
The steps to overwrite an existing AuraDB with the snapshot from another differs for a historical snapshot and the latest snapshot, as described in the following sections.
```
created_at: 2025-03-06T12:44:48Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
+They are only shown once.
+Make sure to record these safely and securely.
+
+
+== List
+
+Viewing AuraDB instances is achieved by using:
+
+[source, shell]
+----
+aura-cli instance list
+----
+
+Use the table format output option to improve readability:
+
+[source, shell]
+----
+aura-cli instance list --output table 
+----
+
+From the list, you can then use the ID for an AuraDB instance to get detailed information about it, including the URL to use for metrics:
+
+[source, shell]
+----
+aura-cli instance get YOUR_INSTANCE_ID
+----
+
+
+== Update
+
+A deployed AuraDB instance can have its name, memory or both changed.
+
+[source, shell]
+----
+aura-cli instance update YOUR_INSTANCE_ID --name NEW_NAME --memory NEW_MEMORY
+----
+
+You may omit `--name` and `--memory` as needed but at least one must be present.
+
+
+== Delete
+
+There's no confirmation required when using the aura-cli for deletion and the operation starts immediately.
+Use with caution:
+
+[source, shell]
+----
+aura-cli instance delete YOUR_INSTANCE_ID
+----
+
+
+== Pause and resume
+
+A paused AuraDB instance incurs a lower cost per hour than when it is running.
+Pausing AuraDB instances when they are not in use and resuming them when needed is an effective mechanism for cost control.
+
+
+=== Pause
+
+[source, shell]
+----
+aura-cli instance pause YOUR_INSTANCE_ID
+----
+
+
+=== Resume
+
+[source, shell]
+----
+aura-cli instance resume YOUR_INSTANCE_ID
+----
+
+
+== Snapshots
+
+A snapshot is a copy of an AuraDB instances data at a specific point in time.
+It can then be restored with the `overwrite` command of the Aura CLI.
+
+
+=== Create
+
+An instance must be running for a snapshot to be created:
+
+[source, shell]
+----
+aura-cli instance snapshot create --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== List
+
+All of the snapshots for an AuraDB instance are returned in the response.
+
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== Get
+
+To obtain the details for a single snapshot, use the `get` command:
+
+[source, shell]
+----
+aura-cli instance snapshot SNAPSHOT_ID --instance-id YOUR_INSTANCE_ID
+----
+
+
+## Overwrite
+
+You can overwrite the content of one AuraDB instance with the content of another while leaving the configuration as is.
+However, the destination storage must be large enough.
+Use a snapshot of the source AuraDB instance.
+Overwrites can be used for restoration of an AuraDB instance databases, for duplication, moving between regions or any situation where you want to use the content of one AuraDB with another AuraDB.
+Note that the content of the destination AuraDB instance is completely overwritten.
+
+There is no confirmation for an overwrite.
+Proceed with caution.
+
+The steps to overwrite an existing AuraDB with the snapshot from another differs for a historical snapshot and the latest snapshot.
+See the following sections.
+
+In both cases, the destination AuraDB instance must be running.
+
+
+=== Steps for a historical snapshot
+
+. Obtain the ID of the AuraDB instance that has the desired snapshot you wish to use, referred to as the "source instance.
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Decide which of its snapshots to use and note the snapshot ID, referred to as source snapshot:
++
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id SOURCE_INSTANCE_ID
+----
++
+. Locate the destination AuraDB instance and obtain its ID, referred to as the destination instance:
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Perform the overwrite:
++
+[source, shell]
+----
+aura-cli instance overwrite DESTINATION_INSTANCE_ID --source-instance-id SOURCE_INSTANCE_ID --source-snapshot-id SOURCE_SNAPSHOT_ID
+----
++
+If you receive a response that looks like the following, select a different snapshot:
++
+[source, shell]
+----
+Error: [Source snapshot SOURCE_SNAPSHOT_ID is not exportable ]
+----
++
+It is not possible at this time for the Aura CLI to indicate which snapshots are exportable.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
It is not possible at this time for the Aura CLI to indicate which snapshots are exportable.
See xref:managing-instances/backup-restore-export.adoc#export-create[Export / Create] for more information about exportable snapshots.
```
created_at: 2025-03-06T12:51:43Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
+They are only shown once.
+Make sure to record these safely and securely.
+
+
+== List
+
+Viewing AuraDB instances is achieved by using:
+
+[source, shell]
+----
+aura-cli instance list
+----
+
+Use the table format output option to improve readability:
+
+[source, shell]
+----
+aura-cli instance list --output table 
+----
+
+From the list, you can then use the ID for an AuraDB instance to get detailed information about it, including the URL to use for metrics:
+
+[source, shell]
+----
+aura-cli instance get YOUR_INSTANCE_ID
+----
+
+
+== Update
+
+A deployed AuraDB instance can have its name, memory or both changed.
+
+[source, shell]
+----
+aura-cli instance update YOUR_INSTANCE_ID --name NEW_NAME --memory NEW_MEMORY
+----
+
+You may omit `--name` and `--memory` as needed but at least one must be present.
+
+
+== Delete
+
+There's no confirmation required when using the aura-cli for deletion and the operation starts immediately.
+Use with caution:
+
+[source, shell]
+----
+aura-cli instance delete YOUR_INSTANCE_ID
+----
+
+
+== Pause and resume
+
+A paused AuraDB instance incurs a lower cost per hour than when it is running.
+Pausing AuraDB instances when they are not in use and resuming them when needed is an effective mechanism for cost control.
+
+
+=== Pause
+
+[source, shell]
+----
+aura-cli instance pause YOUR_INSTANCE_ID
+----
+
+
+=== Resume
+
+[source, shell]
+----
+aura-cli instance resume YOUR_INSTANCE_ID
+----
+
+
+== Snapshots
+
+A snapshot is a copy of an AuraDB instances data at a specific point in time.
+It can then be restored with the `overwrite` command of the Aura CLI.
+
+
+=== Create
+
+An instance must be running for a snapshot to be created:
+
+[source, shell]
+----
+aura-cli instance snapshot create --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== List
+
+All of the snapshots for an AuraDB instance are returned in the response.
+
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== Get
+
+To obtain the details for a single snapshot, use the `get` command:
+
+[source, shell]
+----
+aura-cli instance snapshot SNAPSHOT_ID --instance-id YOUR_INSTANCE_ID
+----
+
+
+## Overwrite
+
+You can overwrite the content of one AuraDB instance with the content of another while leaving the configuration as is.
+However, the destination storage must be large enough.
+Use a snapshot of the source AuraDB instance.
+Overwrites can be used for restoration of an AuraDB instance databases, for duplication, moving between regions or any situation where you want to use the content of one AuraDB with another AuraDB.
+Note that the content of the destination AuraDB instance is completely overwritten.
+
+There is no confirmation for an overwrite.
+Proceed with caution.
+
+The steps to overwrite an existing AuraDB with the snapshot from another differs for a historical snapshot and the latest snapshot.
+See the following sections.
+
+In both cases, the destination AuraDB instance must be running.
+
+
+=== Steps for a historical snapshot
+
+. Obtain the ID of the AuraDB instance that has the desired snapshot you wish to use, referred to as the "source instance.
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Decide which of its snapshots to use and note the snapshot ID, referred to as source snapshot:
++
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id SOURCE_INSTANCE_ID
+----
++
+. Locate the destination AuraDB instance and obtain its ID, referred to as the destination instance:
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Perform the overwrite:
++
+[source, shell]
+----
+aura-cli instance overwrite DESTINATION_INSTANCE_ID --source-instance-id SOURCE_INSTANCE_ID --source-snapshot-id SOURCE_SNAPSHOT_ID
+----
++
+If you receive a response that looks like the following, select a different snapshot:
++
+[source, shell]
+----
+Error: [Source snapshot SOURCE_SNAPSHOT_ID is not exportable ]
+----
++
+It is not possible at this time for the Aura CLI to indicate which snapshots are exportable.
++
+. The destination AuraDB instance content will now be overwritten.
+  Depending on the size, this will take several minutes to complete.
+  You can check the status with:
++
+[source, shell]
+----
+aura-cli instance get DESTINATION_INSTANCE_ID 
+----
+
+When the status is "Running" the overwrite is completed.
+
+
+=== Steps for the latest snapshot
+
+. Locate the destination AuraDB instance and obtain its ID, referred to as the destination instance:
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Perform the overwrite:
++
+[source, shell]
+----
+aura-cli instance overwrite DESTINATION_INSTANCE_ID --source-instance-id SOURCE_INSTANCE_ID
+----
++
+. The destination AuraDB instance content will now be overwritten.
+  Depending on the size, this will take several minutes to complete.
+  You can check the status with:
++
+[source, shell]
+----
+aura-cli instance get DESTINATION_INSTANCE_ID 
+----
+
+When the status is "Running" the overwrite is completed.
+
+
+== Customer-managed keys
+
+Encryption of data at REST is a standard feature of AuraDB and uses keys from a supported cloud key management service (KMS).
+AuraDB Virtual Dedicated Cloud customers may wish to use their own encryption keys, a capability that is referred to as Customer-Managed Encryption Keys (CMEK).
+More information is available in the Aura documentation for link:https://neo4j.com/docs/aura/classic/platform/security/encryption/[Encryption].
+We advise you to read this before continuing.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
For more information about Customer Managed Keys, see xref:security/encryption.adoc#customer-managed-keys/[Encryption].
It is recommended to familiarize yourself with this before proceeding.
```
created_at: 2025-03-06T12:57:57Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
+They are only shown once.
+Make sure to record these safely and securely.
+
+
+== List
+
+Viewing AuraDB instances is achieved by using:
+
+[source, shell]
+----
+aura-cli instance list
+----
+
+Use the table format output option to improve readability:
+
+[source, shell]
+----
+aura-cli instance list --output table 
+----
+
+From the list, you can then use the ID for an AuraDB instance to get detailed information about it, including the URL to use for metrics:
+
+[source, shell]
+----
+aura-cli instance get YOUR_INSTANCE_ID
+----
+
+
+== Update
+
+A deployed AuraDB instance can have its name, memory or both changed.
+
+[source, shell]
+----
+aura-cli instance update YOUR_INSTANCE_ID --name NEW_NAME --memory NEW_MEMORY
+----
+
+You may omit `--name` and `--memory` as needed but at least one must be present.
+
+
+== Delete
+
+There's no confirmation required when using the aura-cli for deletion and the operation starts immediately.
+Use with caution:
+
+[source, shell]
+----
+aura-cli instance delete YOUR_INSTANCE_ID
+----
+
+
+== Pause and resume
+
+A paused AuraDB instance incurs a lower cost per hour than when it is running.
+Pausing AuraDB instances when they are not in use and resuming them when needed is an effective mechanism for cost control.
+
+
+=== Pause
+
+[source, shell]
+----
+aura-cli instance pause YOUR_INSTANCE_ID
+----
+
+
+=== Resume
+
+[source, shell]
+----
+aura-cli instance resume YOUR_INSTANCE_ID
+----
+
+
+== Snapshots
+
+A snapshot is a copy of an AuraDB instances data at a specific point in time.
+It can then be restored with the `overwrite` command of the Aura CLI.
+
+
+=== Create
+
+An instance must be running for a snapshot to be created:
+
+[source, shell]
+----
+aura-cli instance snapshot create --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== List
+
+All of the snapshots for an AuraDB instance are returned in the response.
+
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== Get
+
+To obtain the details for a single snapshot, use the `get` command:
+
+[source, shell]
+----
+aura-cli instance snapshot SNAPSHOT_ID --instance-id YOUR_INSTANCE_ID
+----
+
+
+## Overwrite
+
+You can overwrite the content of one AuraDB instance with the content of another while leaving the configuration as is.
+However, the destination storage must be large enough.
+Use a snapshot of the source AuraDB instance.
+Overwrites can be used for restoration of an AuraDB instance databases, for duplication, moving between regions or any situation where you want to use the content of one AuraDB with another AuraDB.
+Note that the content of the destination AuraDB instance is completely overwritten.
+
+There is no confirmation for an overwrite.
+Proceed with caution.
+
+The steps to overwrite an existing AuraDB with the snapshot from another differs for a historical snapshot and the latest snapshot.
+See the following sections.
+
+In both cases, the destination AuraDB instance must be running.
+
+
+=== Steps for a historical snapshot
+
+. Obtain the ID of the AuraDB instance that has the desired snapshot you wish to use, referred to as the "source instance.
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Decide which of its snapshots to use and note the snapshot ID, referred to as source snapshot:
++
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id SOURCE_INSTANCE_ID
+----
++
+. Locate the destination AuraDB instance and obtain its ID, referred to as the destination instance:
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Perform the overwrite:
++
+[source, shell]
+----
+aura-cli instance overwrite DESTINATION_INSTANCE_ID --source-instance-id SOURCE_INSTANCE_ID --source-snapshot-id SOURCE_SNAPSHOT_ID
+----
++
+If you receive a response that looks like the following, select a different snapshot:
++
+[source, shell]
+----
+Error: [Source snapshot SOURCE_SNAPSHOT_ID is not exportable ]
+----
++
+It is not possible at this time for the Aura CLI to indicate which snapshots are exportable.
++
+. The destination AuraDB instance content will now be overwritten.
+  Depending on the size, this will take several minutes to complete.
+  You can check the status with:
++
+[source, shell]
+----
+aura-cli instance get DESTINATION_INSTANCE_ID 
+----
+
+When the status is "Running" the overwrite is completed.
+
+
+=== Steps for the latest snapshot
+
+. Locate the destination AuraDB instance and obtain its ID, referred to as the destination instance:
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Perform the overwrite:
++
+[source, shell]
+----
+aura-cli instance overwrite DESTINATION_INSTANCE_ID --source-instance-id SOURCE_INSTANCE_ID
+----
++
+. The destination AuraDB instance content will now be overwritten.
+  Depending on the size, this will take several minutes to complete.
+  You can check the status with:
++
+[source, shell]
+----
+aura-cli instance get DESTINATION_INSTANCE_ID 
+----
+
+When the status is "Running" the overwrite is completed.
+
+
+== Customer-managed keys
+
+Encryption of data at REST is a standard feature of AuraDB and uses keys from a supported cloud key management service (KMS).
+AuraDB Virtual Dedicated Cloud customers may wish to use their own encryption keys, a capability that is referred to as Customer-Managed Encryption Keys (CMEK).
+More information is available in the Aura documentation for link:https://neo4j.com/docs/aura/classic/platform/security/encryption/[Encryption].
+We advise you to read this before continuing.
+The Aura CLI allows management of this feature with these commands:
+
+* `create` - allows Aura to use the key defined in your Cloud Key Management System.
+* `delete` - removes the permission for Aura to use a key. This makes all data encrypted with that key inaccessible.
+* `list` - lists already defined CMEKs.
+* `get` - detailed information about an individual CMEK.
+
+
+=== Create
+
+To use this command, you must have created your custom managed key in your cloud provider's Key Management System (KMS) and configured its permissions correctly.
+This is explained in the Neo4j AuraDB documentation under link:https://neo4j.com/docs/aura/classic/platform/security/encryption/[Encryption].
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
For more information, see xref:security/encryption.adoc[Encryption].
```
created_at: 2025-03-06T12:59:25Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,295 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a tenant where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura tiers, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response will provide the connection details for the request AuraDB which will contain authentication details, the username and password.
+They are only shown once.
+Make sure to record these safely and securely.
+
+
+== List
+
+Viewing AuraDB instances is achieved by using:
+
+[source, shell]
+----
+aura-cli instance list
+----
+
+Use the table format output option to improve readability:
+
+[source, shell]
+----
+aura-cli instance list --output table 
+----
+
+From the list, you can then use the ID for an AuraDB instance to get detailed information about it, including the URL to use for metrics:
+
+[source, shell]
+----
+aura-cli instance get YOUR_INSTANCE_ID
+----
+
+
+== Update
+
+A deployed AuraDB instance can have its name, memory or both changed.
+
+[source, shell]
+----
+aura-cli instance update YOUR_INSTANCE_ID --name NEW_NAME --memory NEW_MEMORY
+----
+
+You may omit `--name` and `--memory` as needed but at least one must be present.
+
+
+== Delete
+
+There's no confirmation required when using the aura-cli for deletion and the operation starts immediately.
+Use with caution:
+
+[source, shell]
+----
+aura-cli instance delete YOUR_INSTANCE_ID
+----
+
+
+== Pause and resume
+
+A paused AuraDB instance incurs a lower cost per hour than when it is running.
+Pausing AuraDB instances when they are not in use and resuming them when needed is an effective mechanism for cost control.
+
+
+=== Pause
+
+[source, shell]
+----
+aura-cli instance pause YOUR_INSTANCE_ID
+----
+
+
+=== Resume
+
+[source, shell]
+----
+aura-cli instance resume YOUR_INSTANCE_ID
+----
+
+
+== Snapshots
+
+A snapshot is a copy of an AuraDB instances data at a specific point in time.
+It can then be restored with the `overwrite` command of the Aura CLI.
+
+
+=== Create
+
+An instance must be running for a snapshot to be created:
+
+[source, shell]
+----
+aura-cli instance snapshot create --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== List
+
+All of the snapshots for an AuraDB instance are returned in the response.
+
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== Get
+
+To obtain the details for a single snapshot, use the `get` command:
+
+[source, shell]
+----
+aura-cli instance snapshot SNAPSHOT_ID --instance-id YOUR_INSTANCE_ID
+----
+
+
+## Overwrite
+
+You can overwrite the content of one AuraDB instance with the content of another while leaving the configuration as is.
+However, the destination storage must be large enough.
+Use a snapshot of the source AuraDB instance.
+Overwrites can be used for restoration of an AuraDB instance databases, for duplication, moving between regions or any situation where you want to use the content of one AuraDB with another AuraDB.
+Note that the content of the destination AuraDB instance is completely overwritten.
+
+There is no confirmation for an overwrite.
+Proceed with caution.
+
+The steps to overwrite an existing AuraDB with the snapshot from another differs for a historical snapshot and the latest snapshot.
+See the following sections.
+
+In both cases, the destination AuraDB instance must be running.
+
+
+=== Steps for a historical snapshot
+
+. Obtain the ID of the AuraDB instance that has the desired snapshot you wish to use, referred to as the "source instance.
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Decide which of its snapshots to use and note the snapshot ID, referred to as source snapshot:
++
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id SOURCE_INSTANCE_ID
+----
++
+. Locate the destination AuraDB instance and obtain its ID, referred to as the destination instance:
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Perform the overwrite:
++
+[source, shell]
+----
+aura-cli instance overwrite DESTINATION_INSTANCE_ID --source-instance-id SOURCE_INSTANCE_ID --source-snapshot-id SOURCE_SNAPSHOT_ID
+----
++
+If you receive a response that looks like the following, select a different snapshot:
++
+[source, shell]
+----
+Error: [Source snapshot SOURCE_SNAPSHOT_ID is not exportable ]
+----
++
+It is not possible at this time for the Aura CLI to indicate which snapshots are exportable.
++
+. The destination AuraDB instance content will now be overwritten.
+  Depending on the size, this will take several minutes to complete.
+  You can check the status with:
++
+[source, shell]
+----
+aura-cli instance get DESTINATION_INSTANCE_ID 
+----
+
+When the status is "Running" the overwrite is completed.
+
+
+=== Steps for the latest snapshot
+
+. Locate the destination AuraDB instance and obtain its ID, referred to as the destination instance:
++
+[source, shell]
+----
+aura-cli instance list --output table
+----
++
+. Perform the overwrite:
++
+[source, shell]
+----
+aura-cli instance overwrite DESTINATION_INSTANCE_ID --source-instance-id SOURCE_INSTANCE_ID
+----
++
+. The destination AuraDB instance content will now be overwritten.
+  Depending on the size, this will take several minutes to complete.
+  You can check the status with:
++
+[source, shell]
+----
+aura-cli instance get DESTINATION_INSTANCE_ID 
+----
+
+When the status is "Running" the overwrite is completed.
+
+
+== Customer-managed keys
+
+Encryption of data at REST is a standard feature of AuraDB and uses keys from a supported cloud key management service (KMS).
+AuraDB Virtual Dedicated Cloud customers may wish to use their own encryption keys, a capability that is referred to as Customer-Managed Encryption Keys (CMEK).
+More information is available in the Aura documentation for link:https://neo4j.com/docs/aura/classic/platform/security/encryption/[Encryption].
+We advise you to read this before continuing.
+The Aura CLI allows management of this feature with these commands:
+
+* `create` - allows Aura to use the key defined in your Cloud Key Management System.
+* `delete` - removes the permission for Aura to use a key. This makes all data encrypted with that key inaccessible.
+* `list` - lists already defined CMEKs.
+* `get` - detailed information about an individual CMEK.
+
+
+=== Create
+
+To use this command, you must have created your custom managed key in your cloud provider's Key Management System (KMS) and configured its permissions correctly.
+This is explained in the Neo4j AuraDB documentation under link:https://neo4j.com/docs/aura/classic/platform/security/encryption/[Encryption].
+
+[source, shell]
+----
+aura-cli customer-managed-key create --tenant-id YOUR_TENANT_ID --type AURADB_TYPE --region CLOUD_REGION_OF_THE_AURADB_INSTANCE --name YOUR_CUSTOM_KEY_NAME  --key-id YOUR_CUSTOM_KEY_ARN --cloud-provider YOUR_CLOUD_PROVIDE_THAT_HAS_THE_CUSTOM_KEY
+----
+
+
+=== Delete
+
+This command executes immediately, resulting in a loss of data access by any AuraDB which is using the CMEK.
+Use with caution:
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
Keep in mind that this command executes immediately, resulting in a loss of data access by any AuraDB which is using the CMEK.
Therefore, use with caution:
```
edit by rsill: changed suggestion - "his" -> "this"
created_at: 2025-03-06T13:01:21Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,79 @@
+= Configuration of Aura CLI
+:description: Configure the Neo4j Aura command line interface.
+
+Aura CLI has two commands for its own configuration:
+
+* `credential` - sets of client IDs and client secrets that are used to authenticate with the Aura API that the Aura CLI uses to perform its own operations.
+* `config` - addtional configuration options for the Aura CLI, such as turning Beta features on or off.
+
+
+== Credential
+
+
+=== Add
+
+Adds a set of credentials, client ID and client secret, that were obtained from the Aura Console:
+
+[source, shell]
+----
+aura-cli credential add --name YOUR_LABEL --client-id YOUR_CLIENT_ID --client-secret YOUR_CLIENT_SECRET
+----
+
+=== List
+
+Show all configured credentials that can be used by the Aura CLI:
+
+[source, shell]
+----
+aura-cli credential list
+----
+
+=== Remove
+
+Remove a set of credentials:
+
+[source, shell]
+----
+aura-cli credential list --name NAME_TO_REMOVE
+----
+
+=== Use
+
+Set the default credentials for the Aura CLI to use:
+
+[source, shell]
+----
+aura-cli credential use --name NAME_TO_USE
+----
+
+== Config
+
+There are various configuration settings that can be controlled by this command, for example, enabling beta features.
+
+
+=== List
+
+Show the current configuration settings:
+
+[source, shell]
+----
+aura-cli config list
+----
+
+=== Get
+
+Show the value of a chosen setting:
path: modules/ROOT/pages/aura-cli/configuration.adoc
user: login: AlexicaWright
body: ```suggestion
Show the value of a selected setting:
```
created_at: 2025-03-06T13:04:20Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,79 @@
+= Configuration of Aura CLI
+:description: Configure the Neo4j Aura command line interface.
+
+Aura CLI has two commands for its own configuration:
+
+* `credential` - sets of client IDs and client secrets that are used to authenticate with the Aura API that the Aura CLI uses to perform its own operations.
+* `config` - addtional configuration options for the Aura CLI, such as turning Beta features on or off.
+
+
+== Credential
+
+
+=== Add
+
+Adds a set of credentials, client ID and client secret, that were obtained from the Aura Console:
+
+[source, shell]
+----
+aura-cli credential add --name YOUR_LABEL --client-id YOUR_CLIENT_ID --client-secret YOUR_CLIENT_SECRET
+----
+
+=== List
+
+Show all configured credentials that can be used by the Aura CLI:
+
+[source, shell]
+----
+aura-cli credential list
+----
+
+=== Remove
+
+Remove a set of credentials:
+
+[source, shell]
+----
+aura-cli credential list --name NAME_TO_REMOVE
+----
+
+=== Use
+
+Set the default credentials for the Aura CLI to use:
+
+[source, shell]
+----
+aura-cli credential use --name NAME_TO_USE
+----
+
+== Config
+
+There are various configuration settings that can be controlled by this command, for example, enabling beta features.
+
+
+=== List
+
+Show the current configuration settings:
+
+[source, shell]
+----
+aura-cli config list
+----
+
+=== Get
+
+Show the value of a chosen setting:
+
+[source, shell]
+----
+aura-cli config set SETTING\_NAME
+----
+
+=== Set
+
+Set the value for a chosen setting:
path: modules/ROOT/pages/aura-cli/configuration.adoc
user: login: AlexicaWright
body: ```suggestion
Set the value for a selected setting:
```
created_at: 2025-03-06T13:04:31Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: AlexicaWright
body: ```suggestion
Aura CLI  has evolved from a Neo4j Labs to a supported Neo4j product.
```
created_at: 2025-03-06T13:05:04Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: AlexicaWright
body: ```suggestion
It is recommended that you move to the Aura CLI as soon as you are able.
```
created_at: 2025-03-06T13:05:30Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: AlexicaWright
body: ```suggestion
* The name of the CLI is now `aura-cli`.
```
created_at: 2025-03-06T13:05:53Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer-managed keys
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: AlexicaWright
body: ```suggestion
* Customer managed keys
```
created_at: 2025-03-06T13:06:44Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer-managed keys
+* Beta of GraphQL Data APIs
+
+
+== Installation
+
+Download the Aura CLI from link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+It is available as a native binary for Windows, Linux and Mac platforms.
+After downloading the relevant file and extracting the executable, the Aura CLI can be run immediately; there are no dependencies.
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: AlexicaWright
body: ```suggestion
After downloading the relevant file and extracting the executable, the Aura CLI can be run immediately as there are no dependencies.
```
created_at: 2025-03-06T13:07:13Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer-managed keys
+* Beta of GraphQL Data APIs
+
+
+== Installation
+
+Download the Aura CLI from link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+It is available as a native binary for Windows, Linux and Mac platforms.
+After downloading the relevant file and extracting the executable, the Aura CLI can be run immediately; there are no dependencies.
+
+
+== Commands
+
+[cols="3,^1,3", options="header"]
+|====
+| Labs Aura CLI                      | maps to | Aura CLI
+| config                             | →       | config
+| credentials                        | →       | credential       
+| instances                          | →       | instance         
+| snapshots                          | →       | instance → snapshot               
+| tenants                            | →       | tenant            
+| tenants → get-metrics-integration  | →       | instance get `<InstanceID>` returns the URL for metrics integration
+|                                    |         | **NEW**: customer-managed-key
+|                                    |         | **NEW**: data-api (beta)
+|====
+
+
+== Command and flag changes with Aura CLI
+
+As far as was possible, the Aura CLI commands and their flags are the same as for the Labs based Aura CLI.
+However, there are some changes.
+See the following sections.
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: AlexicaWright
body: ```suggestion
However, there are some changes as outlined in the following sections.
```
created_at: 2025-03-06T13:07:48Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer-managed keys
+* Beta of GraphQL Data APIs
+
+
+== Installation
+
+Download the Aura CLI from link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+It is available as a native binary for Windows, Linux and Mac platforms.
+After downloading the relevant file and extracting the executable, the Aura CLI can be run immediately; there are no dependencies.
+
+
+== Commands
+
+[cols="3,^1,3", options="header"]
+|====
+| Labs Aura CLI                      | maps to | Aura CLI
+| config                             | →       | config
+| credentials                        | →       | credential       
+| instances                          | →       | instance         
+| snapshots                          | →       | instance → snapshot               
+| tenants                            | →       | tenant            
+| tenants → get-metrics-integration  | →       | instance get `<InstanceID>` returns the URL for metrics integration
+|                                    |         | **NEW**: customer-managed-key
+|                                    |         | **NEW**: data-api (beta)
+|====
+
+
+== Command and flag changes with Aura CLI
+
+As far as was possible, the Aura CLI commands and their flags are the same as for the Labs based Aura CLI.
+However, there are some changes.
+See the following sections.
+
+
+== Config
+
+It is not possible to remove a setting and its value although the value itself can be changed.
+If deletion is wanted, then remove it from the JSON configuration file, either _$HOME/Library/Preferences/neo4j/cli/config.json_ (MAC) or _%LOCALAPPDATA%\neo4j\cli\config.json_ (Windows).
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: AlexicaWright
body: Shouldn't these be in a code block?
created_at: 2025-03-06T13:08:21Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer-managed keys
+* Beta of GraphQL Data APIs
+
+
+== Installation
+
+Download the Aura CLI from link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+It is available as a native binary for Windows, Linux and Mac platforms.
+After downloading the relevant file and extracting the executable, the Aura CLI can be run immediately; there are no dependencies.
+
+
+== Commands
+
+[cols="3,^1,3", options="header"]
+|====
+| Labs Aura CLI                      | maps to | Aura CLI
+| config                             | →       | config
+| credentials                        | →       | credential       
+| instances                          | →       | instance         
+| snapshots                          | →       | instance → snapshot               
+| tenants                            | →       | tenant            
+| tenants → get-metrics-integration  | →       | instance get `<InstanceID>` returns the URL for metrics integration
+|                                    |         | **NEW**: customer-managed-key
+|                                    |         | **NEW**: data-api (beta)
+|====
+
+
+== Command and flag changes with Aura CLI
+
+As far as was possible, the Aura CLI commands and their flags are the same as for the Labs based Aura CLI.
+However, there are some changes.
+See the following sections.
+
+
+== Config
+
+It is not possible to remove a setting and its value although the value itself can be changed.
+If deletion is wanted, then remove it from the JSON configuration file, either _$HOME/Library/Preferences/neo4j/cli/config.json_ (MAC) or _%LOCALAPPDATA%\neo4j\cli\config.json_ (Windows).
+
+
+== Create a new AuraDB
+
+When creating an Aura instance with the Aura CLI, the memory size is specified with an integer appended with "GB" e.g. "8GB".
+Previously, this was just the integer.
+
+
+== Delete an AuraDB
+
+The Aura CLI does not prompt for confirmation when deleting an AuraDB and starts the operation immediately.
+
+
+== Update an AuraDB
+
+Only the ID can be used to identify the AuraDB to update.
+The same properties can be changed as previously: its name and memory size.
+
+
+== Get AuraDB instance details
+
+This now includes the URL to obtain metrics.
+
+
+== Tenants
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: AlexicaWright
body: Again with tenants...
created_at: 2025-03-06T13:09:11Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer-managed keys
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: rsill-neo4j
body: above, customer managed keys was capitalized - should it be capitalized here as well?
created_at: 2025-03-06T14:29:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer-managed keys
+* Beta of GraphQL Data APIs
+
+
+== Installation
+
+Download the Aura CLI from link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+It is available as a native binary for Windows, Linux and Mac platforms.
+After downloading the relevant file and extracting the executable, the Aura CLI can be run immediately; there are no dependencies.
+
+
+== Commands
+
+[cols="3,^1,3", options="header"]
+|====
+| Labs Aura CLI                      | maps to | Aura CLI
+| config                             | →       | config
+| credentials                        | →       | credential       
+| instances                          | →       | instance         
+| snapshots                          | →       | instance → snapshot               
+| tenants                            | →       | tenant            
+| tenants → get-metrics-integration  | →       | instance get `<InstanceID>` returns the URL for metrics integration
+|                                    |         | **NEW**: customer-managed-key
+|                                    |         | **NEW**: data-api (beta)
+|====
+
+
+== Command and flag changes with Aura CLI
+
+As far as was possible, the Aura CLI commands and their flags are the same as for the Labs based Aura CLI.
+However, there are some changes.
+See the following sections.
+
+
+== Config
+
+It is not possible to remove a setting and its value although the value itself can be changed.
+If deletion is wanted, then remove it from the JSON configuration file, either _$HOME/Library/Preferences/neo4j/cli/config.json_ (MAC) or _%LOCALAPPDATA%\neo4j\cli\config.json_ (Windows).
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: rsill-neo4j
body: what's our convention for file paths?
created_at: 2025-03-06T14:31:45Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub] and works with all versions onf the Aura API.
+Select the latest release and download the archive suitable for your platform and architecture of choice.
+The CLI is fully compatible with Mac, Linux and Windows.
+
+. In your browser, navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+. Download the compressed file that matches your OS.
+  Make a note of the folder where the file is located.
+. Once the file is downloaded, extract the contents.
+. Open a command prompt and move to the location where you extracted the files.
+. Complete the installation by moving the aura-cli executable file into the file path.
+  - Mac users:
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: fiquick
body: ```suggestion
Mac users:
```
created_at: 2025-03-07T15:00:21Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,44 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub] and works with all versions onf the Aura API.
+Select the latest release and download the archive suitable for your platform and architecture of choice.
+The CLI is fully compatible with Mac, Linux and Windows.
+
+. In your browser, navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+. Download the compressed file that matches your OS.
+  Make a note of the folder where the file is located.
+. Once the file is downloaded, extract the contents.
+. Open a command prompt and move to the location where you extracted the files.
+. Complete the installation by moving the aura-cli executable file into the file path.
+  - Mac users:
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: fiquick
body: Maybe remove the bullet point formatting here
created_at: 2025-03-07T15:00:48Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,69 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Log in to the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and use the down arrow to access the account menu.
++
+image::/aura-cli/console-classic-home.png[]
++
+. Navigate to **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a name for the client and then **Create**.
+. Make sure to securely save the generated client ID and client secret as they are required to use the Aura CLI. 
+
+
+=== New unified Aura Console experience
+
+. Log in to the link:https://console.neo4j.io/[Neo4j Aura Console].
+ Navigate to the top right where your account name is displayed and use the down arrow to access the account menu.
++
+image::/aura-cli/unified-console-home.png[]
++
+. Use *Create** from **API Keys** in the menu to create a new key.
++
+image::/aura-cli/unified-console-account-dropdown.png[]
++
++
+image::/aura-cli/unified-console-api-keys.png[]
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: fiquick
body: Hey, this image isn't showing
created_at: 2025-03-07T15:02:03Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,95 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a supported Neo4j product.
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: fiquick
body: Be mindful many users won't have used labs before 
created_at: 2025-03-07T15:04:09Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer-managed keys
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: fiquick
body: Yes please (it's no biggie though, users don't mind so much about the capitalization) 
created_at: 2025-03-07T15:04:58Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,95 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a supported Neo4j product.
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: rsill-neo4j
body: do you suggest linking to the labs page/project?
created_at: 2025-03-10T17:22:28Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub] and works with all versions onf the Aura API.
+Choose the latest release and download the archive suitable for your platform and architecture of choice.
+The CLI is fully compatible with Mac, Linux and Windows.
+
+. Using your browser, navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+. Download the compressed file that matches your computer.
+  Make a note of the folder where the file is located.
+. After the file has been downloaded, extract the contents.
+. Open a command prompt and move to the location where you extracted the files.
+. Complete the installation by moving the aura-cli executable file into the file path.
+  - Mac users:
++
+[source, shell]
+----
+sudo mv aura-cli /usr/local/bin
+----
++
+  - Windows users:
++
+[source, shell]
+----
+move aura-cli c:\windows\system32
+----
+
+Check the installation with:
+
+[source, shell]
+----
+aura-cli -v
+----
+
+You should see the version of the Aura CLI displayed.
+
+[NOTE]
+====
+If you are using a Mac, you may receive a warning from Apple that aura-cli could not be verified.
+If this happens, open **System Settings**, select **Privacy & Security** on the left, and scroll down on the right.
+Select **Open Anyway**.
+This should not happen again.
+The aura-cli has been through the Apple certification process but it can take time to trickle down through the Apple ecosystem.
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: rsill-neo4j
body: removed the critical wording
created_at: 2025-03-10T17:23:44Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
++
+image::/aura-cli/unified-console-home.png[]
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: rsill-neo4j
body: removed
created_at: 2025-03-10T17:24:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed.
+  Click the down arrow.
++
+image::/aura-cli/console-classic-home.png[]
++
+. In the a menu with your account name, click **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a client name, then click **Create**.
+. You will be shown the newly created client ID and client secret.
+  Make sure to securely save these as they are required to use the Aura CLI.
+
+
+=== New unified Aura Console experience
+
+. Login into the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and click the down arrow.
++
+image::/aura-cli/unified-console-home.png[]
++
+. In the menu, click **API Keys**.
++
+image::/aura-cli/unified-console-account-dropdown.png[]
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: rsill-neo4j
body: conflated the two images
created_at: 2025-03-10T17:25:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer-managed keys
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: rsill-neo4j
body: done
created_at: 2025-03-10T17:26:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,69 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
+This also applies to Aura Free.
+====
+
+
+=== Aura console classic
+
+. Log in to the link:https://console.neo4j.io/[Neo4j Aura Console].
+. Navigate to the top right where your account name is displayed and use the down arrow to access the account menu.
++
+image::/aura-cli/console-classic-home.png[]
++
+. Navigate to **Account Details**.
+. In the **Account Details** display, click **Create** under **Aura API** and **Credentials**.
++
+image::/aura-cli/console-classic-api-keys.png[]
++
+. In the pop-up window, enter a name for the client and then **Create**.
+. Make sure to securely save the generated client ID and client secret as they are required to use the Aura CLI. 
+
+
+=== New unified Aura Console experience
+
+. Log in to the link:https://console.neo4j.io/[Neo4j Aura Console].
+ Navigate to the top right where your account name is displayed and use the down arrow to access the account menu.
++
+image::/aura-cli/unified-console-home.png[]
++
+. Use *Create** from **API Keys** in the menu to create a new key.
++
+image::/aura-cli/unified-console-account-dropdown.png[]
++
++
+image::/aura-cli/unified-console-api-keys.png[]
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: rsill-neo4j
body: fixed
created_at: 2025-03-10T17:26:47Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,74 @@
+= Initial configuration
+:description: First configuration of the Neo4j Aura command line interface.
+
+
+== Obtain an Aura API Key
+
+[NOTE]
+====
+You must have some form of payment information in your account to access this functionality.
path: modules/ROOT/pages/aura-cli/initial-configuration.adoc
user: login: rsill-neo4j
body: apparently, this has been decided by the aura team to reduce costs of running the aura api. we should probably not be too transparent with that :thinking: 
created_at: 2025-03-12T10:48:14Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,95 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a supported Neo4j product.
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: rsill-neo4j
body: added a link to the labs page
created_at: 2025-03-12T10:50:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,96 @@
+= Migrating to the Aura CLI
+:description: Migrate to the Neo4j Aura command line interface.
+
+Aura CLI  has evolved from a Neo4j Labs to a proper Neo4j product.
+The Neo4j Labs Aura CLI will continue to be available for installation for the foreseeable future, but without any further development.
+We recommend you to move to the Aura CLI as soon as you are able.
+This section outlines what you must consider to move the Aura CLI.
+
+
+== Behavior
+
+* The name of the CLI is now "aura-cli".
+* Support for using environmental variables has been removed as they can be visible in process listings and can be accidentally logged making them vulnerable to exposure.
+  For sensitive values e.g. Aura API client ID and client secret, a secrets manager is recommended.
+* Neo4j Labs Aura CLI used plural names for commands; the new Aura CLI has singular naming instead.
+* It is not possible to return the raw API response body with the Aura CLI.
+* Flags with the Aura CLI do not have a short form and must be specified in full length.
+
+
+== Feature set
+
+At the time of general availability, the Aura CLI supports these new features compared to the previous Labs project:
+
+* Customer-managed keys
+* Beta of GraphQL Data APIs
+
+
+== Installation
+
+Download the Aura CLI from link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
+It is available as a native binary for Windows, Linux and Mac platforms.
+After downloading the relevant file and extracting the executable, the Aura CLI can be run immediately; there are no dependencies.
+
+
+== Commands
+
+[cols="3,^1,3", options="header"]
+|====
+| Labs Aura CLI                      | maps to | Aura CLI
+| config                             | →       | config
+| credentials                        | →       | credential       
+| instances                          | →       | instance         
+| snapshots                          | →       | instance → snapshot               
+| tenants                            | →       | tenant            
+| tenants → get-metrics-integration  | →       | instance get `<InstanceID>` returns the URL for metrics integration
+|                                    |         | **NEW**: customer-managed-key
+|                                    |         | **NEW**: data-api (beta)
+|====
+
+
+== Command and flag changes with Aura CLI
+
+As far as was possible, the Aura CLI commands and their flags are the same as for the Labs based Aura CLI.
+However, there are some changes.
+See the following sections.
+
+
+== Config
+
+It is not possible to remove a setting and its value although the value itself can be changed.
+If deletion is wanted, then remove it from the JSON configuration file, either _$HOME/Library/Preferences/neo4j/cli/config.json_ (MAC) or _%LOCALAPPDATA%\neo4j\cli\config.json_ (Windows).
path: modules/ROOT/pages/aura-cli/migration.adoc
user: login: rsill-neo4j
body: it's now in backticks
created_at: 2025-03-12T10:50:44Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,298 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword "tenant".
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
The Aura CLI makes heavy use of console commands containing the keyword `tenant`.
```
created_at: 2025-03-12T12:37:51Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,298 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword "tenant".
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: Perhaps an explanation why? A new user doesn't know the relation between tenant and project. You could link to https://neo4j.com/docs/aura/new-console/#_topology for some background.
created_at: 2025-03-12T12:39:11Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,33 @@
+= Working with AuraDB tenants
+:description: Work with AuraDB tenants in the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword "tenant".
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead.
path: modules/ROOT/pages/aura-cli/auradb-tenants.adoc
user: login: AlexicaWright
body: AS above
created_at: 2025-03-12T12:39:55Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,298 @@
+= Managing AuraDB instances
+:description: Manage AuraDB instance with the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword "tenant".
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead.
+====
+
+The Aura CLI provides a full set of commands to manage the lifecycle of an AuraDB instance.
+
+
+== Create
+
+Before you can create an AuraDB instance, make sure that your desired configuration is available in a project where the AuraDB will reside.
+Get these by using the tenant command from xref:aura-cli/auradb-tenants.adoc[Working with AuraDB tenants].
+If you are using Aura Free, there is no need to do this as the configurations are fixed.
+Create an AuraDB instance with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR\_INSTANCE\_NAME --type free-db --await 
+----
+
+For other Aura plans, provide the following:
+
+* Instance name
+* Memory
+* Cloud provider
+* Cloud region
+* Type
+
+You can find the values for these by using the tenant commands.
+Once you have them, proceed with:
+
+[source, shell]
+----
+aura-cli instance create --name YOUR_INSTANCE_NAME --cloud-provider YOUR_CLOUD_PROVIDER --region CLOUD_REGION --memory MEMORY --type  AURA_INSTANCE_TYPE --tenant-id YOUR_TENANT_ID 
+----
+
+You can skip `--tenant-id` if you have set a default tenant.
+
+The response provides the connection details for the request AuraDB and contains authentication details, the username and password.
+Make sure to record these safely and securely as they are only shown once.
+
+
+== List
+
+To see a list of AuraDB instances, use:
+
+[source, shell]
+----
+aura-cli instance list
+----
+
+Use the table format output option to improve readability:
+
+[source, shell]
+----
+aura-cli instance list --output table 
+----
+
+From the list, you can then use the ID for an AuraDB instance to get detailed information about it, including the URL to use for metrics:
+
+[source, shell]
+----
+aura-cli instance get YOUR_INSTANCE_ID
+----
+
+
+== Update
+
+You can change name, memory, or both for a deployed AuraDB instance:
+
+[source, shell]
+----
+aura-cli instance update YOUR_INSTANCE_ID --name NEW_NAME --memory NEW_MEMORY
+----
+
+You may omit `--name` and `--memory` as needed but at least one must be present.
+
+
+== Delete
+
+If you want to delete an instance, keep in mind that the operation starts immediately and without requiring confirmation.
+Therefore, use with caution:
+
+[source, shell]
+----
+aura-cli instance delete YOUR_INSTANCE_ID
+----
+
+
+== Pause and resume
+
+A paused AuraDB instance incurs a lower cost per hour than when it is running.
+Pausing AuraDB instances when they are not in use and resuming them when needed is an effective mechanism for cost control.
+
+
+=== Pause
+
+[source, shell]
+----
+aura-cli instance pause YOUR_INSTANCE_ID
+----
+
+
+=== Resume
+
+[source, shell]
+----
+aura-cli instance resume YOUR_INSTANCE_ID
+----
+
+
+== Snapshots
+
+A snapshot is a copy of an AuraDB instances data at a specific point in time.
+It can then be restored with the `overwrite` command of the Aura CLI.
+
+
+=== Create
+
+An instance must be running for a snapshot to be created:
+
+[source, shell]
+----
+aura-cli instance snapshot create --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== List
+
+All of the snapshots for an AuraDB instance are returned in the response.
+
+[source, shell]
+----
+aura-cli instance snapshot list --instance-id YOUR_INSTANCE_ID
+----
+
+
+=== Get
+
+To obtain the details for a single snapshot, use the `get` command:
+
+[source, shell]
+----
+aura-cli instance snapshot SNAPSHOT_ID --instance-id YOUR_INSTANCE_ID
+----
+
+
+## Overwrite
+
+You can overwrite the content of one AuraDB instance with the content of another while leaving the configuration as is.
+However, the destination storage must be large enough.
+Use a snapshot of the source AuraDB instance.
path: modules/ROOT/pages/aura-cli/auradb-instances.adoc
user: login: AlexicaWright
body: ```suggestion
This requires that the destination storage is large enough.
You use a snapshot of the source AuraDB instance for this operation.
```
created_at: 2025-03-13T15:09:12Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,50 @@
+= Installation
+:description: Install the Neo4j Aura command line interface.
+
+[NOTE]
+====
+The Aura CLI makes heavy use of console commands containing the keyword "tenant".
+To be consistent with that, all Aura CLI documentation pages use the term "tenant", which other parts of the documentation refer to as "project" instead.
+====
+
+The Aura CLI is available on link:https://github.com/neo4j/aura-cli/releases[GitHub] and works with all versions onf the Aura API.
+Select the latest release and download the archive suitable for your platform and architecture of choice.
+The CLI is fully compatible with Mac, Linux and Windows.
+
+. In your browser, navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
path: modules/ROOT/pages/aura-cli/installation.adoc
user: login: AlexicaWright
body: ```suggestion
. Navigate to link:https://github.com/neo4j/aura-cli/releases[https://github.com/neo4j/aura-cli/releases].
```
created_at: 2025-03-13T15:23:16Z
author_association: COLLABORATOR

PR comments:
user: login: rsill-neo4j
created_at: 2025-03-06T14:34:55Z
body: applied a chunk of the suggestions by @AlexicaWright 

i left tenant vs projects + some other things untouched for @LackOfMorals to have a look
author_association: CONTRIBUTOR
user: login: neo-technology-commit-status-publisher
created_at: 2025-03-10T17:28:46Z
body: This PR includes documentation updates
View the updated docs at https://neo4j-docs-aura-622.surge.sh

New pages:
- [Managing AuraDB instances](https://neo4j-docs-aura-622.surge.sh/aura/aura-cli/auradb-instances)
- [Working with AuraDB tenants](https://neo4j-docs-aura-622.surge.sh/aura/aura-cli/auradb-tenants)
- [Configuration of Aura CLI](https://neo4j-docs-aura-622.surge.sh/aura/aura-cli/configuration)
- [Aura CLI](https://neo4j-docs-aura-622.surge.sh/aura/aura-cli)
- [Initial configuration](https://neo4j-docs-aura-622.surge.sh/aura/aura-cli/initial-configuration)
- [Installation](https://neo4j-docs-aura-622.surge.sh/aura/aura-cli/installation)
- [Migrating to the Aura CLI](https://neo4j-docs-aura-622.surge.sh/aura/aura-cli/migration)
<!-- Sticky Pull Request Commentdocs-pr-changes -->
author_association: COLLABORATOR
user: login: recrwplay
created_at: 2025-03-14T14:43:20Z
body: Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.
<!-- Sticky Pull Request Commentdocs-pr-changes -->
author_association: CONTRIBUTOR