All Products
Search
Document Center

Platform For AI:Overview of invocation methods

Last Updated:Nov 04, 2025

EAS offers five invocation methods. This guide helps you choose the one that best fits your requirements.

Architecture overview

Important

After you configure a virtual private cloud (VPC), vSwitch, and security group for an EAS service, the following conditions apply:

  • Accessing EAS through a shared gateway or a dedicated gateway is not restricted by security group rules. For a dedicated gateway, however, you can configure access rules with a whitelist.

  • Accessing EAS through NLB, Nacos, or a VPC direct connection, and all outbound traffic from EAS, are restricted by security group rules.

image

Feature comparison

Invocation method

Features

Scenarios

Shared gateway

  • Free and available out-of-the-box.

  • Lacks support for custom access policies and provides limited isolation and elasticity.

Ideal for services that handle low traffic and do not require high performance or strong isolation.

Dedicated gateway

  • A paid service that requires creation.

  • Supports custom access policies, cross-VPC and cross-cloud access, and custom domain names.

Recommended for services that require high security, stability, and performance, and can handle high traffic.

VPC direct connection

  • Provides direct access via IP address by bypassing the gateway, which improves performance and reduces latency.

  • Offers limited load balancing capabilities.

Ideal for high-traffic services.

Server Load Balancer (NLB)

  • Requires a pre-configured NLB instance.

  • Allows you to use all of NLB's access control capabilities.

Best for services with extremely high traffic that require robust load balancing.

Service discovery (Nacos)

  • Requires a pre-configured Nacos instance.

  • Allows you to use all of Nacos's access control capabilities.

Ideal for environments that use Nacos for service registration and discovery.