> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gcore.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Managing buckets
Gcore Object Storage organizes files into buckets. The built-in file manager handles uploading and organizing files, with controls for public access and lifecycle policies.
## Bucket creation
Navigate to the [Gcore Customer Portal](https://portal.gcore.com) > **Storage** > **Object Storage** and click the relevant storage name. Alternatively, open the storage's three-dot menu and select **Buckets**.
In the dialog that appears, enter a name that meets the following criteria:
* Between 3 and 63 characters.
* Lowercase only.
* No underscores, trailing dashes, consecutive dots, or a mix of dots and dashes — these conflict with DNS notation rules.
* Unique across the entire Gcore Object Storage system. A `This bucket name already exists. Please use a different name` error appears if the name is taken.
Avoid using sensitive information in the bucket name. The bucket name appears in object URLs and is publicly visible.
The new bucket appears in the list once created. The following sections cover how to upload and manage files, control public access, and configure lifecycle policies.
## File manager
The file manager is a browser-based interface for managing files in a bucket. Two setup steps are required before use: configuring CORS and authenticating with S3 credentials.
### CORS setup
To access the file manager, add `https://portal.gcore.com` to the bucket's CORS policy. This is a one-time setup per bucket.
Click the bucket name to open the access settings dialog, then click **Override CORS**.
Configure CORS individually for each bucket.
The [API](/api-reference/storage/storage/create-s3-bucket-cors) also supports multiple allowed origins beyond `https://portal.gcore.com`.
### Authorization
To authorize, click the bucket name, enter the Access key and Secret key, then click **Auth**.
Alternatively, access the file manager from the bucket's three-dot menu by selecting **File manager**.
Keys entered during a session remain active for that session. Each new session requires entering them again.
To avoid re-entering keys manually, save them using the browser's credential manager.
Storage creation generates the Access key and Secret key. Gcore does not store these values. To regenerate lost keys, click **Generate new keys** in the **Object Storage** list using the three-dot menu.
### Adding folders
After [authorizing](/storage/manage-object-storage/manage-buckets-via-the-control-panel#authorization), click **Add folder**. Enter a name in the field and click **Create**.
Each folder displays its last modification date. Click a folder name to open it.
### Uploading files
To upload files, [authorize](/storage/manage-object-storage/manage-buckets-via-the-control-panel#authorization) and click **Select and upload file(s)** either in the bucket root or within a specific folder. Then, follow the standard upload process.
### Deleting folders and files
To delete folders or files, [authorize](/storage/manage-object-storage/manage-buckets-via-the-control-panel#authorization) and click **Delete** next to the desired object. Alternatively, select the checkboxes next to the object names and click **Delete selected**.
Deleting a folder removes all files nested within it.
### Copying file URLs
To copy file URLs, [authorize](/storage/manage-object-storage/manage-buckets-via-the-control-panel#authorization), select objects, and click the relevant button: **Copy S3 URL** or **Copy URL**.
The links for the file `image 3972.png` look like this:
* `s3://s-ed1.cloud.gcore.lu/000-sample-for-articles/test/image%203972.png`
* `https://s-ed1.cloud.gcore.lu/000-sample-for-articles/test/image%203972.png`
Without public HTTP access enabled, the direct file URL returns a 403 error.
## Managing access
Enable public HTTP access to make files directly accessible by URL or to use the bucket as a [CDN origin](/storage/use-storage-as-the-origin-for-your-cdn-resource). Click the three-dot menu on the bucket row, select **Public access to all files**, and confirm by clicking **Apply**.
To revert to private access, click the three-dot menu on the bucket row and click **Default access to all files**.
## Adding lifecycle policy (for S3 in Luxembourg only)
Click the three-dot menu on the bucket row and select **Lifecycle Management**. Set the retention period and click **Save changes**.
To remove an existing policy, click **Cancel policy**.
For other storage locations, configure lifecycle policies with the [AWS CLI](/storage/manage-object-storage/configure-aws-sli-s3cmd-and-aws-javascript-sdk/remove-objects-from-a-bucket-automatically-with-aws-cli).