> For the complete documentation index, see [llms.txt](https://docs.eazybackup.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eazybackup.com/e3-object-storage/advanced/share-files-from-an-e3-storage-bucket.md).

# Share files from an e3 storage bucket

Share bucket files with public access settings or a hosted download page from the Buckets Management tab.

e3 Object Storage gives you two ways to share files from the dashboard.

**Public access** changes the bucket policy so anonymous visitors can open specific objects if they already have the exact URL. Nothing is browsable. There is no file list.

**Public download pages** create a hosted page on eazyBackup where visitors can browse a folder you choose, search file names, and download what they need. The bucket stays private. Access is controlled by the share link, an optional password, or a signed-in eazyBackup account.

Most buckets should stay on **Private**. 

{% hint style="info" %}
Leave buckets on **Private** until you have a specific reason to share.
{% endhint %}

**On this page:** [Private (default)](#private-default) · [Public files](#public-files) · [Public folder](#public-folder) · [Public download pages](#public-download-pages) · [Change or stop sharing](#change-or-stop-sharing)

## Choosing an option

If you need one permanent link to a file and you are fine with anyone who has that URL being able to fetch it, **Public files** or **Public folder** is enough. Copy the object URL from the Bucket Browser after you save the setting.

If you want people to pick files themselves without you sending a URL for every object, use a **Public download page**. That is the better fit for client deliverables, shared asset folders, and anything where you might add or remove files over time.

For a typical hand-off to an external client, a download page with a password and an expiry date is usually the safer choice. Direct public URLs do not expire on their own and there is no gate in front of them.

## Open the sharing controls

Sign in to the client area and open **e3 Object Storage**, then **Buckets**. Click the **Management** tab and scroll to **Public sharing**.

You will see two cards: **Public access** on top and **Public download page** below it.

![Public access options on the bucket Management tab](https://2026595258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSvHh4wgiJn6bl81UXqVT%2Fuploads%2Fwyo8K1jFISJ8MG3VeQTQ%2Fshare-public-access.png?alt=media)

## Private (default)

**Private** is selected by default. Objects need normal authentication. Access keys, signed requests, and the bucket browser all behave the way you expect.

When you save **Private**, e3 removes only the public-read rules it manages itself. If you previously applied a custom bucket policy through the AWS CLI or another S3 tool, those statements are left alone. The dashboard may show a warning when custom rules could still allow anonymous access even though e3 public access is off. See Bucket policies overview if you manage policies outside the dashboard.

Leave new buckets on **Private** until you have a specific reason to share.

## Public files

Choose **Public files** when every object in the bucket needs a direct link and you do not want to maintain a separate folder prefix.

After you select it, click **Save public access**. Anyone with the full HTTPS URL of an object can download or view that file. They cannot list the bucket, guess file names, or walk folders. If they do not have the exact link, they cannot get in.

Once saved, the card shows an example object URL for your bucket. You can also copy URLs from the **Bucket Browser** using **Copy URL** on a selected file. Those links stay valid until you switch the bucket back to **Private** or delete the object.

{% hint style="warning" %}
Public files applies to the whole bucket. Every object is reachable if someone learns or guesses its key. Do not use this mode for buckets that also hold private data.
{% endhint %}

## Public folder

Choose **Public folder** when only part of the bucket should be reachable. Enter the folder prefix in the **Folder** field, then click **Save public access**.

Use a path inside the bucket, with a trailing slash. Examples:

* `documents/` for a top-level folder
* `downloads/manuals/` for a nested folder

Only objects under that prefix get anonymous read access. Files sitting at the bucket root or in other folders stay private.

If the files you want to share live at the bucket root, use **Public files** instead. **Public folder** is for a defined subtree.

The same rules apply as with **Public files**: visitors need the exact object URL. There is still no public file listing.

## Public download pages

A download page is separate from **Public access**. It does not change your bucket policy. You can keep the bucket **Private** and still publish a folder through a hosted page.

Expand **Create download page** on the **Public download page** card.

**Published folder** sets what visitors can browse. Enter a prefix such as `public-downloads/`, or leave it blank to publish from the bucket root. Only that scope appears on the page.

**Access** controls who can open the page:

* **Anyone with the link** — no extra sign-in. Anyone with the URL can browse and download within the published folder.
* **Require password** — visitors enter a password before they see files. Wrong attempts are rate limited.
* **e3 users only** — the visitor must sign in to the eazyBackup account that owns the bucket.

**Link expires** lets you leave the share open indefinitely (**Never**) or stop accepting new visits on a date you pick (**On a specific date**).

Click **Create download page**. The new share appears above the form with its link. Use **Copy link** to send it out.

### What visitors see

The share opens on a lightweight eazyBackup page, if the share is password protected, they enter the password first. If it is restricted to e3 users, they sign in.

Downloads use short-lived signed links, typically valid for about five minutes. A link that was already issued may still work briefly after you disable the page.

### When to use a download page

Use a download page when you want browsing without making the whole bucket public. It works well for deliverables, shared libraries, and folders that change over time. Use **Require password** when you are sending files to someone outside your organization.

You can run a download page while the bucket stays **Private**. You can also combine a **Public folder** with a download page on the same prefix if you need both direct object URLs and a browsable page. 

## Change or stop sharing

**Public access:** select **Private** (or switch to a different mode), then click **Save public access**. The change applies as soon as the save succeeds.

**Public download pages:** each active share is listed on the **Public download page** card. **Disable** stops new visitors from using the page. It does not delete the files in your bucket.

If you no longer need a share, disable it when the project ends. For direct public URLs, switch back to **Private** so old links stop working for anonymous visitors.

{% hint style="info" %}
Custom bucket policies applied outside the dashboard are not removed when you choose **Private**. If you use CLI-managed policies, review them separately.
{% endhint %}