Docs

Torch Object Storage

Event notification

Delivering event notifications to veFaaS

This topic explains how to configure event notification rules.

Prerequisites

You have created a Volcano Engine Function as a Service (veFaaS) function based on the template vefaas-golang-tos-trigger, and have published it. For instructions, see Creating a function and Publishing a function.

warning

Asynchronous functions are not supported for TOS events. Do not enable "Asynchronous task" when creating functions for event notifications.

Notes

A single bucket can have a maximum of 30 event notification rules.

An object cannot match multiple rules that include the same event type. This means that, within the same bucket, event types and prefixes/suffixes across different rules cannot overlap.

The total JSON description size of all event notification rules in a bucket cannot exceed 20 KB.

Steps

In the left navigation pane, click Buckets. In the Buckets list, click the bucket you want to configure.

In the left navigation pane, select Basic configurations > Event notification. On the Event notification page, click Create rule.

On the Create event notification page, set the following parameters:

Parameter			Description
Basic configurations	Event name	Specify the name of the event notification rule. Naming rules: Event names must be unique within the bucket. Length must not exceed 255 characters.
		Prefix	Enter the prefix of the object(s) to be matched. For example, if the prefix is set to test/, then objects in the test directory will be matched.
		Suffix	Enter the suffix of the object(s) to be matched. For example, if the suffix is set to .png, then all objects in PNG format will be matched. tip If neither a prefix nor a suffix is set, all objects in the bucket will be matched.
Event type	Event type	Select the event(s) to be notified. For a list of types supported by TOS, see Supported event types. warning If the same event type is selected in different rules, the object-matching scopes for this event type must not overlap. This means that a single object cannot trigger multiple rules containing the same event type. For example, if Rule A is created to send a notification for PutObject events on objects with the suffix png, Rule B cannot be configured to trigger for PutObject events on objects with the same suffix png. If there is an overlap, the creation of the rule will fail.
Data target	Target type	Select Function service.
Data target		Function service	Select the function to which notifications will be delivered. To select multiple functions, click Add row. Up to five functions can be set. tip If no function is available, you can create one through the veFaaS console. For instructions, see Creating a function. Version 2 of the event notification APIs is now available. This enhanced version allows you to deliver notifications for a single event type to multiple destinations instead of just one. To avoid errors caused by version incompatibility, we recommend switching to the new version as soon as possible. For more information, see Notice Regarding Updates to the Event Notification APIs.

Click Confirm.

tip

After the event notification rule is created, veFaaS generates a trigger with the same name as the event for the function to which notifications will be delivered. Log in to the veFaaS console, and click the function to view the trigger.

The event notification rule takes effect five minutes after creation.

Other operations

Edit an event notification rule: Click Edit in the Actions column of the rule you want to modify.

Delete an event notification rule: Click Delete in the Actions column of the rule you want to remove, and confirm the deletion by clicking Delete in the box that appears.

Last updated: 2026.07.01 14:48:56