Configure Private Service Connect for Blockchain Node Engine

Warning: Private Service Connect enabled nodes may require a manual migration effort to remain compatible with future versions of the product. If this feature is enabled, you will be notified of these changes along with any required action to avoid disruption.

This page describes how to configure a Private Service Connect endpoint for use with Blockchain Node Engine.

1. Create a Private Service Connect-enabled node. The endpoint configuration cannot be changed once created.

2. Complete the setup by following the Private Service Connect configuration guide. The target service can be found in the output of your node.

3. Once the Private Service Connect-enabled node has been successfully set up, working with it closely resembles the process for a node with public endpoints, with just two essential adjustments to the standard workflow:

   1. Ensure the network is set up appropriately for the use case as described in Access published services through endpoints.
   2. During node interaction, employ the Private Service Connect static IP address along with the designated port for your chosen interaction, in place of the standard DNS endpoint.