Skip to content

Quotas and limits

The service quotas on instances, vCPUs, volumes, snapshots, network interfaces, IPv4 addresses, VPCs, subnets and firewalls, and Compute's fixed limits.

Updated View as Markdown

Service quotas

Compute, Block Storage, Network and Firewall have service quotas: instances, shared and dedicated vCPUs, SSH keys, launches per minute, console sessions, volume storage, provisioned IOPS and throughput, snapshots, network interfaces, IPv4 addresses and their allocations, VPCs, subnets, firewalls, rules and firewall writes. Their defaults are on Default quotas, and your organization’s current values are in the console’s Service quotas page, where you can request an increase.

A request over a quota is 409 quota_exceeded (429 quota_exceeded for console sessions), with a quota object naming it, its limit and what’s used. A launch over any quota, its volumes’, interfaces’ and addresses’ included, is refused and keeps nothing.

Fixed limits

These aren’t quotas and can’t be raised.

Limit Value
SSH keys per launch 10
User data 16 KiB
Volumes and network interfaces per instance The instance type’s limits
Firewalls per network interface 5
Network interfaces per firewall 1,000
Firewalls an interface’s rules can reference as peers 8
Rules per request 1–50 to add, 0–200 to replace
IPv4 addresses per network interface 1 (none on a private interface)
Network interfaces per VPC 1,000
Subnets per VPC 256
Private interfaces per instance, per subnet 1
Secondary private addresses per network interface 2, IPv4 and IPv6 together
Delegated prefixes per network interface 16 IPv4 (/28) and 2 IPv6 (/80)
Private addresses per VPC 4,000: IPv4 and IPv6, primary and secondary, counting addresses still being withdrawn
Member prefixes per VPC 5,000, delegated prefixes included
Private interface MTU 8900
Tags per resource 50
Console sessions Idle for 30 minutes, or 8 hours long, ends the session
Metadata service 100 requests per second per instance
Navigation

Type to search…

↑↓ navigate↵ selectEsc close