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:
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["This page explains how to set up a Private Service Connect endpoint for Blockchain Node Engine."],["To use this feature, you must first create a Private Service Connect-enabled node, noting that this configuration is permanent once the node is created."],["After creating the node, complete the setup by following the Private Service Connect configuration guide using the target service information from your node's output."],["Using a Private Service Connect-enabled node is similar to using a public node, but you must ensure the network is set up correctly and use the Private Service Connect static IP address instead of the standard DNS endpoint."],["If you have Private Service Connect enabled, be aware that a manual migration might be necessary to stay compatible with future updates, and you will receive notifications of any required actions."]]],[]]
