In some cases, event broker services may need to initiate outbound connections with external hosts that are outside of the virtual private network where they are deployed. Typically, an external host permits connections to be initiated through their firewall based on an allowed list of IP addresses.
Connections to external hosts can include these reasons:
- using REST destination points (RDPs) to deliver REST requests to a remote server, for example, for outbound RDPs by subscribing applications (consumers)
- linking to a replication mate (for disaster recovery)
- creating Dynamic Message Routing (DMR) links to another node
- creating VPN bridges made to other brokers
- spawning new connections to an LDAP database
-
For Dedicated Region and Public Region deployments, the availability of static IPs depends on the deployment type and cloud provider you choose. For more information, see Static IP Availability for Messaging Connectivity in Public Regions and Dedicated Regions. If static IPs are available, you can contact SAP to request the static IP address of the network address translation (NAT).
For Kubernetes-based deployments in Customer-Controlled Regions, customers can get the static IP address themselves their own because they own the deployment. For more information, see Using NAT with Static IP Addresses for Outbound Connections for Kubernetes-Based Deployments.