Object Storage type trigger

Available in Classic

You can create Object Storage type triggers in the NAVER Cloud Platform console's Cloud Functions > Trigger. Object Storage is a service on NAVER Cloud Platform that provides a file storage space so that users can store and browse the data they want anytime, anywhere. It can be utilized to store large-volume data or to store data securely. You can also use the provided APIs to back up and restore server data.

Refer to Running action or trigger and Trigger for how to run and monitor triggers that have been created.

Create triggers

To create an Object Storage type trigger, you should click and select Object Storage as a trigger type, and set up the trigger's basic information and Object Storage connection information.

Set up connection information

Setting up connections for Object Storage type triggers is done in the console's Object Storage connection information.

• Select a bucket from Object Storage to view a list of events that belong to that bucket.
• Select a bucket and event, and then click the Add button to complete settings for Object Storage connection information. One or more events can be added, and each event occurrence will execute the same trigger.
• You must read the precautions on recursive calls and mark it as read in order to be able to create triggers.
  Caution

  Please note that if the same bucket is used by an action connected to an Object Storage trigger and the Object Storage event, it may cause increased usage and result in excessive cost being billed due to recursive calls.

• Up to 10 triggers can be connected to a single bucket.
• Click the [Create bucket] button to go to the Object Storage console, where you can create a new bucket.
• Click the [Create bucket event] button to create a new bucket event. To learn how to create bucket events, refer to Object Storage Guide.
  

Events delivered to trigger

When an event created in Object Storage occurs, the event's information will be delivered to the Object Storage type trigger. The delivered event can be used as a parameter in action code connected to a Object Storage trigger, enabling a wide range of applications. The following is an example of an event delivered to an Object Storage type trigger.

{
  "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 the user access key
  "remote_user_type": "user",            // User type
  "request_method": "PUT",               // Request method
  "request_type": "REST.PUT.OBJECT",     // Request type
  "timestamp_finish": "1627881611929",   // Time when the request processing finished, Unix time, milliseconds
  "timestamp_start": "1627881611914"     // Time when the request processing started, Unix time, milliseconds
}

• If remote_user_type is not user, then remote_address and remote_user_sha256 are null.
• Refer to Object Storage Guide for more information about bucket events.