All Products
Search
Document Center

Instance types

Last Updated: Aug 18, 2021

1. API Gateway instance types

An API Gateway instance is a group of resources used to access and process your APIs. The resources include public IP addresses, internal IP addresses, outbound public IP addresses, Server Load Balancer (SLB) instances, servers, and storage resources. API groups can only run on valid instances. API Gateway provides the following instance types: shared instance (VPC) and dedicated instance (VPC).

1.1. Instance type description

  • Shared instance (VPC): If you select a shared instance, you are billed based on the number of API calls and traffic generated on the Internet. However, resources such as the server resource pool, IP addresses, and bandwidth are shared by a group of users in a region. Instances deployed in virtual private clouds (VPCs) are newly introduced for technical reconstruction. Such instances support the entire plug-in system, which covers JSON Web Token (JWT) authentication, throttling, IP address-based access control, backend signature, cross-origin resource sharing (CORS), caching, and routing. They also support access over the Internet or a VPC, and backend service addresses in a VPC and on the Internet.

  • Dedicated instance (VPC): The technical specifications of dedicated instances (VPC) and shared instances (VPC) are the same. To obtain a higher service-level agreement (SLA) guarantee, you can purchase a higher specification for requests per second (RPS) to use dedicated resources. The resources include inbound public IP addresses, inbound IP addresses in VPCs, outbound public bandwidth, and isolated server clusters. For more information about the specifications and pricing of dedicated instances, see Pricing of dedicated instances.

1.2. Technical specifications and limits

Item

Shared instance (VPC)

Dedicated instance (VPC)

Scenarios and suggestions

Shared instances (VPC) are suitable for R&D and test environments because low latency and high performance may not be achieved for backend services.

Dedicated instances (VPC) are suitable for production environments.

Cloud resources

All the cloud resources of a shared instance, including Elastic Compute Service (ECS), SLB, and ApsaraDB for Redis instances, are shared by all users of this shared instance.

All the cloud resources of a dedicated instance are exclusive to a single user.

SLA

99.9%.

99.95% to 99.99%.

Billable items

Number of API calls and network traffic.

Instance specifications and network traffic. The fees of instance specifications vary based on the billing method (pay-as-you-go or subscription).

Inbound public IP address

The IP address is not fixed and is shared by multiple tenants.

The IP address is fixed and exclusive.

Inbound IP address in a VPC

The IP address is not fixed and is shared by multiple tenants.

Access from all VPCs in the same region is supported.

The IP address is fixed and exclusive. Only the access from a specific VPC is supported.

To support access from multiple VPCs in the same region, submit a ticket.

Outbound public bandwidth

The outbound IP address and bandwidth are shared by multiple tenants. The IP address is not fixed.

The outbound IP address and bandwidth are exclusive. The IP address is fixed.

Inbound or outbound IPv6 traffic

Not supported.

Supported.

Maximum timeout at the backend

30s.

90s.

Call by API Gateway

Not supported.

Supported.

Limits on the request body size

8 MB.

32 MB.

Circuit breaker plug-in

The plug-in is configured by default and cannot be customized.

The plug-in can be customized.

Caching

30 MB per user.

Depends on the instance type.

For more information, see Dedicated instances.

Plug-in metadata and quantity

The metadata of a single plug-in cannot exceed 16 KB in size.

Each user can create a maximum of 1,000 plug-ins in each region.

The metadata of a single plug-in cannot exceed 50 KB in size.

Each user can create a maximum of 10,000 plug-ins in each region.

Limits on a backend routing plug-in

A maximum of 16 parameters can be specified in each backend routing plug-in.

A maximum of 16 rules can be configured in each backend routing plug-in.

A maximum of 160 parameters can be specified in each backend routing plug-in.

A maximum of 160 rules can be configured in each backend routing plug-in.

Limits on an IP address-based access control plug-in

A maximum of 16 parameters can be specified in each IP address-based access control plug-in.

A maximum of 16 rules can be configured in each IP address-based access control plug-in.

A maximum of 160 parameters can be specified in each IP address-based access control plug-in.

A maximum of 160 rules can be configured in each IP address-based access control plug-in.

Uploading of trace logs to the Alibaba Cloud Tracing Analysis console

Not supported.

Supported.

Logging of HTTP requests and responses

Not supported.

Supported.

Default domain name to support access over HTTPS

Not supported.

Supported.

Maximum number of inbound RPS

1000 for each user in the same region.

500 for each API group.

2500 to 60000.

For more information, see Dedicated instances.

Maximum number of inbound connections

500 for each user in the same region.

50000 to 1000000.

Maximum number of new connections per second (CPS)

500.

5000 to 20000.

Maximum size of an outbound connection pool

120.

1200 to 28800.

Maximum inbound public bandwidth (Mbit/s)

5120. The bandwidth is shared by multiple tenants, and no specific limit is imposed on each user.

5120.

Maximum outbound public bandwidth (Mbit/s)

The bandwidth is shared by multiple tenants. The maximum outbound public bandwidth is the sum of outbound IP addresses of shared instances. One IP address equals 200 Mbit/s bandwidth.

100 to 600.

2. Instances supported in each region

Region ID

Region name

Shared instance (VPC)

Dedicated instance (VPC)

cn-qingdao

China (Qingdao)

Supported

Supported

cn-beijing

China (Beijing)

Supported

Supported

cn-zhangjiakou

China (Zhangjiakou)

Supported

Supported

cn-huhehaote

China (Hohhot)

Supported

Supported

cn-hangzhou

China (Hangzhou)

Supported

Supported

cn-shanghai

China (Shanghai)

Supported

Supported

cn-shenzhen

China (Shenzhen)

Supported

Supported

cn-heyuan

China (Heyuan)

Supported

Supported

cn-hongkong

China (Hong Kong)

Supported

Supported

ap-northeast-1

Japan (Tokyo)

Supported

Supported

ap-southeast-1

Singapore (Singapore)

Supported

Supported

ap-southeast-2

Australia (Sydney)

Supported

Supported

ap-southeast-3

Malaysia (Kuala Lumpur)

Supported

Supported

ap-southeast-5

Indonesia (Jakarta)

Supported

Supported

ap-south-1

India (Mumbai)

Supported

Supported

us-east-1

US (Virginia)

Supported

Supported

us-west-1

US (Silicon Valley)

Supported

Supported

eu-west-1

UK (London)

Supported

Supported

me-east-1

UAE (Dubai)

Supported

Supported

eu-central-1

Germany (Frankfurt)

Supported

Supported