- 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
Creating Cloud Native Gateway
Last updated: 2022-07-11 11:05:53
This document is currently invalid. Please refer to the documentation page of the product.
Overview
Cloud Native Gateway is an API gateway hosting product incubated by Tencent Cloud that is 100% compatible with the open source Kong gateway. It is currently in beta test.
This document describes how to create a Cloud Native Gateway instance in the console.
Directions
- Log in to the API Gateway console and click Cloud Native Gateway on the left sidebar.
- Click Create to enter the Cloud Native Gateway instance creation page.
| Parameter | Required | Description |
|---|---|---|
| Region | Yes | Select the region of the Cloud Native Gateway instance. |
| Availability Zone | Yes | Select the AZ of the Cloud Native Gateway instance in the selected region. Unavailable AZs have insufficient resources. |
| Gateway Name | Yes | Enter the name of the Cloud Native Gateway instance. |
| Gateway Type | Yes | Currently, only Kong gateway is supported. |
| Gateway Version | Yes | Open-source version of the selected gateway type. |
| Cluster Node Specifications | Yes | Select the specification of each node. A Cloud Native Gateway cluster consists of multiple nodes. |
| Number of Cluster Nodes | Yes | Select the number of cluster nodes. A Cloud Native Gateway cluster consists of multiple nodes. |
| Network | Yes | Select the VPC where the Cloud Native Gateway instance is deployed. |
| Subnet | Yes | Select the subnet where the Cloud Native Gateway instance is deployed in the selected VPC. |
| Description | No | Enter the description of the current Cloud Native Gateway instance. |
- Click Save and wait for the instance to be created.
Notes
- To create a Cloud Native Gateway instance, your account must be granted with the
ApiGateWay_QCSRolerole, and the role must be associated with theQcloudAccessForApiGateWayRoleInCloudNativeAPIGatewaypolicy. If your account doesn't have such role and policy, grant them in the pop-up authorization window during creation. - The log feature of Cloud Native Gateway relies on CLS. Make sure that you have activated CLS in the CLS console before creating a Cloud Native Gateway instance.
- Currently, Cloud Native Gateway is in beta and free of charge.
Yes
No
Was this page helpful?