Two trigger creation methods are provided for HTTP-triggered functions: default creation and custom creation, which have different billing logic.
Default Creation
By choosing "Default Creation", the cloud function will automatically create a basic API Gateway service trigger for you. This type of trigger only provides you with a URL access link and is invisible in the API Gateway console. In this scenario, the billing scheme for HTTP-triggered functions is as follows:
Trigger side: Invocation is not billed, and outbound traffic is billed on the function side.
Function side: In addition to the standard billing items, a new outbound response traffic billing item is added.
Note
A basic API Gateway instance will be created in default creation mode. You can upgrade it to the standard edition in the SCF console. After upgrade, you can use all gateway capabilities, which will be billed in the standard API Gateway billing method. The upgrade is irreversible.
Custom creation
Select "Custom Creation". You need to select the trigger type in the function console and bind the created related services. In this scenario, the billing scheme is the same as the existing billing method. The function and trigger are billed according to their respective billing standards. Taking the standard API Gateway trigger as an example, the HTTP-triggered Function billing scheme is as follows:
Trigger side: Costs are calculated according to the product's own billing standards.
Function side: Costs are calculated based on standard billing items (number of calls, resource usage, outbound traffic). Response traffic is not included in the function side calculation.
Trigger Capability Comparison
Features
Default Creation (Basic API Gateway)
Custom Creation (Standard API Gateway)
Default domain name
Supported
Supported
Binding to custom domain name
Manual binding
Management in API Gateway console
Request method configuration
Supported
Supported
Release environment configuration
Supported
Supported
Authentication method configuration
Not supported
Supported
Visibility in API Gateway console
Invisible
Visible
Advanced API Gateway capabilities (such as plugin and dedicated instance)
Not supported
Supported
Billing method
No charges for the number of gateway calls
Billed according to the standard API Gateway billing plan
Type conversion
Can be upgraded to a standard API Gateway, after which all gateway capabilities can be utilized and billed according to the standard API Gateway billing plan.
Irreversible, a standard gateway cannot be reverted back to the basic gateway created by default.
