On this page

Tigris Web Console is the browser UI for creating buckets, uploading objects, managing access keys, and configuring bucket settings.

## Getting Started

1. Create an account at [storage.new](https://storage.new/).
2. Create a bucket with a unique name.
3. Create [access keys](https://console.storage.dev/createaccesskey?pid=019f7258-482e-7b65-af8d-daf14ccaf538&sid=019f7258-4834-7412-ba05-a78b21ff3910) and upload data with any [S3-compatible tool, library, or extension](/content/docs/sdks/s3/index.html).

## Manage access with IAM

Tigris supports fine-grained access control through familiar AWS-style IAM policies, including `Condition` blocks for IP and date-based restrictions.

In the [Access Keys](https://console.storage.dev/createaccesskey?pid=019f7258-482e-7b65-af8d-daf14ccaf538&sid=019f7258-4834-7412-ba05-a78b21ff3910) page of the Web Console you can:

- Create access keys scoped to specific buckets with `Admin`, `Editor`, or `ReadOnly` permissions.
- Attach IAM policies that allow or deny specific S3 actions (`s3:GetObject`, `s3:PutObject`, `s3:ListBucket`, etc.) at the bucket, prefix, or object level.
- Use `Condition` blocks to restrict a key by source IP (`IpAddress`, `NotIpAddress`) or by time window (`DateGreaterThan`, `DateLessThan`, etc.) — useful for locking a key to a CI runner's IP range or auto-expiring a credential.

Policies use the standard AWS IAM JSON syntax (`Version`, `Statement`, `Effect`, `Action`, `Resource`, `Condition`), so existing AWS policies port over directly.

Two prebuilt roles control dashboard access for organization members: `Member` (list and create buckets) and `Admin` (full access plus member management).

See [IAM Overview](/content/docs/iam/index.html), [Manage Access Keys](/content/docs/iam/manage-access-key/index.html), and [IAM Policies](/content/docs/iam/policies/index.html).

## Choose a storage tier

Each bucket has a default storage tier. Pick one based on access patterns:

- **Standard** — frequently accessed data.
- **Infrequent Access** — lower cost for data accessed less often.
- **Archive** — lowest cost; objects need a restore step (~1 hour) before access.
- **Archive Instant Retrieval** — low cost with no restore step.

Override the tier per object at upload time using the S3 storage class (`STANDARD`, `STANDARD_IA`, `GLACIER`, `GLACIER_IR`). See [Storage Tiers](/content/docs/objects/tiers/index.html).

## Configure bucket settings

Open a bucket and click **Settings** to configure:

- **Public / Private Access** — set the default ACL for the bucket, and optionally enable per-object ACLs. See [Public Buckets](/content/docs/buckets/public-bucket/index.html) and [Object ACLs](/content/docs/objects/acl/index.html).
- **Snapshots and Forks** — capture **whole-bucket point-in-time snapshots** and create zero-copy forks of them. Enable snapshots when you create a bucket, or switch an existing bucket between Regular and Snapshot under **Storage** **Settings**. See [Bucket Snapshots and Forks](/content/docs/buckets/snapshots-and-forks/index.html).
- **Bucket Sharing** — share a bucket with other organization members or outside collaborators. See [Bucket Sharing](/content/docs/buckets/sharing/index.html).
- **Bucket Location**, **Cache Control**, **TTL**, **Object Lifecycle**, **Custom Domains**, **CORS**, **Object Notifications**, and **Deletion** **Protection**.

For the full list, see [Bucket Settings](/content/docs/buckets/settings/index.html).

## Migrate from another S3 provider

On a bucket's **Settings** page in the Web Console you can configure a **shadow** **bucket** that lazily migrates data from your existing S3-compatible bucket as it's accessed, with no upfront copy. With **write-through mode** enabled, new writes are mirrored back to the source so you can roll back until you're ready to cut over.

Open a bucket → **Settings** → **Enable Data Migration** → provide the source endpoint and credentials.

See [Migrate to Tigris](/content/docs/migration/index.html) and the provider-specific guides: [AWS S3](/content/docs/migration/aws-s3/index.html), [Google Cloud Storage](/content/docs/migration/gcs/index.html), [Cloudflare R2](/content/docs/migration/cloudflare-r2/index.html), [MinIO](/content/docs/migration/minio/index.html), and [other S3-compatible providers](/content/docs/migration/s3-compatible/index.html).