Configure a bucket

Bucket settings let you keep previous versions of objects, host a website, delete old data automatically, and allow web pages to load your files. All settings are under Config in the Action column of the bucket.

Versioning

Versioning keeps every version of an object. Each update or deletion creates a new version, so you can restore an earlier one.

1. In the Action column of the bucket, click Config.
2. Open the Versioning tab.
3. Select Enable or Disable, then click Save.

note

The Portal cannot manage non-current versions. To list, download, or restore them, use an S3 client, S3 Browser, or the SDK.

Static website hosting

Static website hosting serves the HTML, CSS, JavaScript, and other files in a bucket as a website, with a public URL from FPT Object Storage.

1. Upload all website files to the bucket.
2. In the Action column of the bucket, click Config.
3. Open the Static Website Hosting tab and select ENABLE WEBSITE HOSTING.
4. Enter the following information, then save:
   • Index Document: the home page of the website, usually index.html.
   • Error Document: the page shown when a URL does not exist.

note

Visitors open the website through the endpoint shown in the tab. Files must be public to load. See Manage permissions.

Lifecycle rules

Lifecycle rules delete objects automatically after a period of time, which saves storage costs. A bucket can have several rules, each for the whole bucket or for objects with a given prefix.

Action	What it deletes
Delete current versions of objects	Current versions after the number of days you set. Without versioning, the object is deleted permanently.
Permanently delete non-current versions of objects	Non-current versions after the number of days you set. These exist only when versioning is enabled.
Delete incomplete multipart uploads	Uploads that did not complete, after the number of days you set.
Delete expired object delete markers	Delete markers that have no older versions left.

With versioning enabled, deleting an object creates a delete marker instead of removing the data, so you can recover it later. A delete marker expires when all older versions of the object are deleted.

note

Some high-risk actions, such as deleting files on a fixed date or transitioning storage class, are not available on the Portal. Configure them with an S3 client.

Create a lifecycle rule

1. In the Action column of the bucket, click Config.
2. Open the Lifecycle Configurations tab and click Create Rule.
3. Enter a Rule Name.
4. In Rule Scope, select Full for the whole bucket, or enter a prefix.
5. Select the actions and the number of days for each, then save. The rule appears in the Lifecycle Configurations tab.

Edit a lifecycle rule

1. Click Edit for the rule.
2. Change the settings and save.

Delete a lifecycle rule

1. Click Delete for the rule.
2. In the confirmation dialog, check the rule name and click Delete.

Bucket CORS configuration

By default, browsers block web pages from other origins from reading data in your bucket. A CORS rule tells the browser which origins (websites or servers) may send requests to the bucket and which HTTP methods they may use.

Create a CORS rule

1. In the Action column of the bucket, click Config.

2. Open the Bucket CORS tab and click Create Rule.

3. Enter the rule details:

   Field	Description
   Rule Name	Name of the rule.
   Allowed Origins	Origins allowed to send requests. Use * to allow all origins.
   Allowed Methods	HTTP methods the origins may use.
   Max Age Seconds	How long the browser caches the CORS response.
   Advanced setting	Expose Headers: response headers that client applications may read. Allowed Headers: headers allowed in Access-Control-Request-Headers.

4. Save the rule. It appears in the Bucket CORS tab.

Edit a CORS rule

1. Click Edit for the rule.
2. Change the settings and save.

Delete a CORS rule

1. Click Delete for the rule.
2. In the confirmation dialog, check the rule name and click Delete.