Data Processing and Usage

Updated at：2025-11-03

Lifecycle management

BOS allows users to set lifecycle rules for buckets to automatically clear expired files and save storage space. Users can set multiple rules simultaneously for files with different prefixes. For details, please refer to [Lifecycle Management](BOS/API Reference/Bucket-Related Interface/Lifecycle/PutBucketLifecycle.md)

Set lifecycle rules

Lifecycle rules can be set in the following two ways:

                Java
                
                // 1. In the form of a Json string
String jsonBucketLifecylce = "{\"rule\":[{\"id\":\"yourBucketName/*-DeleteObject\""+",\"status\":\"enabled\""+",\"resource\":[\"yourBucketName/*\"]"+",\"condition\":{\"time\":{\"dateGreaterThan\":\"2018-09-07T00:00:00Z\"}}"+",\"action\":{\"name\":\"DeleteObject\"}}]}";
SetBucketLifecycleRequest request = new SetBucketLifecycleRequest("yourBucketName",jsonBucketLifecylce);
client.setBucketBucketLifecycle(request);

                Java
                
            

                // 2. Users only need to specify the parameters
List<Rule> rules = new ArrayList<Rule>();
List<String> resource = new ArrayList<String>();
Action action = new Action();
Condition condition = new Condition();
resource.add("yourBucketName/*");
action.setName("DeleteObject");
Time time = new Time();
time.setDateGreaterThan("2018-09-07T00:00:00Z");
condition.setTime(time);
Rule rule = new Rule();
rule.setId("yourBucketName/*-DeleteObject");
rule.setStatus("enabled");
rule.setResource(resource);
rule.setCondition(condition);
rule.setAction(action);
List<String> resource1 = new ArrayList<String>();
Action action1 = new Action();
Condition condition1 = new Condition();
resource1.add("yourBucketName/*");
action1.setName("Transition");
action1.setStorageClass("STANDARD_IA");
Time time1 = new Time();
time1.setDateGreaterThan("2018-09-08T00:00:00Z");
condition1.setTime(time1);
Rule rule1 = new Rule();
rule1.setId("yourBucketName/*-Transition");
rule1.setStatus("enabled");
rule1.setResource(resource1);
rule1.setCondition(condition1);
rule1.setAction(action1);
rules.add(rule1);
rules.add(rule);
SetBucketLifecycleRequest request = new SetBucketLifecycleRequest();
request.withBucketName("yourBucketName");
request.setRuleList(rules);
client.setBucketBucketLifecycle(request);
            

View lifecycle rules

The lifecycle rules in a bucket can be viewed through the following code:

                Java
                
                GetBucketLifecycleRequest request = new GetBucketLifecycleRequest("yourBucketName");
GetBucketLifecycleResponse response = client.getBucketLifecycle(request);

Delete lifecycle rules

A lifecycle rule can be cleared through the following code:

                Java
                
                DeleteBucketLifecycleRequest request = new DeleteBucketLifecycleRequest("yourBucketName");
client.deleteBucketLifecycle(request);

Cross-origin resource sharing (CORS for short) is a standard cross-origin solution provided by HTML5. BOS currently supports the CORS standard to achieve cross-origin access. For an introduction to cross-origin access, please refer to [Cross-Origin Access](BOS/Developer Guide/Bucket Basic Operations/Setting Cross-Origin Resource Sharing (CORS).md).

Set CORS rules

Cross-domain rules can be set in the following two ways:

                Java
                
            

                // 1. In the form of a Json string
String jsonBucketCors = "{\"corsConfiguration\": [{\"allowedOrigins\":[\"http://*\""+",\"https://*\"]"+",\"allowedMethods\":[\"GET\""+",\"HEAD\""+",\"POST\""+",\"PUT\"]"+",\"allowedHeaders\":[\"*\"]"+",\"allowedExposeHeaders\":[\"ETag\""+",\"Content-Length\""+",\"x-bce-next-append-offset\""+",\"x-bce-object-type\""+",\"x-bce-request-id\"]"+",\"maxAgeSeconds\":1800}]}";
SetBucketCorsRequest request = new SetBucketCorsRequest();
request.setJsonBucketCors(jsonBucketCors);
request.withBucketName("yourBucketName");
client.setBucketBucketCors(request);
            

                Java
                
            

                // 2. Users only need to specify the parameters
