To ensure we are updating all relevant channels, this connectivity scenario was resolved by explicitly setting encryption to on.
Aura as a hosted service is, by design, more rigid on security than a user might set up when self hosting.
As such users should look to explicitly enable encryption in their driver connection.
For example here, the issue was reolsved by altering the connection to the following :
For example :
const driver = neo4j.driver('neo4j://<your_aura_DBiD>.databases.neo4j.io:7687', neo4j.auth.basic('neo4j', password), { encrypted: 'ENCRYPTION_ON' })
For other driver types, please refer to section 2.4.1 of the driver docs as here : Client applications - Neo4j Driver Manual and adopt the appropriate setting to set encryption to on, or True.
We'll be updating our documents and Aura UI to more explicitly state this setting requirement.