- 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
Making Serverless Service Available quickly through API Gateway
最終更新日:2023-12-22 10:02:23
Overview
Serverless is a popular architecture in recent years. Through the Serverless function computing platform, you can focus on the core logic and run your code without purchasing and managing servers. In the Serverless mode, using the API Gateway can make the service available to external users, and realize advanced features such as security protection, traffic throttling, log monitoring, releasing in the cloud market, and automatic generation of SDK and documents.
Tencent Cloud API Gateway is highly integrated with Tencent Cloud SCF. This document describes how to build a website quickly by using the API Gateway as the entry to configure dynamic APIs through SCF and store static resources through COS.
With this method, you can use the API Gateway to make the Serverless service available quickly in the cloud.
Prerequisites
Before building a website, you need to go to the API Gateway official repository to download the website source code, which contains a skeleton HTML file and static resources such as pictures, CSS files and JS files.
The directory structure of the downloaded file is as follows:
├── client // Root directory of the project│ ├── static // Static resource│ │ ├── background.jpg // Underground picture of the website│ │ ├── favicon.ico // Website icon│ │ ├── index.js // Script file│ │ ├── style.css // Style file│ ├── index.html // Website homepage
Directions
Step 1. Create a COS bucket to store static resources
1. Log in to the COS console. Create a bucket based on the following figure. For more information, see Creating Buckets.
2. Upload the website source code in the bucket. The directory structure must be consistent with the original file. For more information, see Uploading Objects.
Step 2. Create a SCF
1. Log in to the SCF console. Create a SCF using the "hello world" template. For more information, see Create and Update a Function.
2. Modify the SCF code and return simple JSON data.
The SCF code used is as follows:
'use strict';exports.main_handler = async(event, context, callback) => {return {data: 'hello world' // hello world can be replaced with any content}};
Step 3. Create an API Gateway service
1. Log in to the API Gateway console. Create an API Gateway service based on the following figure. For more information, see Creating Services.
2. Click the name of the service in the service list.
3. Click Manage API to go to the API management page. In the next step, you need to create three APIs on this page, with each API points to the corresponding backend resource.
Step 4. Configure three APIs
1. Click Create to create the first API. It is used to obtain the HTML page of the website. The frontend path is configured as "/". For more information, see API Creation Overview.
The "index.html" that points to the COS bucket is configured for the backend.
2. Click Create again to create the second API. It is used to obtain static resources. The frontend path is configured as "^~/static".
The "/static" path that points to the COS bucket is configured for the backend.
3. Click Create again to create the third API. It is used to obtain dynamic data. The frontend path is configured as "/fetchData".
Enter the corresponding SCF name in the backend configuration.
Step 5. Release the service and access the website
1. On the Service information tab of the service details page, click Release in the upper-right corner to release the service to the "Release" environment.
2. On the Service information tab of the service details page, view the "public network access address". Click the "Copy" icon to copy the address.
3. Paste the "public network access address" in the address bar of a browser. Press "Enter" to access the deployed website.
4. Click Obtain data to initiate a XHR call. The website will return the pre-defined JSON data string through the SCF.
Notes
In addition to access the website you build through the default domain name provided by the API Gateway, you can also bind an custom domain name to the service. After binding, you can access the website through the custom domain name. For more information, see Configuring a Custom Domain Name.
はい
いいえ
この記事はお役に立ちましたか？