This page covers the instance-level operations available in Cloud-native API Gateway: viewing instance details, tuning parameters, enabling WAF, configuring auto scaling, and managing services.
View the details of an instance
View your Cloud-native API Gateway instance's basic information, ingress configuration, and security group authorizations in one place. For more information, see View the details of an instance.
Modify instance parameter settings
Tune your gateway instance's parameters to improve network performance, reliability, and security. Before making changes, review the meaning and valid range of each parameter, as modifications may temporarily affect active connections and running applications. For more information, see Modify instance parameter settings.
Configure security group rules
A Cloud-native API Gateway instance and its backend services reside in separate security groups. Configure a security group rule to authorize your gateway instance to reach the backend so that inbound traffic flows through correctly. For more information, see Configure security group rules.
Enable WAF
Cloud-native API Gateway integrates natively with Alibaba Cloud WAF 3.0. Unlike traditional Web Application Firewall (WAF) setups, requests go directly to the gateway without routing through a separate WAF layer, improving throughput while maintaining the same level of protection. For more information, see Enable WAF.
Does Cloud-native API Gateway support WAF 2.0?
Yes. To integrate Cloud-native API Gateway with WAF 2.0, add the IP address of the Server Load Balancer (SLB) instance associated with your gateway instance as an origin IP address in WAF. For more information, see Tutorial.
Enable auto scaling for gateways
Cloud-native API Gateway automatically scales resources and container instances in response to traffic changes, keeping your applications available during peak loads while reducing costs during off-peak periods. For more information, see Enable auto scaling for gateways.
Services
Add existing services to Cloud-native API Gateway as routing targets, or create new ones directly in the gateway. For each service, you can:
Configure tag-based routing policies for high-availability deployments such as canary releases
Set traffic rules to control backend encryption types and load balancing methods
Enable active health checks that automatically remove unhealthy instances and restore them when they recover
Cloud-native API Gateway supports the following service sources: Container Service for Kubernetes (ACK) clusters, Microservices Engine (MSE) Nacos instances, fixed endpoints, Domain Name System (DNS) domain names, and Function Compute. For more information, see Services.
Service sources
A service source defines a backend registry that Cloud-native API Gateway queries to discover service instances, such as an MSE Nacos registry or an ACK cluster. You can create, modify, and delete service sources to control which registries the gateway can access. For more information, see Add a service source.