Manage IP addresses on an instance

Give your instance a public IP that stays the same by reserving it, and a private VPC IP to reach one of your VPCs. All of an instance’s addresses are on its Network & Security tab, under Network:

Address	What it is
Egress IP	The instance’s outgoing address: the public address that outside servers see when the instance connects out, for example to download a package or call an API. Give it to a service that allows only known addresses.
Public IP	The addresses the instance is reached at from the internet. A floating IP, tagged Floating, comes from E2E’s pool. A reserved IP, tagged Reserved, stays yours and keeps its address.
VPC IP	A private address reserved from one of your VPCs, so the instance can reach that VPC privately. An instance has one VPC IP at a time.

Before you begin

• A role in the project that lets you update instances.
• Permission to create reserved IPs, if you will reserve a new one.
• For a VPC IP, an Active MyAccount VPC in the instance’s region whose address range E2E assigned, rather than one with a custom CIDR.

A reserved IP is a product of its own and is billed monthly. See pricing.

Which addresses change after a stop and start

A floating IP is returned when the instance stops. On start, the instance gets one from E2E’s pool, which can differ from the one it had. The egress IP, which is the instance’s outgoing address, is also released on stop and reassigned on start, so it can change too. Update any allow list that holds it. A reserved IP keeps its address across stops and starts.

To give users, SSH clients, or DNS records an address that stays the same, use a reserved IP.

Keep the public IP by reserving it

To turn the instance’s floating IP into a reserved IP, go to Network & Security > Network and click Convert to reserved on the floating IP. The address is now yours: it stays the same across stops and starts, and you can attach it to another instance after this one is deleted.

You can also give an instance a reserved IP when you create it, and keep its IP when you delete it:

• When you create an instance, Reserve IP Address under Network & Security attaches one of the project’s available reserved IPs.
• When you delete an instance, the delete dialog offers to reserve its public IP. See Delete an instance.

Attach a reserved IP

1. Go to Network & Security > Network.
2. Click Add Reserved IP.
3. Pick an available reserved IP and click Attach, or click Reserve a new IP to reserve one first.

The address joins the instance’s public IPs, marked Reserved. You can attach more than one reserved IP to an instance.

If reserving a new IP is refused because your account has reached its limit, see How many reserved IPs can I have?

When the instance has no floating IP, its SSH command uses the first reserved IP.

Detach a public IP

Detaching the floating IP when no reserved IP is left removes the instance’s public access. To detach an address, click Detach next to it, tick Are you sure you want to proceed?, and confirm.

Some features need the instance to keep an address, so keep one attached in these cases:

• While SSH is on, the instance keeps at least one IP. Attach a reserved IP or a VPC IP before you detach its only address.
• While the instance has security groups attached, it keeps at least one floating or reserved IP. Attach another before you detach this one.

When you delete an instance, its reserved IPs are detached and stay reserved in the project. They are still billed, and you can attach them to another instance.

Release a reserved IP

A reserved IP is billed monthly until you delete it, even after the instance it was on is deleted. To release one, detach it from the instance, then open Networking > Reserve IP (Manage Reserved IP). Select Delete Reserve IP in its row, tick I understand and want to delete Reserve IP ., and select Delete. Deleting an IP that is still attached is refused with “The IP is currently assigned to a service. Please detach it before proceeding.”

Attach a VPC IP

A VPC IP connects the instance to one of your VPCs, so it can reach the other resources in that VPC privately. VPC IPs are available in Delhi and Chennai, and you can attach one in any instance status.

1. Choose Attach VPC from the instance’s actions menu, or use the VPC IP section of Network & Security > Network.
2. Pick an Available VPC IP and click Attach, or click Reserve New VPC IP to reserve one first. In Reserve from VPC IP, the region is already the instance’s; pick My Account Project and VPC. Reserving takes two addresses from the VPC.

TIR schedules the connection. The VPC IP shows Connecting, then Connected, Idle, or Connection Failed. Idle means the VPC IP is reserved and free to attach. An instance holds one VPC IP, so Attach VPC is available only until it has one.

Once connected, the VPC IP has two addresses. Inbound IP is the address your MyAccount nodes in the VPC use to reach the instance. Outbound IP is the address the instance’s traffic to the VPC comes from, so allow it in your nodes’ security groups.

When the instance has neither a floating nor a reserved IP, its SSH command uses the VPC IP. You then connect from a machine in the same VPC.

Detach a VPC IP

You can detach a VPC IP once it has finished Connecting.

1. Go to Network & Security > Network and detach the address under VPC IP. Detach VPC opens and warns that the instance will lose its connection to the VPC.
2. Tick the box and click Detach VPC.

When the VPC IP is the instance’s only IP, attach another IP first if SSH is on or the instance has open security-group ports. Deleting the instance also detaches its VPC IP.

To reach an app on one of these addresses, see Open a port on an instance. For problems with an address, see Troubleshooting TIR Instances.