Public IPs
A Public IP is a persistent public IPv4 address that you can attach to a VM to enable inbound internet connectivity. Public IPs are independent resources that can be created, managed, and reassigned between VMs without affecting the VM itself.
How Public IPs work
By default, VMs can make outbound connections to the internet through the external gateway using a shared IP address. However, to receive inbound connections from the internet, a VM must have a Public IP attached to it.
Public IPs are persistent - once allocated, the IP address belongs to your resource group until you explicitly delete it. You can attach and detach Public IPs from VMs as needed, and the IP address remains constant. This allows you to:
- Replace a VM while keeping the same public IP address
- Temporarily detach a Public IP from one VM and attach it to another
- Reserve IP addresses for future use
When to use Public IPs
You need a Public IP when:
- Running web servers or APIs that accept inbound HTTP/HTTPS traffic from the internet
- Providing SSH access to VMs from external networks
- Hosting services that need a stable, publicly accessible IP address
- Running applications that require inbound connections on specific ports
You don't need a Public IP when:
- VMs only need to communicate with each other within the VPC (private IPs are sufficient)
- VMs only make outbound connections to the internet (the external gateway provides this by default)
- Running internal services not accessible from the public internet
Public IPs and security groups
Attaching a Public IP to a VM is not sufficient for inbound internet access. You must also configure security group rules to allow the desired inbound traffic. The default security group blocks all inbound traffic from the internet.
For example, to allow SSH access to a VM with a Public IP, you need:
- A Public IP attached to the VM
- A security group rule allowing TCP port 22 from the source IP addresses you want to permit
Outbound traffic with Public IPs
When a VM has a Public IP attached, outbound traffic from that VM uses the Public IP address as the source IP. This differs from VMs without Public IPs, which use a shared IP address managed by the external gateway.
Limitations
- Public IPs use IPv4 addresses. IPv6 support is not currently available.
- Each VM can have at most one Public IP attached
- Public IP addresses are allocated from evroc's address space and cannot be imported from external sources
Next steps
- Learn about Security Groups for controlling traffic to VMs with Public IPs
- Understand the Default Networking Setup and the role of the external gateway
- See the Functional Description for more details on networking components