This topic describes solutions to the problem that no available vSwitches can be found when you create a gateway.
Cause
When you create a gateway, you must specify a virtual private cloud (VPC) and a vSwitch. In some cases, no vSwitch is available in the selected VPC. For example, no vSwitch exists in the VPC or existing vSwitches in the VPC are dimmed and cannot be selected. The vSwitch availability issue occurs because no sufficient resources are available for creating a gateway in zones of some regions. This issue is common in alphabetically earlier zones such as zones A, B, C, and D in the China (Beijing), China (Shanghai), and China (Hangzhou) regions.
Solutions
Create a vSwitch in alphabetically later zones, such as Zone G or Zone H, and select the created vSwitch to proceed with gateway creation. When you create a gateway, you do not have to deploy the gateway in the same zone as the Elastic Compute Service (ECS) instance. However, you must make sure that the gateway and ECS instance reside in the same VPC so that they can communicate.