EC2 on Quake AI
Explanation · Updated Jun 2026
Coming from another cloud?
▸AWS·EC2 Instances, Amazon Machine Images (AMIs), EC2 Key Pairs
EC2 Instances
- Uses EC2 RunInstances API instead of Nova servers.create.
- Requires predefined instance type selection.
- Supports per-second On-Demand billing and Spot/Reserved options.
- Includes hibernation state not standard in OpenStack.
Amazon Machine Images (AMIs)
- Managed via EC2 APIs, not Glance.
- Region-specific with cross-region copy.
- Marketplace AMIs may charge hourly fees.
- Includes block device mapping in AMI.
EC2 Key Pairs
- Public key auto-injected to authorized_keys at boot.
- Up to 5000 per region; AWS stores public key.
- Supports import of external keys (RSA/ED25519).
- No post-launch addition without userdata/SSM.
EC2 on Quake AI
Amazon EC2 is AWS compute. On Quake AI the equivalent workload runs as Nova 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 |
| AMI | Image |
| Key pair | Key pair |
| Security group | Security group |
| EBS volume | Volume |
| Elastic IP | Floating IP |
| VPC subnet | Network (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: service mapping and capacity planning
- Migrate from EC2: instance and storage cutover
- Instances: canonical compute model on Quake AI
Quick answers
- Why does `openstack image save` write a 0-byte file for my boot-from-volume instance?CLI
- Why does `openstack server create` fail with "Only volume-backed servers are allowed for flavors with zero disk"?CLIAPITerraform
- Why does my project still have a 10 GiB Cinder volume after I deleted my instance?CLIAPI
Related content
Pages
Was this page helpful?