Function Compute:Configure network settings

Usage notes

For a Custom Container function that is created by using a container image of a Container Registry Enterprise Edition instance, you must select a VPC and a vSwitch based on the following rules when you configure VPC access capabilities for the function:

• If the Default Resolution identifier exists in the Visit IP column on the Access Control page of the Container Registry Enterprise Edition instance, you must set the VPC and vSwitch of the function to the VPC and vSwitch that correspond to the default resolved IP address.

• If the Default Resolution identifier does not exist in the Visit IP column on the Access Control page of the Container Registry Enterprise Edition instance, you can use any VPC and vSwitch that are bound to the instance.

Network access modes

The VPC feature reduces the cold start efficiency of Function Compute. We recommend that you do not configure this feature unless necessary. You can authorize RAM users to access resources such as Tablestore.

You can configure network settings based on your business requirements to obtain corresponding network access capabilities of functions:

• Function outbound traffic settings: specify whether to allow a function to access resources over the Internet or in a VPC by configuring the Access to VPC and Access to Internet parameters.

  Table 1. Function outbound traffic

  Network setting	Description
  Allow a function to access resources only over the Internet.	The function can access the Internet and the internal network and cannot access resources in VPCs. Configure the following parameters: Set Access to VPC to No. Set Access to Internet to Yes.
  Allow a function to access only resources in a VPC.	The function can access public and internal network resources by using a VPC. This setting is applicable to scenarios such as PrivateZone, NAT Gateway, and VPC binding. Configure the following parameters: Set Access to VPC to Yes and specify the VPC that can be accessed by the function. Set Access to Internet to No.
  Allow a function to access resources over the Internet and in a VPC.	The function can access public network resources by using the function logic and internal network resources by using a VPC. Configure the following parameters: Set Access to VPC to Yes and specify the VPC that can be accessed by the function. Set Access to Internet to Yes.
  Prohibit a function from accessing resources over the Internet or in a VPC.	The function can access only the internal network resources by using the function logic. Configure the following parameters: Set Access to VPC to No. Set Access to Internet to No.

• Function inbound traffic settings: specify whether to allow invocation requests from the Internet or VPCs. You can use Function Invocation only by Specified VPCs to configure the inbound traffic settings.

  Table 2. Function inbound traffic

  Network setting	Description
  Allow access to a function over the Internet and a specified VPC.	By default, you can invoke a function over the Internet and VPCs. The following item describes the default network configurations: Function Invocation only by Specified VPCs is set to No.
  Allow access to a function only over a specified VPC.	A function can be invoked over a specified VPC but cannot be invoked over the Internet. Configure the following parameters: Set Function Invocation only by Specified VPCs to Yes and specify the VPC over which your function can be invoked.

Zones where Function Compute is supported

If your resources are deployed in a zone that is not supported by Function Compute, you can create a vSwitch in a zone that is supported by Function Compute in your VPC and use the vSwitch ID in the VPC configurations in Function Compute. vSwitches in the same VPC can communicate with each other over private networks. Therefore, Function Compute can use the vSwitch to access VPC resources that are deployed in other zones. For more information, see How can I resolve the "vSwitch is in unsupported zone" error?

Before you start

• Create a function

• (Optional) Create network resources.

  If you have not created resources, select Automatic Configuration. Otherwise, you must create resources as described in the following topics:

  • Create a VPC and vSwitches

  • Create a security group

Configure network settings and roles

1. Log on to the Function Compute console. In the left-side navigation pane, click Functions.

2. In the top navigation bar, select a region. On the Functions page, click the function that you want to manage.

3. On the function details page, click the Configurations tab.

