This topic describes how to use resources in a virtual private cloud (VPC) as the backend service of an API and perform a connectivity test for a VPC access authorization to ensure the high availability of your API service.
Elastic Compute Service (ECS) instances and Classic Load Balancer (CLB) instances in a VPC can both be used as backend services of APIs. Process:
Use a resource in a VPC as the backend service of an API
Authorize access to and bind your VPC: To create an API by using a resource in a VPC, you must first authorize API Gateway to access the resource. During the authorization, you must specify the resource and port that you want API Gateway to access. This ensures that API Gateway can securely communicate with your service.
Build a high-availability architecture: You must build a high-availability API architecture to ensure system reliability and stability. The topic to which the link directs provides detailed instructions.
FAQ: The topic also provides answers to some commonly asked questions about the configuration. This helps you smoothly complete the configuration.
Test the network connectivity of a VPC access authorization
In this step, you test the network connectivity between your API Gateway instance and the resource to be accessed in your VPC. This test helps identify and resolve API call issues caused by network connectivity in advance during API debugging.