# Elastic IPs and static public addresses

Source: https://docs.quake.ai/docs/network/concepts/elastic-ips
Markdown: https://docs.quake.ai/docs/network/concepts/elastic-ips.md

---

# Elastic IPs and static public addresses

**Elastic IP** (AWS), **reserved IP** (DigitalOcean), **static external IP** (GCP), and **public IP** (Azure) names all describe a stable public address you attach to a workload. On Quake AI that role is a **[floating IP](/docs/network/concepts/floating-ips)** allocated from the provider pool and associated with an instance **port** on a private network.

## On Quake AI

Floating IPs use destination NAT: clients reach the public address; traffic forwards to the instance private IP. You can disassociate and move the address to another instance during maintenance without changing the public side of DNS.

Quotas cap floating IPs per project. Security groups still filter which ports accept traffic after association.

## Provider names

| Provider | Their term | On Quake AI |
|---|---|---|
| AWS | Elastic IP | [Floating IP](/docs/network/concepts/floating-ips) |
| Azure | Public IP address | [Floating IP](/docs/network/concepts/floating-ips) |
| Google Cloud | Static external IP | [Floating IP](/docs/network/concepts/floating-ips) |
| Hetzner | Floating IP | [Floating IP](/docs/network/concepts/floating-ips) |
| DigitalOcean | Reserved IP | [Floating IP](/docs/network/concepts/floating-ips) |

## What to read next

- [Floating IPs](/docs/network/concepts/floating-ips): NAT behavior, quotas, and security groups
- [Allocate a floating IP](/docs/network/how-to/allocate-floating-ips): Console and CLI procedure
- [VPC on Quake AI](/docs/network/concepts/vpc): how public addresses fit private networks