Find a bucket's access keys and endpoint

Find the access key, secret key, and endpoint of a bucket, so that an S3 tool or SDK can reach it.

Before you begin

• A bucket; see Create a bucket.
• Permission to read datasets in the project. A Member gets it through a policy that allows reading datasets. Anyone with permission to open the bucket can see its keys.

Open the keys

1. In TIR, open your project. In the side menu, under Storage, select Object Storage (EOS Dataset).
2. Select the row of the bucket.
3. Open the Overview tab. Under Storage Details are the Access Key, the Secret Key, hidden until you reveal it, and the EOS Endpoint, each ready to copy.

The Overview tab also has the Bucket Name and the Alias (Dataset Name). Right after you create a bucket, Next Steps gives the same details.

You can show the secret key again on the Overview tab at any time, and the Setup tab prints it inside its commands too. Share the keys only with people who need them, and keep them out of outside channels such as GitHub. The keys stay the same for as long as the bucket exists.

Use the keys

Give the Access Key, Secret Key, and EOS Endpoint to any S3-compatible tool: mc, s3cmd, s3fs, or the AWS and MinIO SDKs. For the MinIO CLI and s3cmd, the Setup tab has ready-to-paste commands with these values filled in. See Connect to a bucket with the MinIO CLI or s3cmd.

To give one person a single object while keeping the secret key to yourself, use a presigned URL.

If an S3 tool answers “Access Denied”, see Troubleshooting TIR Object Storage.