--- title: "Creating an Object Store in WEKA" slug: "creating-an-object-store-in-weka" updated: 2026-10-30T21:10:34Z published: 2026-10-30T21:10:34Z canonical: "docs.wasabi.com/creating-an-object-store-in-weka" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt > Use this file to discover all available pages before exploring further. # Creating an Object Store in WEKA In WEKA NeuralMesh, [Object stores](https://docs.weka.io/weka-system-overview/filesystems-object-stores-and-filesystem-groups#object-stores-overview) can be used to extend the SSD performance tier with a cost-efficient capacity tier. This article details the steps to configure a Wasabi bucket as an object store. ## Requirements - WEKA cluster version 4.4.35 or higher - Data Protection Option (DPO) license - An active Wasabi account - Access & Secret Key Pair (see [3—Creating a User Account and Access Key](https://docs.wasabi.com/docs/creating-a-user-account-and-access-key)) - Wasabi bucket (see [2—Working With Buckets and Objects](https://docs.wasabi.com/docs/working-with-buckets-and-objects)) ## Configuration 1. Log in to the WEKA dashboard. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-10-27 at 10.46.19 PM.png) 2. Navigate to **Manage**. 3. Select **Object Stores**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-10-27 at 11.00.03 PM.png) 4. In the Object Store Buckets section, click **+ Create.** ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-10-27 at 11.08.31 PM.png) 5. In the Create Object Store Bucket dialog box, provide the following details. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-10-27 at 11.31.44 PM.png) - Name—Provide a name for the object store bucket. - Object Store—Select **default-local** to create a bucket for tiering and snapshots, select **default-remote** to access read-only snapshots. - Type—Select **OTHER**. - Protocol—HTTPS_UNVERIFIED. - Hostname—Provide the Wasabi endpoint URL of the region where the bucket is located. - Port—443. - Bucket—Provide the name of the Wasabi bucket. - Auth Method—Select **AWSSignature4**. - Region—Provide the region of the Wasabi bucket. - Access Key—Provide your Wasabi access key. - Secret Key—Provide your Wasabi secret key. 6. Click **Validate** to verify the connectivity to the Wasabi bucket. 7. Click **Create**. > This configuration example uses Wasabi’s us-east-1 storage region. To use another Wasabi storage region, use the appropriate URL as described in [Service URLs for Wasabi's Storage Regions](https://docs.wasabi.com/docs/what-are-the-service-urls-for-wasabis-different-storage-regions). The object store buckets page displays the newly created buckets. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-10-27 at 11.47.41 PM.png) To learn more about managing Object Stores, refer to [Manage object stores](https://docs.weka.io/weka-filesystems-and-object-stores/managing-object-stores). ## Appendix This section provides the command line approach for the above configuration. Attach Wasabi bucket (local, writable): ```plaintext weka fs tier s3 add --site=local --hostname=s3.wasabisys.com --auth-method=AWSSignature4 --port 443 --protocol HTTPS_UNVERIFIED --region=us-east-1 --bucket= --access-key-id= --secret-key= ``` Detach Wasabi bucket (local, writable): ```plaintext weka fs tier s3 add --site=remote --hostname=s3.wasabisys.com --auth-method=AWSSignature4 --port 443 --protocol HTTPS_UNVERIFIED --region=us-east-1 --bucket= --access-key-id= --secret-key= ``` > This configuration example uses Wasabi’s us-east-1 storage region. To use another Wasabi storage region, use the appropriate URL as described in [Service URLs for Wasabi's Storage Regions](https://docs.wasabi.com/docs/what-are-the-service-urls-for-wasabis-different-storage-regions).