Alibaba Cloud Function Compute provides a complete console operation interface that simplifies most of your work through the interactive operations. You can see the following subtitles to use resources in the console, create your first service, function, and trigger, and view the Function Compute execution results, bills, and data monitoring results.
- Activate Function Compute
- View AccessKeys
- View service regions
- Create a service, function, and trigger
- Create a function trigger event
- View role authorization
- View execution results
- View data monitoring
- View bills
Go to the Alibaba Cloud Function Compute homepage and click Activate Now. If you have not logged on to the system yet, you are prompted to log on first. After successful logon before the activation page is displayed. Click Activate Now and Management Console to go to the console. If the console page is not displayed, click here.
In the console, click your account in the upper-right corner and select accesskeys from the drop-down menu. Before the AccessKeys page is displayed, you are prompted to choose whether to continue with the AccessKey or use the AccessKey of the primary account or subaccount. Both AccessKeys can be used to normally access Function Compute. You can select one based on your business features.
If you do not have any AccessKey, click “Create Access Key”.
Use your AccessKey if you already have one.
Note: You must enter the mobile phone number of the primary account and obtain the verification code to view the AccessKeySecret.
For more information about the list of currently activated regions and corresponding region codes, see List of regions and codes.
You can create a service in the Function Compute console. In the console, select Function Compute to go to the Function Compute homepage. Then, select a region and click Create Service in the upper-right corner.
- After a service is successfully created, you can click Advanced Settings to configure log and role authorization.
- You can create unlimited number of services and a maximum of 50 functions for each service currently. For more information about the system restrictions, see Restrictions.
You can create functions under a service. A function is the smallest code execution unit. Each function can have only one entry method but multiple other methods. A maximum of 10 triggers can be set for each function. A navigation page displays the function creation process, which includes three steps: selecting a template, configuring a trigger (optional), and configuring the function. Two templates are available currently. One is the blank function template that allows you to compile your own code. The other template contains a sample code, where you can compile your own business function using the sample code.
Parameters with the red asterisk (*) are required, such as the function name, running environment, and code upload method.
- The function code entry varies with the language. For more information, click here.
- You can set the entry function, memory size, and time-out for the function.
- You can compile the code of a function online. Currently, you can compile codes online using Node.js or Python. If you use other languages, you can only upload codes through OSS or locally. You can upload a maximum of 5 MB codes locally. To upload codes greater than 5 MB, use the Command line tool or store the codes to OSS for execution.
You can create a trigger on the navigation page when creating a function or after creating the function. The configuration varies with the trigger type. The following uses the OSS trigger as an example. Parameters with the asterisk (*) are required.
- When using the trigger for the first time, click OK on the displayed authorization page to authorize OSS to call Function Compute.
- If you have already configured a role, select it.
- The trigger events are stored in a Bucket. Therefore, you must first create a Bucket in the region of Function Compute in OSS.
- For trigger event execution, we recommend that you set the file prefix or suffix to prevent Function Compute from random execution.
A function trigger event is a tool used to simulate your actual request for function debugging. After you put a request string into an event source, the system uses this request string to run the function.
Note: The trigger event string is stored in the local browser cache. You must enter the string again if you clear the cached data or use a new browser.
Function Compute supports two role authorization methods:
- You can configure role authorization in Advanced Settings of the service to authorize Function Compute to access certain resources. Generally, Function Compute can be authorized to access Log Service, OSS, and Table Store. Currently, only the Read-Only permission is granted. To grant more permissions, configure role authorization in RAM.
- You can also configure role authorization in Advanced Settings when creating the trigger to authorize the trigger to trigger execution of Function Compute. Generally, the trigger is authorized, and each trigger needs to be authorized only once.
After a function is executed, the execution result and abstract of the execution process are displayed in the console. For example, the execution status, execution duration, actual billing time, configured memory size, actual used memory size, and other information are displayed. The execution log on the right displays the debugging information during the execution process.
If Log Service is disabled, the console displays only the latest 4 KB running logs. To view more logs, enable Log Service in Advanced Settings of the service.
You can click Real-time Service Monitoring in the upper-right corner of the Function Compute console to view the function execution status in a period.
After logging on to CloudMonitor, you can view the execution status of each service in detail, such as the average latency and total number of calls, which are measured by service.
Select Billing Center > Consumption Record > Consumption Details > Function Compute. The billing items of Function Compute mainly include the resource usage, number of requests, and Internet outbound traffic. For more information about the billing information, see Product pricing. The bill is calculated by hour, which is one hour delayed. For example, the bill of data consumed from 01:00 to 02:00 is output at 04:00.