Skip to main content

​
What is Static Egress IP?

Static Egress IP provides a fixed, predictable IP address for outbound traffic originating from StreamNative Cloud. Instead of dynamic IP addresses that change over time, your environment uses the same IP address for all outbound connections, making it easier to:
  • Configure firewall rules on your side
  • Set up network allowlists for external services
  • Maintain consistent security policies
  • Simplify network monitoring and logging

​
Supported Traffic Types

Static Egress IP applies to outbound data flows including:
  • Connectors: Both source and sink connectors that connect to external systems
  • Pulsar Functions: Functions that make outbound network calls to external APIs or services
  • Other outbound traffic: Any network traffic initiated from your StreamNative Cloud environment
Static Egress IP only affects outbound (egress) traffic from StreamNative Cloud to external systems. It does not affect inbound (ingress) traffic to your environment.

​
Availability

​
Cluster Types

Static Egress IP is enabled by default for:
  • All new Dedicated clusters
  • BYOC clusters
  • Serverless clusters
Some older legacy clusters may not have Static Egress IP enabled. If you have a legacy cluster that needs this feature, contact StreamNative support to enable it.

​
Cloud Provider Support

Cloud ProviderStatus
AWS✅ Enabled by default
Azure✅ Enabled by default
Alibaba Cloud✅ Enabled by default
GCP✅ Enabled by default in new environments. Contact support for more details.

​
IP Address Scoping

Static egress IP addresses are assigned at the environment level. All clusters within the same environment share the same static egress IP address:
  • BYOC: All clusters in the same BYOC environment share one static egress IP
  • Dedicated: All clusters in the same pool and region (e.g., aws/us-east-1) share one static egress IP
  • Serverless: All clusters in the same pool and region (e.g., gcp/us-west-1) share one static egress IP
The static egress IP belongs to the environment (the underlying infrastructure including Kubernetes, networking, DNS, and applications). Clusters run within these environments and inherit the environment’s static egress IP for their outbound traffic.

​
Accessing Your Static Egress IP

Static egress IP addresses are currently not exposed in the StreamNative Cloud Console UI, CLI, or API. This functionality will be added in future releases.
To retrieve your static egress IP address: Open a support ticket through the StreamNative support portal. When contacting support, specify:
  • Your environment ID or cluster name
  • The purpose for needing the static egress IP (firewall configuration, allowlist setup, etc.)
The StreamNative team will provide the IP address so you can configure your firewall or network policies accordingly.

​
Use Cases

​
Firewall Configuration

Configure your firewall to allow traffic from StreamNative Cloud: 
# Example firewall rule (adjust for your firewall system)
# Allow traffic from StreamNative static egress IP
iptables -A INPUT -s <STATIC_EGRESS_IP> -j ACCEPT

​
Database Allowlists

Add the static egress IP to your database allowlist: 
-- Example for PostgreSQL (adjust for your database)
-- Add StreamNative egress IP to allowed connections
-- Contact support to get your actual static egress IP

​
API Gateway Configuration

Configure your API gateway to accept requests from StreamNative: 
# Example API gateway configuration
allowedIPs:
  - "<STATIC_EGRESS_IP>"  # Replace with your actual IP from support

​
Future Enhancements

StreamNative is working to make static egress IP addresses accessible through:
  • StreamNative Cloud Console UI: View and manage egress IPs in the web interface
  • CLI (snctl): Retrieve egress IP information via command line
  • API: Programmatic access to egress IP configuration
These features are planned for future releases. Check the release notes for updates.