By default, a newly created cloud function has only the public network access permission. That is, when the cloud function is being executed, it can only access public network resources such as Tencent Cloud.
SCF supports the following network configurations:
Configuration Item | Description |
---|---|
Only public network access is enabled. | - |
Public network access with a fixed public outbound IP is enabled. | The cloud function can access public network resources using a fixed IP address. |
Only private network access is enabled. | The cloud function can access resources configured with the private network, such as databases and Redis. |
Both public and private network accesses are enabled. | The cloud function can access public network resources and resources configured with the private network, such as databases and Redis. |
Private network access and public network access with a fixed public outbound IP are enabled. | The cloud function can access public network resources using a fixed IP address and access resources configured with the private network, such as databases and Redis. |
Note:For more information about how the cloud function obtains the fixed public outbound IP, please see Fixed Public Outbound IP.
Currently, a maximum of 60,000 connections can access the same ip:port concurrently. For non-persistent connections, since the release of intermediate devices takes time, the number of supported concurrent connections is smaller.
If multiple functions (or multiple requests of a function) need to access the same ip:port concurrently, you should pay attention to this limit. You can take the following measures to avoid using up the connections and making code errors.
If the VPC is connected to a private network, the bandwidth for a single VPC is limited to 100 MB. The bandwidth is shared by the functions as well as the concurrent instances of these functions configured with the same VPC. To increase the private network bandwidth, please submit a ticket.
Was this page helpful?