Skip to content
Product
Networking
EIP
Service Boundaries
Limits and Quotas

Limits and Quotas

Limits

  • Elastic IP will natively work only for incoming traffic. Outgoing traffic will still use the native instance’s IP address as a source. This behavior can be partially circumvented manually with manual Elastic IPs.
  • Instances associated with a managed Elastic IP will see incoming Elastic IP traffic destined to their primary interface IP address.
  • With managed Elastic IPs, it is currently not possible to retrieve the health status of an instance: while the system will not direct traffic to a unhealthy instance, there is no information about which instance is in an unhealthy state.
  • HTTP health checks do not follow redirects.
  • Elastic IPv6 prefixes have the same limitations as Elastic IPs.
  • For managed Elastic IPv6 prefixes, only the first-plus-one IPv6 address of that prefix is transparently forwarded to the associated instances.

Quotas

Elastic IPs are initially limited to 5 per organization.

UsageQuota
Elastic IP adresses count5

Availability

EIP is available in all zones.

Last updated on