Bucket Actions
There are six actions in Bucket:
Object Versioning
Presigned URL
Lifecycle Rule
Replication Rule
Empty
Add to CDN
Delete
Object Versioning
E2E provides an Object Versioning feature in Object storage. Using this feature, users can upload duplicate files, which will be stored in Minio with different versions.
To enable versioning, click on the Action button and select Object Versioning.
Presigned URL
E2E provides a Presigned URL feature in Object Storage. This feature allows users to generate presigned URLs for files in their buckets, enabling direct download or upload of files via these URLs. Users can also easily integrate upload presigned URLs into their code for seamless file uploads.
After clicking on Generate Presigned URL, you have to enter the required details and select the type of URL, as shown below.
Now click on Generate URL to create the Presigned URL.
Lifecycle Rule
E2E provides a Lifecycle Rule feature in Object storage. Using this feature, users can apply a lifecycle rule to a bucket. After applying this, the object will be deleted as per your set rule. To set it up, click on the Action button, select Lifecycle Rule, enter the details, and click Save.
Replication Rule
E2E provides a Replication Rule feature in Object Storage. This feature allows users to transfer their objects from one region to another region's bucket. To enable replication, click on Action and select Replication Rule. Enter the required details and click Save.
For enabling replication rule, versioning must be enabled for the bucket.
Users can perform actions on the replication bucket by clicking on Action. Available actions include Delete and Disable.
Empty Bucket
Using the Empty action, the user can empty the bucket, which will delete all objects from it.
Add to CDN
EOS integration with CDN improves the performance, scalability, and reliability of the platform by leveraging the capabilities of a Content Delivery Network.
Users can perform actions on Add to CDN by clicking on the Action button.
To add CDN, you need to give public access to your bucket.
After clicking on Add to CDN, click on Create CDN.
Once created, a new section named Bucket CDN will appear in the Manage Object Storage interface, showing the details of the CDN.
You can access comprehensive details about CDN services and view all their actions in the dedicated CDN section.
Upload Files
Permissions
In the Permissions tab, permission details are displayed, and customers can apply permissions to the bucket using the access key and perform actions on it.
Access Key
If you intend to use CLI or API for accessing your data on EOS, you will need to define bucket permissions.
Customers can create access keys using the Manage Access Keys option in the Permissions tab.
Using Manage Access Key
To create an access key, click on the Manage Access Keys button.
Actions in Manage Access Key
Customers can perform two actions on access keys: Lock, Unlock, and Delete.
-
Go to Products > Storage option in the sidebar menu
-
Choose any bucket or create a new one
-
Click the Permissions tab
-
Click the Create Access Key button
-
Enter a name for your access key
-
Choose an access key or create a new one
-
Assign a role:
Role Permissions bucket admin can read, write, manage bucket writer can read, write bucket reader can read
Public Access Config
Using Public Access Config, you can give the permissions for Upload, Download, Upload & Download, or Private for the objects using URL. To enable this, click on Public Access Config and select the desired permission.
Bucket Lifecycle
In this section, the lifecycle rules you have created are displayed. You can also create and perform actions on these rules.
Bucket Details
In this section, the details of the bucket are displayed.
Bucket Permissions
If you intend to use CLI or API for accessing your data on EOS, you will need to define bucket permissions.
-
Go to Products > Storage option in the sidebar menu
-
Choose any bucket or create a new one
-
Click the Permissions tab
-
Click the Create Access Key button
-
Enter a name for your access key
-
Choose an access key or create a new one
-
Assign a role:
Role Permissions bucket admin can read, write, manage bucket writer can read, write bucket reader can read -
Save the permission.
Create Access Key
You can create an access key from the Permissions tab on the Bucket details page or the Manage Access page.
- Enter a name for your access key (application name, project name, or team member name).
- Click Generate Key.
- A newly generated access and secret key will be displayed.
- Keep a note of both keys as you will not see them again after you close the modal window.
- If you have mc setup, use the given command to configure CLI for this access key.
Hint: Choose a short name for the access key, as you will be entering this for each command you type in CLI.
Manage Access
Sometimes you may need to disable access for certain users or applications. You can lock their access key from the Manage Access page.
- Go to Products > Storage option in the sidebar menu
- Click Manage Access Key
- Identify the access you want to lock by key name
- Click the Lock icon
To unlock, follow the same steps, but click the Unlock icon.
Protect Your Bucket Data With Encryption
Introduction
The procedure on this page configures and enables Server-Side Encryption with Client-Managed Keys (SSE-C). EOS SSE-C supports client-driven encryption of objects before writing the object to the drive. Clients must specify the correct key to decrypt objects for read operations.
Prerequisites
- The mc client is required to encrypt an object (How to install mc client).
- The SSE-C key must be a 256-bit base64-encoded string.
- The client application is responsible for generating and storing the encryption key.
- EOS does not store SSE-C encryption keys and cannot decrypt SSE-C encrypted objects without the client-managed key.