On this page, you can find an explanation of how to use Object Storage with its integrated S3-Browser in the Cloud Console, how to create and delete buckets, how to navigate through folders and files, upload and download files and instructions for other steps to manage an Object Storage effectively in the Cloud Console.
In the Cloud Console, you have the option to use Object Storage with its integrated S3-Browser, which offers essential Object Storage functionality.
With our S3 browser, you can perform the following actions:
This integrated S3 browser provides an efficient and user-friendly way to manage your Object Storage resources within the Cloud Console. Before we start using the integrated S3-Browser, we need to create Object Storage credentials that include the access key and secret key.
š” To find instructions on how to create Object Storage Credentials in the Cloud Console, please, see the article - Object Storage Credentials
To get inside the integrated S3-Browser select theĀ StorageĀ from the VIRTUAL DATACENTER block in the side-bar menu and click theĀ S3 Browser TAB:
These actions will redirect you to the Object Storage Credentials page, and if you have already created Object Storage Credentials, you will have the BROWSE BUCKETS button available:
Clicking on this button will open the integrated S3-Browser and take you to the S3 Buckets page, where you can view all your previously created buckets, create new ones, browse objects inside the buckets, and perform other related actions:
If you haven’t created Object Storage Credentials yet, click on the CREATE S3 CREDENTIALS button and once you have completed this step, you will be able to use the BROWSE BUCKETS button:
š” To find more information about how to manage Object Storage Credentials, please, see the article - Object Storage Credentials.
To create a new S3 Bucket in the Cloud Console, do the following:
After these steps the newly created Bucket will be added to the S3 Buckets page with private access, which is set as the default access setting:
To access and navigate through the folders and files inside a bucket, click on the Name of the corresponding bucket on the S3 Buckets page:
This action will redirect you to the inside Bucket page, where you can find:
To browse inside folders within the bucket, click on the Name of the desired folder:
Inside the folder, you will have access to the same functionality as before, but on a deeper level. This allows you to continue navigating through the nested folder structure, perform actions like creating new folders or uploading files specific to the selected folder, and manage the files and folders within it.
To navigate to the parent level in the folder structure, click on the ../ icon and this action will take you up one level, allowing you to browse the contents of the previous folder in the hierarchy:
To create a new Folder inside S3 Bucket in the Cloud Console, do the following:
After these steps the newly created Folder will be added to the Bucket. Inside the folder, you will have access to the same functionality as before, but on a deeper level. This allows you to continue navigating through the nested folder structure, perform actions like creating new folders or uploading files specific to the selected folder, and manage the files and folders within it.
š As of the current limitations, the largest file you can upload via this integrated S3 browser is 5 GB.
š” If this is your first time attempting to upload a file to the selected bucket, the system may require you to set up CORS (Cross-Origin Resource Sharing) policies. In this case, a dialog window will appear asking you to grant permissions for console access to the specific bucket. Please click on GRANT PERMISSIONS to enable successful file uploading and proceed with the upload process.
š As of the current limitations, you can only download separate files one by one using the integrated S3 browser. There is no direct option to download entire folders or multiple files at once.
To download a File from S3 Bucket to your local environment, do the following:
After these steps, the downloading process of the selected file will start automatically.
You can make your bucket public from both the Buckets page and the inside of the selected Bucket page.
After these steps your bucket will be publicly available and you can obtain a URL that allows direct access to the entire bucket or to individual objects (files or folders) within it. This URL can be shared with others, and they will be able to access the bucket or objects directly through the provided link without requiring any special authentication or permissions.
Making a bucket public allows anyone to access its contents without requiring authentication or special permissions. Please be cautious when setting buckets to public, as it may expose sensitive data to the public. Always review and manage access controls carefully to ensure the security of your data.
You can obtain the URL for S3 bucket only if the bucket is publicly available. In such cases, you can generate a URL that allows direct access to the entire bucket or to individual objects (files or folders) through the provided link. However, if the bucket is not publicly accessible, generating a URL will not grant access, and users will require appropriate authentication and authorization to access the bucket.
You can get your bucket’s public URL from both the Buckets page and the inside of the selected Bucket page.
The next opened window will provide yourĀ bucket’s URLĀ and you can save it by clicking on theĀ COPY TO CLIPBOARDĀ button.
You can obtain the URL for a folder or file in an S3 bucket only if the object is set as publicly available. In such cases, you can generate a URL that allows direct access to the object through the provided link. However, if the object is not publicly accessible, generating a URL will not grant access, and users will require appropriate authentication and authorization to access the object.
To get an object’s public URL, do the following:
The next opened window will provide yourĀ object’s URLĀ and you can save it by clicking on theĀ COPY TO CLIPBOARDĀ button.
You can make your bucket private from both the Buckets page and the inside of the selected Bucket page.
After these steps, your bucket will not be publicly available.
The access permissions will not allow the public to access the bucket or its contents through any direct URL. The objects within the bucket will remain private and can only be accessed by users with appropriate authentication and authorization.
To delete an object from S3 Bucket, do the following:
After these steps, the selected file or folder will be deleted.
Also, the integrated S3 browser allows you to perform multiple deletions of files and folders using the following steps:
After these steps, the selected objects will be deleted in a few seconds.
š Best practice for large datasets
For buckets containing large datasets with numerous files, manually deleting objects one by one or even using multi-delete functionality can be time-consuming and inefficient. In such cases, the best practice is to use the retention policy feature, which provides automated cleanup functionality.
š” To learn more about setting up and managing retention policies for your buckets, please see the section - Set bucket retention policy.
The integrated S3 browser allows you to set a retention policy for your bucket, which provides automatic cleanup functionality for managing large datasets. This feature enables you to specify the number of days after which files will be automatically and permanently removed from the bucket. The bucket itself will never be deleted by the retention policy and will remain intact and functional.
To set a retention policy for your bucket, do the following:
After these steps, the retention policy will be active for your bucket. All files that are older than the specified number of days will be automatically and permanently deleted from the bucket. The bucket itself will never be affected by this policy and will remain available for new uploads and continued use.
š Once a retention policy is applied to a bucket, you cannot modify the existing policy settings. If you need to change the retention period, you must first delete the current policy and then set a new one with the desired settings.
Setting a retention policy will permanently delete files older than the specified number of days. This action cannot be undone. Please ensure you have proper backups of important data before applying a retention policy. This feature is particularly useful for managing large datasets that require regular cleanup. Remember that the bucket itself will never be deleted by the retention policy.
ā ļø Lifecycle Configuration Shadowing: If youāve previously set up custom lifecycle rules on your bucket using the S3 API or other tools, please note that these may shadow the retention policy set through the Cloud Console. To avoid unexpected behavior, review and adjust any existing lifecycle rules before applying a new policy.
To quickly delete all files from a bucket with large amounts of data:
This method will clear all bucket content while keeping the bucket itself intact.
ā ļø CRITICAL: You must delete or change the 1-day retention policy before uploading any new files, otherwise new uploads will also be automatically deleted after one day.
š” This technique is the fastest way to empty buckets containing thousands of files, much more efficient than manual deletion methods.
To delete an existing retention policy from your bucket, do the following:
After these steps, the retention policy will be removed from your bucket, and no automatic file deletion will occur. You can then set a new retention policy if needed.
To avoid any potential data loss during the deletion process, in the Cloud Console, you can only delete a bucket if it is empty.
Before deleting a bucket, all files must be removed. To empty your bucket efficiently, you can either use the Fast bucket cleanup technique with retention policy for large datasets, or the multi-delete functionality for smaller amounts of data.
You can delete bucket from both the Buckets page and the inside of the selected Bucket page but before, please ensure that all the objects (files and folders) inside the bucket have been removed or moved to another location.
After these steps, your bucket will be deleted.