Migrate API groups between instances
Move an API group from one API Gateway instance to another to meet higher throughput, SLA, or network isolation requirements.
Instance types
Serverless instance (VPC): Tenants share the same outbound IP address and bandwidth. Suited for testing and small-scale production workloads.
Dedicated instance (VPC): Provides a higher service level agreement (SLA) with isolated resources — including dedicated inbound public IP addresses, virtual private cloud (VPC) IP addresses, outbound Internet bandwidth, and isolated server clusters. Purchase a specification with the requests per second (RPS) limit your workload requires.
Before you begin
Review the following before migrating. If you have changed the RPS for an API group, submit a ticket before proceeding.
Migrate from a serverless instance to a dedicated instance
After migration, the destination dedicated instance's maximum RPS and HTTPS security policy apply to the API group.
The outbound IP address of the instance may change. Check the updated address on the Instances page and add it to the allowlist of IP addresses permitted to reach your backend service.
If your API group uses any of the following features, enable them on the destination instance before migrating: second-level domain name for VPC access, internal domain name for API Gateway API calls, inbound IPv6 traffic, and outbound IPv6 traffic.
If the destination is a VPC integration instance, confirm that the backend service's IP address or CIDR block is permitted by the security group of the Elastic Network Interface (ENI) bound to that instance.
Migrate from a dedicated instance to another dedicated instance
After migration, the destination dedicated instance's maximum RPS and HTTPS security policy apply to the API group.
The outbound IP address of the instance may change. Check the updated address on the Instances page and add it to the allowlist of IP addresses permitted to reach your backend service.
If your API group uses any of the following features, enable them on the destination instance before migrating: second-level domain name for VPC access, internal domain name for API Gateway API calls, inbound IPv6 traffic, and outbound IPv6 traffic.
If the destination is a VPC integration instance, confirm that the backend service's IP address or CIDR block is permitted by the security group of the ENI bound to that instance.
Migrate an API group
Log on to the API Gateway console. In the top navigation bar, select a region.
In the left-side navigation pane, choose Manage APIs > API Groups. Click the API group you want to migrate.
On the Group Details page, click Modify Instance for API Group Deployment.
In the dialog box, select a destination instance from the Destination Instance drop-down list. Read the precautions, select I have read the preceding statement and know the potential risks associated with the migration, then click Migration. The change takes effect within 1 to 10 minutes, depending on the Domain Name System (DNS) cache.
If your dedicated instance's specification no longer meets your requirements, you can upgrade it to a higher specification. For more information, see Change an instance specification.
Due to DNS caching, some requests may still reach the previous instance after migration completes. Verify that all traffic has switched to the new instance before releasing the old one.