# EC2 on Quake AI

Source: https://docs.quake.ai/docs/compute/concepts/ec2
Markdown: https://docs.quake.ai/docs/compute/concepts/ec2.md

---

# EC2 on Quake AI

**Amazon EC2** is AWS compute. On Quake AI the equivalent workload runs as Nova **[instances](/docs/compute/concepts/instances)** in a **project**, sized with **flavors**, booted from **images**, and reached over **networks** and **security groups**.

## Mapping EC2 habits

| EC2 | On Quake AI |
|---|---|
| Instance type | [Flavor](/docs/compute/concepts/flavors) |
| AMI | [Image](/docs/compute/concepts/images) |
| Key pair | [Key pair](/docs/compute/concepts/key-pairs) |
| Security group | [Security group](/docs/network/concepts/security-groups) |
| EBS volume | [Volume](/docs/block/concepts/volumes) |
| Elastic IP | [Floating IP](/docs/network/concepts/floating-ips) |
| VPC subnet | [Network](/docs/network/concepts/networks) (subnet CIDR on that network) |
| `RunInstances` | `openstack server create` or Console create flow |

API shapes differ: Nova uses OpenStack auth (Keystone tokens or application credentials), not SigV4. Terraform uses the `openstack` provider instead of `aws`.

## What to read next

- [Coming from AWS](/resources/migration/coming-from-aws): service mapping and capacity planning
- [Migrate from EC2](/docs/compute/migration/migrate-from-ec2): instance and storage cutover
- [Instances](/docs/compute/concepts/instances): canonical compute model on Quake AI