All Products
Search
Document Center

Serverless App Engine:Application access and traffic control

Last Updated:Oct 13, 2026

This topic describes the concepts and capabilities that are related to Serverless App Engine (SAE) networks.

FAQs

How can an SAE application access the Internet?

SAE supports the following types of Internet access: outbound access and inbound access, as shown in the following figure. For information about outbound access over the Internet, see the methods that are described in this section. For information about inbound access over the Internet, see How can an SAE application be accessed over the Internet?dg_sae_access_public_network

SAE allows you to enable Internet access for an application by using one of the following methods: Configure a NAT gateway for an SAE application to enable Internet access and Enable Internet access for SAE instances based on EIPs.

How can an SAE application be accessed over the Internet?

SAE supports the following types of Internet access: outbound access and inbound access, as shown in the following figure. For information about inbound access over the Internet, see the methods that are described in this section. For information about outbound access over the Internet, see How can an SAE application access the Internet?dg_sae_access_public_network

We recommend that you enable Internet access for applications by configuring gateway routing based on ALB and CLB instances. If the gateway routing method cannot meet your requirements, see Configure application access based on CLB instances or Enable Internet access for SAE instances based on EIPs.

How do I bind a public domain name to an SAE application?

SAE does not provide features that are related to domain names. To bind a domain name to an SAE application, perform the following operations: Configure an ALB instance or CLB instance for the SAE application, obtain the related public IP address or domain name, and then bind the IP address or domain name to the SAE application in the Alibaba Cloud DNS console.

What do I do if an SAE application cannot access an ECS instance?

To troubleshoot the issue, perform the following steps:

  1. Check whether the SAE application and the ECS instance reside in the same VPC, and check whether the related ports are configured in the corresponding security group.

  2. Run the ping <Service address> command or telnet <Service address> command in a container to check the connectivity. If the preceding commands are not available, Copy a command to install O&M components.

For information about how to access a public ECS endpoint, see How can an SAE application access the Internet?

What do I do if an SAE application cannot access an ApsaraDB RDS instance or ApsaraDB for Redis instance?

Check whether the endpoint of the ApsaraDB RDS instance or ApsaraDB for Redis instance is a public endpoint or an internal endpoint. The SAE application accesses the ApsaraDB RDS instance or ApsaraDB for Redis instance by using the corresponding endpoint. The network quality and latency of an internal endpoint are better than that of a public endpoint. If the SAE application resides in the same VPC as the ApsaraDB RDS instance or ApsaraDB for Redis instance, we recommend that you use the internal endpoint of the ApsaraDB RDS instance or ApsaraDB for Redis instance. Network fees vary based on the types of resources that you create. For more information, see Billing. If the SAE application resides in a different VPC as the ApsaraDB RDS instance or ApsaraDB for Redis instance, we recommend that you use a What is Cloud Enterprise Network? instance to connect the VPCs, and then use the internal endpoint of the ApsaraDB RDS instance or ApsaraDB for Redis instance. Then, perform the following steps to troubleshoot the issue:

  1. Check whether a whitelist is configured.

    Note

    To enable internal access, you must add the CIDR blocks of the VPC and vSwitch of the SAE application to a whitelist. To enable Internet access, you must add the EIP of the SAE application to the whitelist.

  2. Run the ping <Service address> or telnet <Service address> command in a container. If the preceding commands are not available, Copy a command to install O&M components.

  3. If the output of the ping or telnet command indicates normal, you can install a MySQL client or Redis client to test whether the ApsaraDB RDS instance or ApsaraDB for Redis instance can be connected. For more information, see Connect to an RDS MySQL instance by CLI or client or Procedure. If the instance can be connected, the SAE network environment is normal. In this case, you must check the configurations of your program.