Available in VPC
You can add Object Storage type triggers on the NAVER Cloud Platform console's Cloud Functions > Action > Action details. Object Storage is a NAVER Cloud Platform service that provides file storage space allowing you to store and explore data anytime, anywhere. It can be used to store data that needs secure storage or large volumes, and can also be used for server data backup and recovery using the provided API.
- Additional fees apply when you subscribe to Object Storage. For information on Object Storage and its pricing plans, see Services > Storage> Object Storage in NAVER Cloud Platform portal.
Add trigger
To add an Object Storage type trigger, click and select Object Storage in the trigger type, then configure the trigger's basic information and Object Storage connection information.
Connection information setup
You can configure the connection settings for Object Storage type trigger in Object Storage connection information within the console.

-
Select an Object Storage bucket to check the list of events in that bucket.
-
Select a bucket and an event, then click the add button to complete Object Storage connection information setup. You can add multiple events, and each event occurrence runs the same trigger.
-
You must check and acknowledge the recursive call caution to create the trigger.
CautionIf an action connected to an Object Storage type trigger uses the same bucket as the Object Storage event, usage may increase and excessive charges may occur due to recursive calls.
-
A maximum of 10 triggers can be connected per bucket.
-
Click [Create bucket] to go to the Object Storage console and create a new bucket.
-
Click [Create bucket event] to create a new bucket event. For information on creating bucket events, see Object Storage user guide.

When creating a bucket event in Object Storage on the NAVER Cloud Platform console, select Cloud Functions as the target to connect to an existing trigger or create a new one.
Events forwarded to trigger
When an event created in Object Storage occurs, event information is forwarded to the Object Storage type trigger. The event information can then be used as parameters within the action code connected to the Object Storage type trigger for various applications. The examples of the events forwarded to Object Storage type trigger are as follows:
{
"container_name": "my-bucket", // bucket name
"event_name": "my-event-rule", // event name
"event_type": "ObjectCreated:PUT" // event type
"event_version": "1.0" // event format version
"object_length": "1000", // object size
"object_name": "my-object", // object key
"region": "KR", // Region name
"remote_address": "127.0.0.1", // request IP
"remote_user_sha256": "ef5dd4b34d...", // SHA256 hash hex value of user Access Key
"remote_user_type": "user", // user type
"request_method": "PUT", // request method
"request_type": "REST.PUT.OBJECT", // request type
"timestamp_finish": "1627881611929", // request completion time, Unix time, milliseconds
"timestamp_start": "1627881611914" // request start time, Unix time, milliseconds
}
- If remote_user_type is not user, remote_address and remote_user_sha256 should include null.
- For more information about bucket events, see Object Storage user guide.
If order guarantee is required, implement it in action code using the Timestamp in event information as event occurrence order is not guaranteed.