Bucket Settings | Tigris Object Storage Documentation
On this page
The Tigris Dashboard lets you configure various settings for your buckets. Here's an overview of the settings you can configure:
- Bucket Sharing: Share buckets between your organization members or outside collaborators.
- Public / Private Access: Set the default access rules for a bucket.
- Bucket Location: Set the location type for a bucket to control where your data is stored.
- Storage Tier: Set the storage tier for a bucket.
- Bucket Type: Switch a bucket between Regular and Snapshot to enable or disable snapshots and forks.
- Cache Control: Set the default Cache-Control header for objects in the bucket.
- Data Migration: Migrate data from one bucket to another (also known as shadow bucket migration).
- TTL Configuration: Set the default time-to-live (TTL) for objects in the bucket.
- Object Lifecycle: Set an Object Lifecycle rule for objects in the bucket.
- Custom Domains: Configure a custom domain to serve your bucket content.
- Additional Headers: Configure implicit response headers for objects stored in your buckets.
- CORS Configuration: Configure Cross-Origin Resource Sharing (CORS) rules for your bucket.
- Object Notifications: Subscribe to events on your buckets.
- Soft Delete: Keep deleted buckets and objects recoverable for a configurable retention window.
- Delete This Bucket: Permanently delete a bucket.
Sharing [](/content/docs/buckets/settings/#sharing "Direct link to Sharing"/index.html)
You use Bucket Sharing to share buckets between your organization members or outside collaborators. For more information, please see the bucket sharing page: Bucket Sharing.
Public / Private Access [](/content/docs/buckets/settings/#public--private-access "Direct link to Public / Private Access"/index.html)
Tigris lets you control the access rules for a bucket. This section lets you set the default access rules for a bucket (either public or private). You can optionally enable "Allow Object ACL" to let you customize public/private status for individual objects.
Bucket Location [](/content/docs/buckets/settings/#bucket-location "Direct link to Bucket Location"/index.html)
You can set the location type for your bucket to control where your data is stored and how it is replicated across regions. For more information, please see the bucket locations documentation.
Storage Tier [](/content/docs/buckets/settings/#storage-tier "Direct link to Storage Tier"/index.html)
This is set on bucket creation and cannot be changed. For more information, please see the storage tiers page: Storage Tiers.
You can set the storage tier for individual objects when you upload them. For more information, please see the storage tiers page: Storage Tiers: Setting object tier
Bucket Type [](/content/docs/buckets/settings/#bucket-type "Direct link to Bucket Type"/index.html)
A bucket is either Regular or Snapshot. Snapshot buckets support whole-bucket point-in-time snapshots and zero-copy forks.
Some restrictions apply for bucket type changes:
- Regular to Snapshot: the bucket must not use the GLACIER storage tier, object lifecycle rules, or object expiration (TTL) rules, since these are not supported on snapshot-enabled buckets.
- Snapshot to Regular: the bucket must not be a fork parent or a fork child.
note
If a Snapshot bucket is converted to Regular, all object versions are still kept in the bucket.
For more information, see Bucket Snapshots and Forks.
Cache Control [](/content/docs/buckets/settings/#cache-control "Direct link to Cache Control"/index.html)
This lets you set the default Cache-Control header for objects in the bucket.
Tigris will set some
cache control headers by default for
public objects, but you can set an implicit default here.
Data Migration [](/content/docs/buckets/settings/#data-migration "Direct link to Data Migration"/index.html)
You can migrate data from another S3-compatible bucket to Tigris using the data migration feature, also known as shadow bucket migration. The source bucket you migrate from is called a shadow bucket. Tigris copies data lazily as it's accessed, so there's no upfront transfer. Tigris implements the following migration strategy:
- When an object is requested, it is served from your Tigris bucket if it is found.
- If the object is not found in Tigris bucket, the object will be returned from your source bucket and asynchronously copied to Tigris.
- All other operations, including put and delete, continue to work as usual
If you enable the write-through option, Tigris will write the object to your source bucket and Tigris bucket at the same time. This is useful for keeping your source bucket in sync with Tigris.
TTL Configuration [](/content/docs/buckets/settings/#ttl-configuration "Direct link to TTL Configuration"/index.html)
You can set the default time-to-live (TTL) for objects in the bucket. This is useful for buckets that contain ephmemeral data that should be deleted after a certain period of time. For more information see the Object Expiration documentation.
You can configure the following modes:
You can configure Tigris to delete anything older than a given date. This lets you clean up a bucket by deleting old data on the server side.
You can also configure Tigris to automatically delete any object older than a given number of days.
Object Lifecycle [](/content/docs/buckets/settings/#object-lifecycle "Direct link to Object Lifecycle"/index.html)
You can set an Object Lifecycle rule for objects in the bucket. This is useful for buckets that contain lots of old objects that are not accessed that often. They can be transitioned to a different storage tier after a certain period of time. For more information see the Object Lifecycle documentation.
Custom Domains [](/content/docs/buckets/settings/#custom-domains "Direct link to Custom Domains"/index.html)
You can configure a custom domain to serve your bucket content. The custom
domain must have a CNAME record that points to the bucket URL. For example, if
you own the domain images.example.com and bucket foo-bucket, the CNAME
record for images.example.com should point to foo-bucket.t3.tigrisbucket.io.
For more information see the Custom Domains documentation.
Additional Headers [](/content/docs/buckets/settings/#additional-headers "Direct link to Additional Headers"/index.html)
You can configure additional headers for objects stored in your buckets. This
can be useful when your tools set incorrect headers or you need to set custom
headers. Right now, the only setting implemented is to set the
X-Content-Type-Options header to nosniff, which prevents browsers from
performing "content sniffing" and guessing the MIME type of the content based on
the content itself.
CORS Configuration [](/content/docs/buckets/settings/#cors-configuration "Direct link to CORS Configuration"/index.html)
You can configure Cross-Origin Resource Sharing (CORS) rules for your bucket. This allows you to have a website dynamically fetch data from Tigris. For more information see the CORS Configuration documentation.
Object Notifications [](/content/docs/buckets/settings/#object-notifications "Direct link to Object Notifications"/index.html)
Object notifications allow you to subscribe to events on your buckets. For more information see the Object Notifications documentation. You can configure the following settings:
- Webhook URL: The URL to send the notification to.
- Authentication type: None, token or password.
- Filter: SQL style filtering for objects.
Tigris will notify you on the following events:
- New objects being put into buckets.
- Existing objects being deleted from buckets.
Soft Delete [](/content/docs/buckets/settings/#soft-delete "Direct link to Soft Delete"/index.html)
Soft Delete keeps deleted buckets and objects recoverable for a configurable retention window (7–90 days, default 7) instead of removing them immediately. Within that window you can restore them; after it expires, Tigris purges them automatically. Enable it under Bucket Settings → Data Management. See the Soft Delete page for the full feature.
Delete This Bucket [](/content/docs/buckets/settings/#delete-this-bucket "Direct link to Delete This Bucket"/index.html)
You can delete a bucket by clicking the "Delete Bucket" button. This will permanently delete all objects in the bucket. This action cannot be undone.
When you delete a bucket, its name will become unavailable for reuse for a few minutes while the deletion is processed. If you try to create a new bucket with the same name during this time, you will receive an error.