- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Instance Management
- Service Management
- Creating API
- API Creation Overview
- Creating APIs Connecting to the Public URL/IP Backend
- Creating APIs Connecting to the VPC Resource Backend
- Creating APIs Connecting to the SCF Backend
- Creating API for Interconnecting Backend with COS
- Creating APIs Connecting to the Mock Backend
- Creating APIs Connecting to the TSF Backend
- Importing APIs
- API Management
- Calling API
- Release and Access
- Custom Domain Name and Certificate
- Usage Plan
- Backend Upstream
- Verification and Security
- Log Statistics
- Access Monitoring
- API Doc Generator
- Application Management
- Permission Management
- Precautions
- Private IP Ranges and Public VIPs of API Gateway Regions
- Plugin Usage
- Best Practices
- Making Serverless Service Available quickly through API Gateway
- Integrating WAF to API Gateway for Security Protection
- Accessing Resources in IDC via API Gateway Dedicated Instance
- Quick Access to TEM Application via API Gateway
- Integrating ECDN to API Gateway for Acceleration
- API Gateway Providing the Access Capability for TKE
- Migrating from Region A to Region B
- Development Guide
- API Documentation
- Legacy Features
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Instance Management
- Service Management
- Creating API
- API Creation Overview
- Creating APIs Connecting to the Public URL/IP Backend
- Creating APIs Connecting to the VPC Resource Backend
- Creating APIs Connecting to the SCF Backend
- Creating API for Interconnecting Backend with COS
- Creating APIs Connecting to the Mock Backend
- Creating APIs Connecting to the TSF Backend
- Importing APIs
- API Management
- Calling API
- Release and Access
- Custom Domain Name and Certificate
- Usage Plan
- Backend Upstream
- Verification and Security
- Log Statistics
- Access Monitoring
- API Doc Generator
- Application Management
- Permission Management
- Precautions
- Private IP Ranges and Public VIPs of API Gateway Regions
- Plugin Usage
- Best Practices
- Making Serverless Service Available quickly through API Gateway
- Integrating WAF to API Gateway for Security Protection
- Accessing Resources in IDC via API Gateway Dedicated Instance
- Quick Access to TEM Application via API Gateway
- Integrating ECDN to API Gateway for Acceleration
- API Gateway Providing the Access Capability for TKE
- Migrating from Region A to Region B
- Development Guide
- API Documentation
- Legacy Features
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
Integrating ECDN to API Gateway for Acceleration
Last updated: 2023-12-22 10:03:04
Overview
Tencent Cloud Enterprise Content Delivery Network (ECDN) integrates static edge caching and dynamic origin-pull route optimization. Through Tencent's global nodes and based on more than ten years of technical practice on the QQ platform, ECDN provides one-stop acceleration service with high reliability and low latency.
Connecting the API Gateway with ECDN can help you solve problems such as slow response, high packet loss and unstable service caused by cross-ISP, cross-boarder and cross-network data transfer.
Relevant Products
Directions
1. Log in to the API Gateway console. Create an API Gateway service. A default access address is generated.
2. Configure a custom domain name in the ECDN console.
Enter the custom domain name in the "Add acceleration domain name" field.
Select "Origin server domain name" as the origin server type.
Select "Optimal origin-pull" as the origin-pull policy.
Enter the default access address generated in step 1 (without the protocol and port number) as the origin-pull address.
Select the origin-pull protocol and acceleration region as needed.
Click Save to complete the configuration. A CNAME domain name will be generated in the CDN console after a while.
3. Modify the origin server Host.Select the just configured domain name in the domain name list in ECDN console. Click it to go to the details page.
Change the origin server Host to the default public network access address generated in step 1.
4. Configuring CNAME.
Configure the CNAME domain name for the connected domain name.
5. Initiate a call, and you can see that they are already connected.
Yes
No
Was this page helpful?