Skip to main content
This feature is in public preview.
Instances can have a public IPv4 address for internet connectivity. Public IPs are enabled or disabled when creating an instance and cannot be changed afterward. IPv6 is not yet supported.

​
Enabling a public IP

Set --public-ipv4 when creating an instance to assign a public IP address:
The public IP is auto-assigned when the instance is created and released when the instance is deleted. IPs are not shared between instances. Without --public-ipv4, the only inbound port open on the instance is SSH (TCP port 22); nothing else is reachable from the internet. Connect with sf instance ssh.

​
Internet connectivity

Instances reach the internet via IPv4 using TCP, UDP, and ICMP; other layer 4 protocols are blocked. Outbound SMTP (TCP and UDP port 25) is blocked—contact SFC if you need this restriction removed. Inbound traffic is governed by firewall rules. Source CIDRs are restricted to public IPv4 addresses, and because internet source IPs are spoofable, firewall rules should be treated as security hardening, not as a security mechanism. Additionally, all traffic to an instance’s UDP or TCP port 68 is blocked to prevent DHCP attacks.

​
Finding an instance’s IP

An instance’s IP is available through sf instance get and sf instance list.
The response includes the public_ip field (if enabled).