StreamNative Cloud offers data streaming services, such as Pulsar, Kafka, Functions, Connectors, Schema Registry, and Audit Logs, that can be shared across organizations over the internet on AWS. StreamNative Cloud services include internet connectivity for the all cluster types.

​
Ingress IP addresses

Because the cloud infrastructure used by StreamNative Cloud does not guarantee static IP addresses for ingress public endpoints, such as for Pulsar brokers, Pulsar Admin API, and Metrics API, DNS is used to provide a consistent address. The underlying IP addresses might be stable for a period of time, but are subject to change at any time, and they can assume any public IP the cloud provider uses in the region where the cluster is located, so they should not be relied upon for any use. StreamNative Cloud does not provide static public ingress IP addresses. Instead, DNS resolution is used to provide consistent endpoints for each Pulsar cluster. The DNS names follow a predictable pattern based on your cluster configuration. For example, if your cluster domain is pc-9293889f.<pool-name>.<cloud>.snio.cloud (where pc-9293889f is your unique cluster ID), and you are using the default broker prefix, all broker endpoints will follow a standardized format as shown in the examples below. If the cluster is a Class-Engine cluster, the broker endpoints will be of the following format: 
pb0-pc-9293889f.<pool-name>.<cloud>.snio.cloud
pb1-pc-9293889f.<pool-name>.<cloud>.snio.cloud
pb2-pc-9293889f.<pool-name>.<cloud>.snio.cloud
...
If the cluster is a Ursa-Engine cluster, the broker endpoints include the availability zone name in the DNS name for zone-aware routing. For example: 
pb0-pc-9293889f.<zone-name>.<pool-name>.<cloud>.snio.cloud
pb1-pc-9293889f.<zone-name>.<pool-name>.<cloud>.snio.cloud
pb2-pc-9293889f.<zone-name>.<pool-name>.<cloud>.snio.cloud
...
The following blogs describe how the common outbound proxies handle IP address changes:

​
Egress IP addresses

StreamNative Cloud doesn’t provide egress public IP addresses that you can use for communicating between StreamNative clusters (within public networking) in StreamNative Cloud and external data sources and sinks. This feature will be supported in the future.