Disabling network access #536
Conversation
|
|
||
| The Aura Console runs in a separate VPC, separate from the rest of Aura. | ||
| An Aura instance can be publicly available, completely private, or configured to allow both public and private access. | ||
| To configure network access, you need to be authorized to access the part of [your system's?] infrastructure that runs and handles these instances as well as the networking used to establish secure connections between the database and the application's VPC. This includes the ability to connect over the cloud provider's private link and private endpoint. |
There was a problem hiding this comment.
@AlexicaWright do you think the original writer meant authorized access to the "customer insfrastructure", "Aura infrastructure" or both?
There was a problem hiding this comment.
User=customer, we speak directly to the user. I think what is meant is that in order to configure access, you need access to either the console, or whatever equivalent the user has in their setup.
| . Create a VPC endpoint | ||
| . Accept endpoint connection requests and enable private DNS in the cloud provider's console | ||
| . Disable public traffic (optional). | ||
| If you disable public traffic it is highly recommended to link:https://support.neo4j.com/s/article/13174783967507-How-To-Test-Connectivity-Through-The-Private-Endpoint[Test Connectivity Through The Private Endpoint] |
There was a problem hiding this comment.
I was wondering, if I should put the steps in here? They are available in a KB and it's a major pain point that customer's are not checking their connectivity.
There was a problem hiding this comment.
There should not be a link to a Support article. If the information there is needed, better to lift it from there and put it here somewhere.
|
|
||
| .Network access visual | ||
| [.shadow] | ||
| image::network_access.png[] |
There was a problem hiding this comment.
The shield icon is a bit wonky in UPX designs.
| @@ -65,7 +93,7 @@ Aura VPCs can't initiate connections back to your VPCs. | |||
| ==== Browser and Bloom access over private endpoints | |||
|
|
|||
| To connect to your instance via Browser or Bloom, you must use a dedicated VPN. | |||
| This is because when you disable public access to your instance, this applies to all connections, including those from your computer when using Browser or Bloom. | |||
| This is because when you xref:[disable public access] to your instance, this applies to all connections, including those from your computer when using Browser or Bloom. | |||
There was a problem hiding this comment.
Do you think I should link to the disabling public access section here, and in the xrefs below?
There was a problem hiding this comment.
Yes, why not? I think it would be helpful.
|
|
||
| The Aura Console runs in a separate VPC, separate from the rest of Aura. | ||
| An Aura instance can be publicly available, completely private, or configured to allow both public and private access. | ||
| To configure network access, you need to be authorized to access the part of [your system's?] infrastructure that runs and handles these instances as well as the networking used to establish secure connections between the database and the application's VPC. This includes the ability to connect over the cloud provider's private link and private endpoint. |
There was a problem hiding this comment.
User=customer, we speak directly to the user. I think what is meant is that in order to configure access, you need access to either the console, or whatever equivalent the user has in their setup.
| . Create a VPC endpoint | ||
| . Accept endpoint connection requests and enable private DNS in the cloud provider's console | ||
| . Disable public traffic (optional). | ||
| If you disable public traffic it is highly recommended to link:https://support.neo4j.com/s/article/13174783967507-How-To-Test-Connectivity-Through-The-Private-Endpoint[Test Connectivity Through The Private Endpoint] |
There was a problem hiding this comment.
There should not be a link to a Support article. If the information there is needed, better to lift it from there and put it here somewhere.
| @@ -65,7 +93,7 @@ Aura VPCs can't initiate connections back to your VPCs. | |||
| ==== Browser and Bloom access over private endpoints | |||
|
|
|||
| To connect to your instance via Browser or Bloom, you must use a dedicated VPN. | |||
| This is because when you disable public access to your instance, this applies to all connections, including those from your computer when using Browser or Bloom. | |||
| This is because when you xref:[disable public access] to your instance, this applies to all connections, including those from your computer when using Browser or Bloom. | |||
There was a problem hiding this comment.
Yes, why not? I think it would be helpful.
|
This PR includes documentation updates Updated pages: |
No description provided.