4. In the left-side navigation pane, click Network. On the page that appears, click Modify. In the Network panel, modify the following parameters and click Deploy.

   • Access to VPC: Specify whether to allow the function to access resources in a VPC. Valid values:

     • Yes: The function can access resources in a VPC. If you set the value to Yes, you must also configure the Configuration Mode parameter. Options:

       • (Recommended) Automatic Configuration: Function Compute automatically creates resources such as a VPC, vSwitches, and a security group. After network resources are created, you can modify the network resources based on your business requirements.

         Note

         The names of network resources that are automatically created by Function Compute are prefixed with fc.auto.create.

       • Custom Configuration: You must select resources from the existing network resources. Make sure that resources are created in advance.

         • VPC: Select a VPC ID from the drop-down list.

           Important

           You can create a maximum of 10 vSwitches for the selected VPC.

         • vSwitch: Select at least one vSwitch ID from the drop-down list.

           This parameter defines the subnets that can be accessed by Function Compute. We recommend that you specify two or more vSwitch IDs. This way, your function can run on another subnet if a zone becomes unavailable or IP addresses are insufficient.

         • Security Group: Select a security group ID from the drop-down list.

           This parameter specifies the security group with which Function Compute is associated. This security group defines the inbound and outbound rules of Function Compute in the specified VPC. In the security group that is associated with the VPC, configure a rule to allow access from the security group with which Function Compute is associated. Otherwise, Function Compute cannot access resources that are deployed in the specified VPC.

     • No: The function cannot access resources in a VPC.

   • Static Public IP Address: Specify whether to obtain a static public IP address by using a NAT gateway and elastic IP address (EIP). For more information, see Configure static public IP addresses.

   • Allow Default NIC to Access Internet: Specify whether to allow the function to access the Internet. Valid values:

     • Yes: The function can access the Internet.

     • No: The function cannot access the Internet.

   • Function Invocation only by Specified VPCs: Specify whether to allow invocation requests only from specified VPCs. Valid values:

     • Yes: The function can be invoked only over specified VPCs. Take note of the following items:

       • You can associate a maximum of 20 VPCs with a function.

       • If you allow a function to be invoked only over specified VPCs, function invocation by triggers are not affected.

       • After one or more VPCs are associated with a function, the VPCs are associated with all versions and aliases of the function.

       • If you allow only requests from specified VPCs to invoke the function, requests from the Internet and other VPCs are rejected. For requests from the Internet and other VPCs, StatusCode 403, ErrorCode AccessDenied, and error message Resource access is bound by VPC: VPC ID are reported.

       • VPCs can be associated only with private HTTP endpoints.

     • No: The function can be invoked only over the Internet.

FAQ

• Why am I unable to connect Function Compute to a VPC for debugging?

  If Function Compute fails to connect to a VPC after you set Access to VPC to Yes, the following items list the possible causes:

  • An error occurred on the subnet with which the vSwitch is associated, or IP addresses are insufficient. We recommend that you specify at least two vSwitch IDs. This allows your function to run in another zone if an error occurs in the current zone.

  • The security group is invalid. Configure the security group based on the following rules:

    • In the security group with which the specified VPC is associated, a rule is configured to allow access from the security group with which Function Compute is associated.

    • The outbound traffic of the security group must support Internet Control Message Protocol (ICMP). Function Compute checks the VPC network connectivity based on ICMP.

    For more information about how to configure a security group, see Add a security group rule.

• What do I do if the resources are insufficient when I create network resources?

  When you create VPC resources, the prefix length of the CIDR block is 24 and the number of available IP addresses is 252. If the number of instances is too large, the limit may be exceeded. In this case, you must manually modify the CIDR block of the vSwitch and the security group.

Troubleshooting

Function Compute does not verify permissions to access a VPC if you configure vpcConfig. Instead, permissions are verified when a function is executed. Therefore, new errors may occur when you invoke the function by using the InvokeFunction operation if vpcConfig is configured. The following table describes common errors that may occur when a function in Function Compute accesses a VPC. You can refer to this table to troubleshoot issues.

More information

• If you want a function to access a database that resides in a VPC, we recommend that you add the CIDR block of the vSwitch that you configured to the whitelist. For more information, see Access a database.

• If you want to restrict function access to the Internet, use static IP addresses. For more information, see Configure static public IP addresses.