If you have purchased resources of Function Compute in the China (Hangzhou), China (Shanghai), China (Beijing), or China (Shenzhen) region, and you need to use the VPC feature of Function Compute, you can submit an application to use this feature as prompted in the Function Compute console. After the application is submitted, Function Compute migrates the VPC to allow access to resources. This topic describes how to troubleshoot possible problems during migration.

Note You can view the prompt to activate the VPC feature on the Overview page in the Function Compute console.

VPC migration may affect your functions. Make sure that your business scenarios are suitable for migrations that you have prepared solutions to ensure compatibility. After migration, your service performs normally again. For more information about VPC resources, see Configure functions to access VPC resources.

  • During migration, if the 503 error occurs within seconds after you call the following operations, try again later.
  • If your functions are part of the following scenarios, your business may be affected after migration.
    • Some services in the functions are deployed on Alibaba Cloud, and these services are invoked by using internal endpoints instead of the VPC endpoints. After migration, the services cannot be accessed by using the internal endpoints. These services include Tablestore, Key Management Service, and Container Registry.

      Solution:

      Access the services by using the VPC endpoints. If a service does not provide the VPC endpoint, access the service by using its public endpoint.
      Note For more information about the Internet data transfer fees incurred when you use the public endpoint, see Pricing.
    • The functions access the resources of your ECS instance in the classic network by using the internal endpoint of the ECS instance. This may affect normal business.
      Solutions:
      • Solution 1: Migrate the ECS instance from the classic network to a VPC and use the VPC feature of Function Compute to access the resources.
      • Solution 2: Access the ECS instance by using the public endpoint instead of the internal endpoint.
        Note For more information about the incurred Internet data transfer fees, see Pricing.
    • The functions access your ApsaraDB RDS instance in the classic network by using the internal endpoint, which affects normal business.
      Solutions:
      • Solution 1: Migrate the ApsaraDB RDS instance from the classic network to a VPC and use the VPC feature of Function Compute to access the instance. For more information, see Change the network type of an ApsaraDB RDS for MySQL instance.
      • Solution 2: Access the ApsaraDB RDS instance by using the public endpoint instead of the internal endpoint.
        Note For more information about the incurred Internet data transfer fees, see Pricing.

If you have any feedback or questions, contact us.