--- title: Actions on Object Storage --- # Bucket Actions Each bucket has an **Actions** menu with the following options: - Object Versioning - Presigned URL - Lifecycle Rule - Replication Rule - Empty - Add to CDN - Delete --- ## Object Versioning Object Versioning preserves every version of every object in a bucket, protecting against accidental overwrites and deletions. To enable versioning, open the **Actions** menu and select **Object Versioning**. Toggle the switch to enable it. Once enabled, each new upload of an existing object creates a new version instead of overwriting the previous one. For full details on managing versions, see [Object Versioning](/docs/myaccount/storage/object_storage/versioning). --- ## Presigned URL A Presigned URL grants time-limited access to a specific object without requiring credentials. It can be used to share a file for download or to allow an external application to upload directly to your bucket. To generate a Presigned URL: 1. Open the **Actions** menu and select **Presigned URL**. 2. Select the URL type: **Download** or **Upload**. 3. Set the expiry duration. 4. Click **Generate URL**. Copy the generated URL and share it as needed. The URL expires after the configured duration. --- ## Lifecycle Rule A Lifecycle Rule automatically deletes objects after a defined period, helping manage storage costs for time-limited data. To create a lifecycle rule: 1. Open the **Actions** menu and select **Lifecycle Rule**. 2. Enter the rule name and the number of days after which objects should be deleted. 3. Click **Save**. To view and manage existing rules, see the **Bucket Lifecycle** tab in the bucket detail panel. --- ## Replication Rule A Replication Rule automatically copies objects from one bucket to another, including cross-region buckets. :::info For enabling replication rule, versioning must be enabled for the bucket. ::: To create a replication rule: 1. Open the **Actions** menu and select **Replication Rule**. 2. Enter the destination bucket details and region. 3. Click **Save**. Once created, all new objects written to the source bucket are replicated to the destination. You can **Disable** or **Delete** a replication rule from the **Actions** menu on the replication entry. --- ## Empty Bucket The **Empty** action permanently deletes all objects in the bucket. The bucket itself is retained. :::warning This action cannot be undone. All objects are permanently deleted. ::: To empty a bucket, open the **Actions** menu, select **Empty**, and confirm the action. --- ## Add to CDN Integrating your bucket with CDN distributes your content across edge locations, reducing latency for end users. :::info The bucket must have **public access** enabled before it can be added to CDN. ::: To add a bucket to CDN: 1. Open the **Actions** menu and select **Add to CDN**. 2. Click **Create CDN**. Once created, a **Bucket CDN** section appears in the bucket detail panel showing the CDN URL and status. Full CDN configuration and actions are available in the dedicated CDN section under **Other Services**. --- ## Delete Bucket Permanently deletes the bucket and all its contents. :::warning Buckets with active **Object Lock** or **Legal Hold** on objects cannot be fully deleted until all locks are cleared. ::: --- ## Upload Files To upload files to a bucket: 1. Open the bucket and go to the **Objects** tab. 2. Click **Upload**. 3. Select one or more files from your local system. 4. Click **Upload** to confirm. Uploaded files appear in the object list. For large or automated uploads, use the [mc CLI](/docs/myaccount/storage/object_storage/work_cli) or the [S3-compatible API](/docs/myaccount/storage/object_storage/using_api). --- ## Public Access Config Public Access Config controls whether objects in the bucket can be accessed via URL without authentication. Available access modes: | Mode | Description | |---|---| | **Private** | No public access (default) | | **Download** | Anyone can download objects via URL | | **Upload** | Anyone can upload objects via URL | | **Upload & Download** | Both upload and download are publicly allowed | To configure public access, click **Public Access Config** on the bucket and select the desired mode. :::warning Setting a bucket to public exposes all objects to the internet. Only use this for content intended for public consumption. ::: ---