Private Endpoints Notes

Describes restrictions and notes for private endpoints on Visual Builder.

  • After you update the network access to use a private endpoint, or after the provisioning completes where you configure a private endpoint, you can view the network configuration on the Visual Builder Details page under the Network section.

    The Network section shows the following information for a private endpoint:

    • Subnet: This includes a link for the subnet associated with the private endpoint.
    • Private endpoint IP: Shows the private endpoint IP for the private endpoint configuration.
    • Network security groups: This field includes links to the NSG(s) configured with the private endpoint.

  • You can map a custom endpoint to a private endpoint during the provision process, or after provisioning completes.

  • You can specify up to five NSGs to control access to your instance.

  • You can change the private endpoint Network Security Group (NSG) for the instance.

    To change the NSG for a private endpoint, do the following:

    1. On the Visual Builder page, select the instance you want to edit.

    2. On the Visual Builder Details page, click Edit. In the Edit instance, click Show network advanced options to open the pane and edit the details in the Network security groups (NSGs) pane.

  • You can connect your private endpoint to an ATP database in the same VCN and subnet. See Access an ATP Database Configured as a Private Endpoint. To connect to a database in a different VCN, you need to configure private views using DNS in the VCNs.

  • Modifying a private IP address is not allowed after you provision an instance, regardless of whether the IP address is automatically assigned or if you enter a value in the Private IP address field.

  • You cannot change the node count for private endpoint-enabled Visual Builder instances. You will need to raise a service request to increase the node count for private-endpoint enabled Visual Builder instances.

  • When using a load balancer in front of a private endpoint, use the private endpoint IP for the Load Balancer Backend, and forward traffic on port 443. You also need to share the IP address of the public load balancer with your DevOps/Networking team so they can update the DNS registration to make the instance URL publicly accessible.