Help Center> FunctionGraph> User Guide (Kuala Lumpur Region)> Creating Triggers> Using an APIG (Dedicated) Trigger
Updated on 2023-07-06 GMT+08:00
View PDF

Using an APIG (Dedicated) Trigger

Prerequisites

You have created an API group, for example, APIGroup_test. For details, see Creating an API Group.

Creating an APIG Trigger

  1. Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
  2. On the Function List page, click Create Function in the upper right corner.
  3. Set the following parameters:

    • Function Name: Enter a function name, for example, apig.
    • Agency: Select Use no agency.
    • Enterprise Project: Select default.
    • Runtime: Select Python 2.7.

  4. Click Create.
  5. On the Code tab page, copy the following code to the code window and click Deploy.

    # -*- coding:utf-8 -*-
import json
def handler (event, context):
    body = "<html><title>Functiongraph Demo</title><body><p>Hello, FunctionGraph!</p></body></html>"
    print(body)
    return {
        "statusCode":200,
        "body":body,
        "headers": {
            "Content-Type": "text/html",
        },        
        "isBase64Encoded": False
    }

  6. Choose Configuration > Triggers and click Create Trigger.

    Figure 1 Creating a trigger

  7. Configure the trigger information.

    Table 1 Trigger information

    Parameter

    Description

    Trigger Type

    Select API Gateway (Dedicated Gateway).

    Instance

    Select an instance. If no instance is available, click Create Instance.

    API Name

    Enter an API name, for example, API_apig.

    API Group

    An API group is a collection of APIs. You can manage APIs by API group.

    Select APIGroup_test.

    Environment

    An API can be called in different environments, such as production, test, and development environments. API Gateway supports environment management, which allows you to define different request paths for an API in different environments.

    To ensure that the API can be called, select RELEASE.

    Security Authentication

    There are three authentication modes:

    • App: AppKey and AppSecret authentication. This mode is of high security and is recommended.
    • IAM: IAM authentication. This mode grants access permissions to IAM users only and is of medium security.
    • None: No authentication. This mode grants access permissions to all users.

    Select None.

    Protocol

    There are two types of protocols:

    • HTTP
    • HTTPS

    Select HTTPS.

    Timeout (ms)

    Enter 5000.

  8. Click OK.

    Figure 2 Creating a trigger
    1. URL indicates the calling address of the APIG trigger.
    2. After the APIG trigger is created, an API named API_apig is generated on the API Gateway console. You can click the API name in the trigger list to go to the API Gateway console.

Invoking the Function

  1. Enter the URL of the APIG trigger in the address bar of a browser, and press Enter.
  2. View the execution result, as shown in Figure 3.

    Figure 3 Returned result
    1. The input for API Gateway invocation comes from an event template provided by the function. For details, see Table 2.
    2. The function response for API Gateway invocation is encapsulated and must contain body(String), statusCode(int), headers(Map), and isBase64Encoded(boolean).

Viewing the Execution Result

  1. Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
  2. Click a function to go to the function details page.
  3. Choose Monitoring > Logs to query function running logs.
Parent topic: Creating Triggers