SetBucketCorsRequest request = new SetBucketCorsRequest();
request.setBucketName("yourBucketName");
List<CorsConfiguration>  corsConfigurations = new ArrayList<CorsConfiguration>();
List<String> allowedOrigins = new ArrayList<String>();
List<AllowedMethods> allowedMethods = new ArrayList<AllowedMethods>();
List<String> allowedHeaders = new ArrayList<String>();
List<String> allowedExposeHeaders = new ArrayList<String>();
CorsConfiguration corsConfiguration = new CorsConfiguration();
CorsConfiguration corsConfiguration1 = new CorsConfiguration();
// AllowedOrigins
allowedOrigins.add("http://www.example.com");
allowedOrigins.add("http://www.example1.com");
allowedMethods.add(AllowedMethods.GET);
allowedMethods.add(AllowedMethods.POST);
allowedMethods.add(AllowedMethods.PUT);
allowedMethods.add(AllowedMethods.DELETE);
// allowedHeaders
allowedHeaders.add("head1");
allowedHeaders.add("head2");
// allowedExposeHeaders
allowedExposeHeaders.add("ETag");
allowedExposeHeaders.add("Content-Length");
allowedExposeHeaders.add("x-bce-next-append-offset");
allowedExposeHeaders.add("x-bce-object-type");
corsConfiguration.setAllowedOrigins(allowedOrigins);
corsConfiguration.setAllowedMethods(allowedMethods);
corsConfiguration.setAllowedHeaders(allowedHeaders);
corsConfiguration.setAllowedExposeHeaders(allowedExposeHeaders);
corsConfiguration.setMaxAgeSeconds(1800);
List<String> allowedOrigins1 = new ArrayList<String>();
List<AllowedMethods> allowedMethods1 = new ArrayList<AllowedMethods>();
List<String> allowedHeaders1 = new ArrayList<String>();
List<String> allowedExposeHeaders1 = new ArrayList<String>();
corsConfigurations.add(corsConfiguration);
// AllowedOrigins
allowedOrigins1.add("allowedOrigin1");
allowedOrigins1.add("allowedOrigin2");
// allowedMethods
allowedMethods1.add(AllowedMethods.GET);
allowedMethods1.add(AllowedMethods.POST);
allowedMethods1.add(AllowedMethods.PUT);
allowedMethods1.add(AllowedMethods.DELETE);
// allowedHeaders
allowedHeaders1.add("head3");
allowedHeaders1.add("head4");
// allowedExposeHeaders
allowedExposeHeaders1.add("ETag");
allowedExposeHeaders1.add("Content-Length");
allowedExposeHeaders1.add("x-bce-next-append-offset");
allowedExposeHeaders1.add("x-bce-object-type");
corsConfiguration1.setAllowedOrigins(allowedOrigins1);
corsConfiguration1.setAllowedMethods(allowedMethods1);
corsConfiguration1.setAllowedHeaders(allowedHeaders1);
corsConfiguration1.setAllowedExposeHeaders(allowedExposeHeaders1);
corsConfiguration1.setMaxAgeSeconds(3600);
corsConfigurations.add(corsConfiguration1);
request.setCorsConfigurationsList(corsConfigurations);
client.setBucketBucketCors(request);
            

Note:

Before using this API to set CORS rules, the bucket's CORS permission is configured to disallow cross-origin operations.

Each bucket permits only a single rule file. Therefore, uploading a new rule file will overwrite any existing rules.

The size limit for a CORS rule file is 20KB. Requests exceeding this size will result in a 400 Bad Request error with the EntityTooLarge code.

Get CORS rules

