Create secrets for Neo4j connection

This feature is experimental and not ready for use in production. It is only available as part of an Early Access Program, and can go under breaking changes until general availability.

The procedures require Neo4j connection parameters to be specified in order to communicate with Neo4j GDS/AuraDS. There is built-in support for the procedures to fetch Google Secret Manager secrets and feed them into the procedure as arguments.

The secret value needs to be constructed as a JSON map, which should at least contain the following properties.

Secret Value
{
    "neo4j_uri": "<a valid Neo4j URI>", (1)
    "neo4j_user": "<username>", (2)
    "neo4j_password": "<password>", (3)
    "neo4j_db_name": "<database>" (4)
}
1 A valid Neo4j URI, such as neo4j+s://my.neo4j.host. Refer to Connection URI Examples for more information.
2 The user to use while establishing the connection.
3 The password to use while establishing the connection.
4 Name of the target database to connect to. Default is neo4j.

Creating secret in GCP

  1. Navigate to Secret Manager and select Create Secret.

    Create secret

  2. Name your secret, paste in the above JSON value with placeholders replaced to reflect your environment and configure the rest of the secret based on your requirements.

    Configure secret

  3. Once your secret is created, click the Actions button on the newly created version and select Copy Resource Name (1). This is the value you will need to provide while invoking the procedure.

    Copy resource name