To manage your network configuration, you can allocate ephemeral or reserved IP addresses depending on your need for temporary or permanent connectivity. The Linode must be configured to support additional addresses. Before you allocate, open a support ticket to request additional addresses.
Ephemeral IPv4 addresses are temporary and tied directly to a specific resource rather than your account. They're typically recycled and returned to the pool once the associated resource is deleted.
Reserved IPs are static, permanent addresses ideal for services requiring a consistent entry point. A reserved IP is permanently locked to the specific region where it was created. You can create a reserved IP independently of a Linode, allowing it to exist on your account with or without an active assignment, but it can only be assigned to resources within that same region. Charges apply as soon as a reserved IP is added to your account, regardless of whether it's assigned to a resource.
You can run this operation for Linodes with legacy configuration interfaces. You can't use it for Linodes with Linode interfaces. To allocate an IP for a Linode with Linode interfaces, use the Add a Linode interface operation.
Permissions and scopes
To call this operation, you need permissions, based on the model you're using:
-
OAuth scopes. Your user needs these scopes assigned. Learn more.
- Scopes:
ips:read_write
- Scopes:
CLI
CLI example - Ephemeral IP
linode-cli networking ip-add \
--type ipv4 \
--public false \
--linode_id 123CLI example - Reserved IP
linode-cli networking ip-add \
--type ipv4 \
--public true \
--linode_id 123 \
--reserved true \
--region us-east