Cross-domain rules can be got in the following way:

                Java
                
                GetBucketCorsRequest request = new GetBucketCorsRequest();
request.setBucketName("yourBucketName");
GetBucketCorsResponse response = client.getBucketCros(request);

Delete CORS rules

Cross-domain rules can be deleted in the following way:

                Java
                
                DeleteBucketCorsRequest request = new DeleteBucketCorsRequest("yourBucketName");
client.deleteBucketCors(request);

Set access logs

The BOS SDK supports recording request logs when users access the bucket, including information such as the requester, bucket name, request time, and request operation. For a detailed functional description of bucket logs, please refer to [Setting Access Logs](BOS/Developer Guide/Bucket Basic Operations/Set access logs.md)

Enable bucket logs

Request parameters

Name	Description	Types	Required or not
targetBucket	Specified bucket for storing access logs	String	Yes
targetPrefix	Specify the prefix of the ultimately saved access log file.	String	No (it is recommended that this field should be filled in for distinguishing access logs)

Currently, there are two ways for users to use it

In the form of a JSON string
Users only need to specify the parameters

Log rules can be set in the following two ways:

                Java
                
            

                // 1. In the form of a Json string
SetBucketLoggingRequest setBucketLoggingRequest = new SetBucketLoggingRequest();
setBucketLoggingRequest.setBucketName("yourBucketName");
String jsonPutBucketLogging = "{\"targetBucket\":\"yourTargetBucketName\""+",\"targetPrefix\":\"mylog1/\"}";
setBucketLoggingRequest.setJsonPutBucketLogging(jsonPutBucketLogging);
client.setBucketLogging(setBucketLoggingRequest);
            

                Java
                
            

                // 2. Users only need to specify the parameters
SetBucketLoggingRequest request = new SetBucketLoggingRequest();
request.setBucketName("yourBucketName");
request.setTargetBucket("yourTargetBucketName");
request.setTargetPrefix("mylog/");
client.setBucketLogging(request);
            

View bucket log settings

Log rules can be got in the following way:

                Java
                
                GetBucketLoggingRequest request = new GetBucketLoggingRequest();
request.withBucketName("yourBucketName");
GetBucketLoggingResponse response = client.getBucketLogging(request);

Disable bucket logs

Log rules can be turned off in the following way:

                Java
                
                DeleteBucketLoggingRequest request = new DeleteBucketLoggingRequest("yourBucketName");
client.deleteBucketLogging(request);

Multimedia cloud processing

Currently, uploading files in mp4 format is supported, and the system automatically saves them in hls format for reading by m3u8-style players. For detailed rules and constraints, see [Audio and Video Processing API](BOS/API Reference/Audio and Video Processing Interface.md).

Set up audio and video processing

The BOS multimedia cloud processing API is defined as follows:

Format conversion parameter

Parameter name	Abbreviation	Types	Value	Command description	Required or not
format	f	string	[hls]	Convert the video to a specified format	Yes
time	t	int	[6,600]	Segment duration, defaulting to 10 s	No

Persistent storage parameter

Parameter name	Abbreviation	Types	Value	Command description	Required or not
object	o	string	-	The object name encoded with base64 is limited by the length of the object, which is no more than 1,024 characters (here is the name of the m3u8 file after transcoding, such as xxx.m3u8)	Yes

Set it in the following way through the SDK:

                Java
                
            

                File file = new File("vedioProcessTest.mp4");
String bucketName = "yourBucketName";
String mp4ObjectKey = "vedioProcessTest.mp4";
String m3u8Path = "video/demo.m3u8";
String encodeToString = Base64.getEncoder().encodeToString(m3u8Path.getBytes(Charset.defaultCharset()));
PutObjectRequest request = new PutObjectRequest(bucketName, mp4ObjectKey, file);     
request.setVideoProcess("video/format,f_hls|system/save,o_" + encodeToString);
PutObjectResponse response = client.putObject(request);
            

Exception handling

Bucket management