Configure a ZIP decompression trigger

Use cases

• Batch uploads

  When you need to upload a large number of small files, uploading them individually is time-consuming. You can use the ZIP decompression feature to package the files and upload them as a single archive.

• Complete file uploads

  To ensure data integrity, you can group multiple files into a single resource. Uploading them separately can be unreliable. The ZIP decompression feature ensures all files are uploaded together, improving the success rate.

• Uploads with a specific directory structure

  A website may reference many static resources with a complex directory structure. Creating each directory and uploading files one by one in OSS is inefficient. You can define the directory structure within a ZIP file on your local machine, upload the compressed file to OSS, and use the ZIP decompression feature to extract it.

• Resource distribution

  When you need to distribute a large number of files to users or servers, you can package them into a ZIP file. Using the OSS ZIP decompression feature, you can extract the files to a specified directory, which reduces data transfer time and bandwidth consumption.

Billing

The ZIP decompression feature incurs costs for both OSS storage and FC function calls and resource usage. The details are as follows:

• OSS fees

  You are charged a request fee for accessing resources and a storage fee for storing files in an OSS bucket.

• FC fees

  You are charged for the number of function invocations and the vCPU, memory, and disk resources that invocations consume. These billable items are converted into CU-seconds for billing. For more information, see Billing overview.

Data transfer over an internal endpoint is free of charge.

Limitations

• Storage class limitations

  You must restore objects in the Cold Archive or Deep Cold Archive storage class before they can be decompressed. For objects of the Archive storage class, if Archive Direct Read is not enabled for the bucket, the objects must be restored before they can be decompressed.

• File and folder naming limitations

  Use UTF-8 or GB 2312 encoding for your file and folder names. Otherwise, the names of the decompressed files or folders may be garbled, or the decompression process may be interrupted.

• Package limitations

  The size of a ZIP package cannot exceed 10 GB, and the size of a single file in the package cannot exceed 10 GB. The default maximum execution time for decompressing a single package is 2 hours. If decompression takes longer than 2 hours, you can adjust the function's execution timeout. For more information, see Decompression of a large file fails because the task takes more than two hours to complete.

Configure a ZIP decompression trigger

1. Log on to the OSS console. In the left-side navigation pane, click Buckets.

2. On the Buckets page, click the name of the target bucket.

3. In the left-side navigation pane of the target bucket page, choose . Then, click ZIP package decompression. On the ZIP package decompression panel, configure the decompression rule.

   Parameter	Description	Example
   Service authorization	Create a service-linked role for FC so it can access other cloud services. If you have not logged on to the FC console before, click Authorize to create the AliyunServiceRoleForFC service-linked role.	Not applicable
   Function authorization	Grant FC the permissions to read from and write to OSS. Click Authorize and follow the on-screen instructions to grant the permissions.	Not applicable
   Trigger authorization	Grant OSS the permissions to access FC. Click Authorize and follow the on-screen instructions to grant the permissions. If you have granted the permissions, this parameter is displayed as Trigger role.	Not applicable
   Prefix	Specify a file prefix for the trigger. If you upload a ZIP file with the specified prefix or upload a ZIP file to a directory with the specified prefix, the FC function is triggered. If you leave this parameter empty, the trigger matches all uploaded ZIP files. Important If you leave this parameter empty, circular triggers can occur. Specify a file prefix to prevent this issue. For more information, see How do I prevent circular triggers?	zipfolder/
   Destination directory	Specify the destination directory for the extracted files. If you leave this parameter empty, FC extracts the files to the root directory of the current bucket. For information about the file structure after decompression when different destination directories are configured, see the configuration examples in this topic. Warning To prevent impacts on the regular use of the OSS-HDFS service or to avoid risks of data contamination and data loss, do not set the destination directory to .dlsdata/ when you configure a ZIP decompression rule for a bucket for which the OSS-HDFS service is enabled.	The destination directory is destfolder, and Decompress directly to destination directory is selected. bucket ├─── zipfolder/ │ ├─── a.zip │ └─── b.zip └─── destfolder/ ├─── a.txt ├─── b.txt └─── ... The destination directory is empty, and Keep compressed file name as a directory is selected. bucket/ ├── zipfolder/ │ ├── a.zip │ └── b.zip ├── a/ │ ├── a.txt │ └── ... └── b/ ├── b.txt └── ... The destination directory is destfolder, and Keep compressed file name as a directory is selected. bucket/ ├── zipfolder/ │ ├── a.zip │ └── b.zip └── destfolder/ ├── a/ │ ├── a.txt │ └── ... └── b/ ├── b.txt └── ...

After completing the configuration, you can modify the trigger's file prefix and related FC function settings. For more information, see Configure a native OSS trigger and Function instance specifications and auto scaling rules.

Related documents

• To automatically decompress other types of compressed files, such as .tar or .gz, see decompress-oss.

• To use FC to package and download OSS files, see Package multiple files into a ZIP package for download.

FAQ