|
1 | 1 | - A [Neo4j deployment](https://neo4j.com/deployment-center/). |
| 2 | + |
| 3 | + The following video shows how to set up a Neo4j Aura deployment: |
| 4 | + |
| 5 | + <iframe |
| 6 | + width="560" |
| 7 | + height="315" |
| 8 | + src="https://www.youtube.com/embed/fo8uDIm1zCE" |
| 9 | + title="YouTube video player" |
| 10 | + frameborder="0" |
| 11 | + allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" |
| 12 | + allowfullscreen |
| 13 | + ></iframe> |
| 14 | + |
2 | 15 | - The username and password for the user who has access to the Neo4j deployment. The default user is typically `neo4j`. |
3 | 16 |
|
4 | | - - For a Neo4j AuraDB instance, the defaut user's is typically set when the instance is created. |
| 17 | + - For a Neo4j Aura instance, the defaut user's is typically set when the instance is created. |
5 | 18 | - For an AWS Marketplace, Microsoft Azure Marketplace, or Google Cloud Marketplace deployment of Neo4j, the default user is typically set during the deployment process. |
6 | 19 | - For a local Neo4j deployment, you can [set the default user's initial password](https://neo4j.com/docs/operations-manual/current/configuration/set-initial-password/) or [recover an admin user and its password](https://neo4j.com/docs/operations-manual/current/authentication-authorization/password-and-user-recovery/). |
7 | 20 |
|
8 | 21 | - The connection URI for the Neo4j deployment, which starts with `neo4j://`, `neo4j+s://`, `bolt://`, or `bolt+s://`; followed by `localhost` or the host name; and sometimes ending with a colon and the port number (such as `:7687`). For example: |
9 | 22 |
|
10 | | - - For a Neo4j AuraDB deployment, browse to the target Neo4j instance in the Neo4j Aura account and click **Connect > Drivers** to get the connection URI, which follows the format `neo4j+s://<host-name>`. A port number is not used or needed. |
| 23 | + - For a Neo4j Aura deployment, browse to the target Neo4j instance in the Neo4j Aura account and click **Connect > Drivers** to get the connection URI, which follows the format `neo4j+s://<host-name>`. A port number is not used or needed. |
11 | 24 | - For an AWS Marketplace, Microsoft Azure Marketplace, or Google Cloud Marketplace deployment of Neo4j, see |
12 | 25 | [Neo4j on AWS](https://neo4j.com/docs/operations-manual/current/cloud-deployments/neo4j-aws/), |
13 | 26 | [Neo4j on Azure](https://neo4j.com/docs/operations-manual/current/cloud-deployments/neo4j-azure/), or |
|
20 | 33 |
|
21 | 34 | - The name of the target database in the Neo4j deployment. A default Neo4j deployment typically contains two standard databases: one named `neo4j` for user data and another |
22 | 35 | named `system` for system data and metadata. Some Neo4j deployment types support more than these two databases per deployment; |
23 | | - Neo4j AuraDB instances do not. |
| 36 | + Neo4j Aura instances do not. |
24 | 37 |
|
25 | 38 | - [Create additional databases](https://neo4j.com/docs/operations-manual/current/database-administration/standard-databases/create-databases/) |
26 | 39 | for a local Neo4j deployment that uses Enterprise Edition; or for Neo4j on AWS, Neo4j on Azure, or Neo4j on GCP deployments. |
|
0 commit comments