--- title: "Troubleshooting & FAQs" description: "Common Object Storage issues, security information, and frequently asked questions" --- # Troubleshooting & FAQ ## Common Issues | Issue | What to do | | :--- | :--- | | **"Access Denied" from a CLI tool** | Open the bucket's **Setup** or **Overview** tab, copy the current Access Key and Secret Key, and reconfigure the client. Check you are pointing at the EOS endpoint shown on the same tab. | | **Bucket name is rejected as taken** | EOS bucket names share one global namespace across every E2E customer, and a deleted bucket keeps its name for a while. Choose another name. | | **Bucket name is rejected as invalid** | Use 3–63 characters, lowercase letters, numbers, and hyphens only, starting and ending with a letter or number. | | **Bucket not visible in an Instance or Virtual Machine** | It was not attached when the workload launched. Attach it from the workload's storage options and restart. | | **Uploaded files do not appear** | Refresh the **Data Objects** tab, or list the bucket with an S3 client to confirm the upload completed. | | **Slow uploads from the web UI** | Use `mc cp` or `s3cmd put` for large files or many small ones. A single compressed archive uploads faster than thousands of individual files. | | **Cannot write to `/datasets/`** | Object Storage mounts read-only. Write through an S3 client or, on an Instance or Virtual Machine, mount a [Block Storage](/docs/tir/block-storage/) disk alongside. | | **Versioning column looks stale** | A very recent change may take a moment to appear in the listing. Open the **Object Versioning** action to confirm the current setting. | | **Save is disabled in the Object Versioning dialog** | The bucket must be in a **Ready** state, and you must tick the acknowledgement checkbox. | | **Cannot disable versioning** | The bucket has object lock enabled, which requires versioning. It cannot be suspended while the lock is in place. | | **Object Lock tab says it cannot be enabled** | Object lock is create-time only. Create a new bucket with it enabled and copy the objects across. | | **Cannot delete an object version** | It is under a legal hold, or still within its governance retention. Clear the hold from **Lock Settings**, or bypass governance if you are the project owner or a project admin. | | **Empty Bucket stops partway** | A version under retention or legal hold blocked it. Clear those locks, then empty again. | | **Empty or Delete is refused** | The bucket is mounted on a running workload, or attached to an AI Labs course. The error names what is holding it. | | **Presigned URL lost** | It cannot be retrieved. Generate a new one. | | **No eligible replication destination** | The destination must be a bucket in this project, in a different region, with versioning on and matching encryption, and not already part of a rule. | --- ## Security Overview ### Authentication - **Access keys** — each bucket gets its own S3-style access key and secret key pair, scoped to that bucket. - **RBAC** — project-level IAM controls who can read, create, update, or delete buckets. Actions you lack permission for are hidden. ### Data Security - **Encryption at rest** — SSE-KMS with E2E-managed keys, or SSE-C with your own keys. - **Encryption in transit** — all traffic is secured with TLS. - **WORM retention** — governance lock and legal hold protect object versions from deletion. See [Object Lock](./Features.mdx#object-lock). ### Network Isolation Buckets are logically isolated within your project. Public access is blocked by default; access requires valid credentials, a presigned URL, or a mount from an authorised workload. --- ## Frequently Asked Questions ### General **What is the difference between Object Storage and Block Storage?** Object Storage is an S3-compatible EOS bucket with no fixed size, mounted read-only, ideal for large training data, backups, and model artifacts. [Block Storage](/docs/tir/block-storage/) is a disk of fixed size, mounted read-write, with low latency and high IOPS — best for scratch space and caching. **Can I convert a bucket to Block Storage?** No. Create a Block Storage disk and copy the data across. **What is the difference between the alias and the bucket name?** The **bucket name** is what EOS creates the bucket as, and is unique across all of EOS. The **alias** is the TIR-side name; Instances and Virtual Machines mount the bucket at `/datasets/`. On the create form the two start out identical. **How do I access my bucket from an Instance, Virtual Machine, or Slurm cluster?** Select it when you launch the workload. On an Instance or Virtual Machine it appears read-only under `/datasets/`; on a Slurm cluster, at the mount path you entered. ### Capacity **What is the maximum size?** There is no fixed limit. Capacity grows with your data, and you are billed on peak usage for the month. ### Encryption and Security **Should I use E2E Managed or User Managed encryption?** Use **E2E Managed** unless you have a compliance requirement to hold the keys yourself. With **User Managed**, key loss means permanent data loss — E2E does not hold a copy. **Where do I find my access keys?** On the bucket's **Setup** or **Overview** tab. **Is encryption free?** Yes, both types. ### Versioning and Lock **What happens to old versions when I suspend versioning?** They stay, remain available, and continue to be stored and billed. Suspending only stops new versions being created. **Can I add object lock to an existing bucket?** No. It is create-time only, and enabling it also turns versioning on permanently. **What is the difference between governance lock and legal hold?** Governance lock expires after a retention period and can be bypassed by the project owner or a project admin. Legal hold never expires and must be cleared explicitly; a version under legal hold cannot be deleted even after its retention has run out. ### Data Management **How do I delete data?** Use the **Data Objects** tab, `mc rm`, or `s3cmd del`. To clear the whole bucket at once, use the **Empty Bucket** action. **What happens to my data if I delete the bucket from TIR?** If TIR created the bucket, the bucket and all its objects are deleted permanently — unless the same bucket is still attached under another alias, in which case it is kept. If you attached a pre-existing bucket, the bucket itself is left alone and stays visible in MyAccount. **Can I share a bucket with other project members?** Yes — buckets are accessible to all members of the project. For sharing a single object outside the project, prefer a [presigned URL](./Features.mdx#presigned-urls) over handing out the secret key. ### Lifecycle Rules **Can I recover data deleted by a lifecycle rule?** No. Lifecycle deletion is irreversible. **Can I have several rules on one bucket?** Yes. Use different prefixes to give different data different retention. **Why is the Bucket Lifecycle tab missing?** It is a pre-existing EOS bucket that was attached to TIR, and TIR only manages lifecycle policies for buckets it created.