AuraDB Enterprise tier customers have a dedicated IP endpoint to access their AuraDB Instance.

For the Aura Console, the fixed IP addresses are listed here.

 

To work out the fixed IP address used to access your AuraDB Instances in your environment, you can proceed as follows:

1. Select, or if none exist create an AuraDB Instance in your environment
2. Copy the connection URI of that AuraDB Instance
3. Remove the protocol specifier of the URI. Example: 

   neo4j+s://abcd1234.databases.neo4j.io => keep only abcd1234.databases.neo4j.io

4. Run from your environment in a command prompt nslookup dbid.databases.neo4j.io (adjust the dbid as appropriate). Example: 

   nslookup abcd1234.databases.neo4j.io

 

If your AuraDB Instance is on AWS, you would see at least 3 IPv4 addresses - one IPv4 address per availability zone - (some regions have up to 5 availability zones and hence there would be more):

$ nslookup abcd1234.databases.neo4j.io
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
Name:	abcd1234.databases.neo4j.io
Address: 50.161.105.214
Name:	abcd1234.databases.neo4j.io
Address: 54.233.121.213
Name:	abcd1234.databases.neo4j.io
Address: 54.167.147.97

If your AuraDB Instance is running on GCP or Azure, you will only see 1 single IPv4 address instead:

$ nslookup a1b2c3d4.databases.neo4j.io
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
Name:	a1b2c3d4.databases.neo4j.io
Address: 51.161.125.214