# Getting Started with Zata.ai This is a comprehensive documentation that provides invaluable assistance to clients during their on-boarding process, **s3-bucket creation**, and **s3-bucket operations**. This concise and user-friendly guide equips clients with step-by-step instructions and best practices to navigate through the setup of their cloud instances smoothly. The documentation offers clear and concise insights, ensuring clients can fully utilize the platform's capabilities. With detailed explanations and practical examples, clients can confidently leverage **Zata.ai** resources to optimize their cloud experience and maximize productivity. # Create & Activate Account This guide explains how to create and activate a new account on **Zata**.\ To ensure security and compliance, **both your email address and phone number must be verified** during signup. ### Overview Creating a Zata account enables you to: * Access the Zata web console * Create and manage storage buckets * Generate access and secret keys * Use Zata with S3-compatible tools and applications Account activation requires **successful verification of both email and phone number**. ### Prerequisites Before starting, ensure that: * You have a valid and accessible email address * You have an active phone number that can receive OTPs * You can access your email inbox and mobile device during signup * You are using a supported web browser (Chrome, Firefox, Safari, or Edge) ### Sign Up for a Zata Account #### 1. Visit the Zata signup page: [**https://zata.ai/signup**](https://zata.ai/signup) #### 2. Enter your Personal Details:

* Fill in the required details * Verify your email address * Click **Next** #### 3. Verification:

* Fill in the required details * Verify your phone number using OTP * Accept the **Privacy Policy** * Click **Start Free Trial** ### Account Activation Confirmation Once **both your email address and phone number are successfully verified**, your Zata account is **automatically activated**. You will see an on-screen confirmation message, after which you will be **redirected to the login page**. You can log in and access your account using **either your username or registered email address**, along with your password, to access the Zata console. # Dashboard The **Storage Dashboard** provides a centralized view of your storage usage, capacity, and activity within **Zata**. It helps you monitor consumption, manage resources, and take quick actions from a single screen.

### Dashboard Overview Once you log in to the Zata console, the dashboard displays real-time insights into your storage environment, including usage metrics, object counts, and bucket information. ### Key Metrics At the top of the dashboard, you will find the following summary cards: * **Storage Used**\ Displays the total amount of storage currently in use against your capacity limit. * **Total Objects**\ Indicates the total number of objects (files) stored across your account. * **Buckets**\ Shows the total number of buckets created across all regions. * **Active Regions**\ Displays the number of active regions you have data in (e.g., Indore, Mumbai). Each metric is updated regularly to reflect the latest available data. ### Region-Specific Metrics & Health Below the plan details, you will find cards dedicated to each active region (e.g., **Indore IDR01** and **Mumbai BOM01**). These cards display real-time system health along with region-specific storage usage, object counts, and bucket quantities. ### Storage Growth The **Storage Growth** section visualizes your daily storage consumption by region over the last 30 days. * Helps track growth patterns and usage spikes across different regions * Useful for capacity planning and forecasting * Data can be exported using the download option ### Storage Capacity The **Storage Capacity** gauge provides a quick snapshot of how much storage you are using relative to your total available capacity. * **Used Storage** – Displays the exact storage consumed * **Available Storage** – Shows remaining storage under your plan * **Total Capacity** – Your total subscribed capacity * **Usage Percentage** – Visual indicator of overall utilization This section helps you decide when to upgrade your plan. ### Quick Actions From the dashboard, you can perform common actions instantly: * **New Bucket** – Create a new storage bucket * **Upgrade Plan** – Increase storage capacity as your needs grow These actions are accessible from the top-right corner of the dashboard. # Managing Profile Settings #### Overview The **Profile Settings** section allows users to manage their personal account information, update contact details, and configure security options such as password changes and multi-factor authentication (MFA). Users can access profile settings from the **account menu** available in the top-right corner of the dashboard. *** #### Procedure **Step 1: Open Profile Settings** 1. Log in to the **Zata.ai Dashboard**. 2. Click on the **Profile icon** located at the **top-right corner** of the dashboard. 3. From the dropdown menu, select **Profile**. This will open the **Profile Settings** page.

*** ### Step 2: Edit Profile Information 1. On the **Profile Settings** page, click **Edit Profile**. 2. The profile fields will become editable. Users can update the following details: * **First Name** * **Last Name** Note: * The **Username cannot be changed** from this page. After making the changes, click **Save Changes**.

*** ### Step 3: Manage Contact Information The **Contact Information** section displays the user's registered email address and mobile number. Fields include: * **Email Address** * **Mobile Number** Important: * The **Email Address cannot be changed** for security reasons. * To update the **mobile number**, users must contact support. *** ### Step 4: Change Account Password Users can update their account password from the **Security** section. 1. Navigate to the **Security** section. 2. Click **Change Password**. 3. Follow the instructions in the secure account settings page. 4. After completion, you will be redirected back to the profile page.

*** ### Step 5: Enable OTP Multi-Factor Authentication (MFA) For additional security, users can enable **OTP-based Multi-Factor Authentication (MFA)**. 1. Click **Enable OTP MFA** in the Security section. 2. A **Mobile Authenticator Setup** page will appear. 3. Install an authenticator application on your mobile device. Supported applications include: * Google Authenticator * Microsoft Authenticator * FreeOTP 4. Open the authenticator app and **scan the QR code** displayed on the screen. 5. Enter the **one-time code generated by the application**. 6. Provide a **Device Name** for the authenticator. 7. Click **Submit** to complete the setup. ![](https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FYu0ntTvgqYQWQK9cL5uE%2Fimage.png?alt=media\&token=45f6822c-2fe3-423c-b04e-d9442051b444) *** **Result** After completing these steps: * Personal information will be updated successfully. * Users can maintain secure access to their account. * Multi-factor authentication provides an additional layer of security. # Manage The **Manage** section is the central control area of the Zata.ai dashboard where all storage resources and access settings are handled. From here, you can monitor your system, manage buckets, preview stored data, control access policies, and generate API keys. It provides complete administrative control over your object storage environment. * **Dashboard** – Gives an overall view of storage usage, buckets, and system activity. * **Buckets** – Used to create, manage, and organize storage buckets and their objects. * **Preview Manager** – Allows you to preview and verify files such as images, videos, and documents without downloading them. * **Policies** – Used to define and manage access control policies for buckets and objects. * **Access Keys** – Used to generate and manage API keys for programmatic access to Zata.ai storage. This section helps in managing storage operations, security, and user access in a structured and efficient way. # Bucket #### Overview Buckets are the core storage containers in Zata, used to organize and store all data within the platform. A bucket acts as a logical container for objects such as files, backups, media, and application data. Each object stored in a bucket is identified by a unique object key, enabling structured and efficient data management. Zata buckets are **S3-compatible** and support standard object storage behavior, allowing seamless integration with commonly used S3 tools, SDKs, and applications. Access to buckets is managed through access keys and bucket policies, ensuring secure, controlled, and role-based data access. Buckets provide a **scalable, durable, and reliable** solution for storing and managing data across a wide range of use cases, including application storage, backups, analytics, and media management. # Create Bucket A **Bucket** in cloud computing is a **container** used to store data. * A bucket acts as a storage container that enables efficient storage, organization, and management of data. Bucket > Create Bucket > Give Bucket Name > Click Create Bucket * Click on the Create bucket Note:- Bucket names can be between 3 and 63 characters long including the \.

Set the unique name.\ Select a region for your bucket. You can choose from available regions such as **Indore** or **Mumbai**.

You can also create a bucket in the **Mumbai** region by selecting it from the Region dropdown.

After this, we can see the Review information like (User name, Bucket name, Region, Versioning, encryption) **Bucket versioning :** * Stores multiple versions of an object (file) * Tracks changes made to an object over time * Allows recovery of deleted or overwritten objects * All versions are stored and can be recovered or reverted to.

**Object Lock (WORM) :** * Prevents objects from being deleted or overwritten for a fixed amount of time or indefinitely. * **Important:** Object Lock can ONLY be enabled when creating the bucket. * Enabling Object Lock automatically and permanently enables Bucket Versioning. There are two modes: Governance and Compliance mode. You can choose either of them. > **Note:** You can change the default object lock settings later from the Bucket Settings page.

You can set the number of days to lock the object versions. The maximum number of days you can set is determined by your account lifecycle.

**Encryption**:- Encryption refers to protecting data by converting it into an unreadable format. To Apply the Tags to Bucket

Now the Review information about bucket, click on the Next.

Now, The bucket review displays details such as bucket name, owner, versioning, public access, creation date, and actions.\ Click on **Create Bucket** to create a new bucket. After successful creation, the bucket becomes visible in the list.

Click on the **Actions** column located to the right of the specific bucket name. In the Actions section, options are available to manage the bucket, such as deleting the bucket, managing tags, and modifying bucket settings.

# Bucket Settings Click on **Settings** to open the bucket configuration page.\ The **Bucket Settings** page allows users to configure bucket properties, versioning, security access, and storage limits.

*** **1. Basic Information** The **Basic Information** section displays the core metadata and properties of the bucket. **Bucket Name** Displays the unique name assigned to the bucket when it was created.\ This name is used to identify and access the bucket within the object storage system. **Region** Indicates the geographical region where the bucket is hosted.\ The selected region determines **data locality, latency, and compliance requirements**. **Current Size** Shows the total storage currently used by all objects inside the bucket. **Total Objects** Displays the total number of objects stored in the bucket. **Created On** Shows the exact **date and time when the bucket was created**. **Last Modified** Displays the most recent timestamp when any object or configuration in the bucket was updated. **Tags** Tags allow users to attach **key–value metadata** to the bucket for easier organization, management, and automation. Example: ``` Environment : Production Project : Backup ```

*** **2. Versioning Management** The **Versioning Management** section controls the object versioning functionality for the bucket.\ \ **Version Control** Version control enables the storage of **multiple versions of the same object**. When **Versioning is Enabled:** * Every update to an object creates a new version. * Older versions are preserved. * Deleted objects can be recovered. This feature helps with: * Data recovery * Protection from accidental deletion * Object rollback

**Note:**\ Once versioning is enabled, it **cannot be completely removed**. It can only be **turned off to stop creating new versions**, while existing versions remain stored. *** **3. Security & Access** The **Security & Access** section controls public accessibility of the bucket. **Public Access** This setting determines whether the bucket is publicly accessible. When **Public Access is Enabled:** * Anyone with the **object URL** can access the files. * Files can be **viewed or downloaded without authentication**. **Warning:**\ Public buckets may expose sensitive data if not properly controlled. **Public URL** Displays the base URL used to access objects in the bucket. Example: ``` https://bucket-name.region.storage-provider.com/object-key ``` Users can access objects by appending the **object key** to the public URL.

*** **4. Storage Management** The **Storage Management** section allows administrators to configure limits on bucket storage usage.\ These limits help control how much storage space and how many objects can be stored in a bucket. **a. Bucket Quota** Bucket Quota allows administrators to set limits on storage consumption for a bucket. Administrators can configure the following limits: **b. Storage Limit** Defines the maximum storage capacity allowed for the bucket. **c. Object Limit** Defines the maximum number of objects that can be stored in the bucket. If no limits are configured, both values remain Unlimited, allowing unrestricted usage of the bucket.

*** **Configure Bucket Quota** To configure storage limits for a bucket, follow the steps below.**Step 1: Open Bucket Quota Configuration** 1. Navigate to the **Bucket Settings** page. 2. Scroll down to the **Storage Management** section. 3. Locate the **Bucket Quota** option. 4. Click on the **Configure** button. This opens the **Bucket Quota configuration panel**.

**Step 2: Enable Bucket Quota** 1. Toggle **Enable Quota** to **ON**. 2. Once enabled, additional fields will appear for configuring limits. Enabling quota allows administrators to control: * Maximum storage usage * Maximum number of objects stored in the bucket

**Step 3: Configure Storage Limits** After enabling quota, the following fields become available: **a. Storage Limit (GB)** Defines the **maximum storage capacity allowed for the bucket**. Example: ``` 100 GB ``` If the storage usage reaches this limit, the system prevents additional uploads until storage becomes available. **b. Object Limit** Defines the **maximum number of objects that can be stored in the bucket**. Example: ``` 10000 objects ``` Once this limit is reached, users cannot upload additional objects until some objects are deleted. **Unlimited Storage or Objects** If the **Storage Limit** and **Object Limit** fields are left empty: * Storage remains **unlimited** * Object count remains **unlimited** **Step 4: Save Configuration** After entering the desired limits: 1. Click **Save Changes** to apply the quota settings. 2. Click **Cancel** to discard any unsaved changes. Once saved, the configured quota limits will be enforced for the bucket. # Deleting Bucket Go to the buckets section.

**Delete Bucket Process:** * ZataCloud follows a minimum storage retention policy, which is applicable to all stored items, even if the objects are deleted. * Deleting a bucket is a critical and irreversible action, so proceed carefully. **Steps to delete a bucket:** 1. Click on the **Delete Bucket** option from the Actions menu. 2. A confirmation pop-up will appear with a warning message stating that this action cannot be undone. 3. Copy the bucket name shown on the screen. 4. Paste the bucket name into the blank confirmation field. 5. Click on the **Delete Bucket** button.

# Deleting Large Buckets **Deleting Large Buckets in Zata** In Zata, buckets that contain a very large number of objects or multiple object versions cannot always be deleted directly through the user interface or by simple API calls. Due to the nature of distributed object storage systems, deleting buckets with large volumes of data requires a controlled and managed process to ensure safety, reliability, and system stability. **Process** **1. Submit a Support Ticket:**\ If you need to delete a bucket that contains a large number of objects or object versions, raise a support ticket and provide the following information: * Full bucket name * Approximate number of objects stored in the bucket * Any relevant details regarding the bucket’s contents or usage **2. Support Team Verification:**\ The Zata support team will review the request to verify that: * The requester has the required permissions to delete the bucket * There are no operational dependencies or regulatory or compliance constraints preventing deletion **3. Deletion Execution and Timeline Confirmation:**\ After successful verification, the support team will perform the deletion using backend procedures optimized to handle large object counts efficiently. Based on the size of the bucket and the volume of objects, the team will communicate the estimated time required to complete the deletion. **Summary** To delete a large bucket in Zata: * Raise a support ticket with all required bucket details * The Zata support team will verify the request and carry out the deletion * The estimated completion time will be shared after verification This controlled approach ensures that large bucket deletions are handled in a secure, reliable, and well-governed manner. # Manage Tags The **Manage Tags** option is used to add, edit, or remove metadata (tags) for a bucket. Tags are key–value pairs that help in organizing, identifying, and managing buckets efficiently. To add a tag, click on **Manage Tags** from the Actions menu. Enter the required Key and Value, or click on the ( + ) Add New Tag button to add more fields. After entering the details, click on Save Changes to apply and store the tag information.

# Storing Objects in a Bucket **Open the Bucket**\ Go to the Bucket List and click on the bucket where you want to store your objects. You can upload objects to buckets in both the **Indore** and **Mumbai** regions.

There are two ways to upload files and folders in Zata. You can upload a file directly into the bucket, or you can first create a folder and then upload files inside that folder. This helps in organizing data in a structured manner. The upload process works the same way for buckets in both the Indore and Mumbai regions. **Upload File Directly**\ Click on the **Upload File** button. A panel will appear where you can either drag and drop files or browse and select files from your system. After selecting the file, the upload process will start automatically.\ \ **Create Folder First (Optional Method)**\ If you want to organize your data, click on **Create Folder**, enter the folder name, and submit.

After selecting the file to click on the upload file then, uploading will start.

After uploading the files we can see details of objects like File name, File type, Size, and Last Updates and actions.

**Object Actions in Zata** For each object, an Actions menu is available that allows you to perform basic operations. The following options are currently supported: * **Share** – Used to generate a temporary presigned URL to provide secure access to the object for a limited time. * **Download** – Used to download the selected object to the local system. * **Delete** – Used to permanently remove the object from the bucket.

# Sharing an Object Using Presigned URL The Share Object feature is used to generate a temporary and secure access link (Presigned URL) for an object. This link allows users to access the object for a limited time without changing bucket permissions. 1.Go to the bucket, locate the required object, and click on the **Actions (three dots)** option. Then select **Share**.

2. **Set Time Duration**\ The Share Object window will appear. Enter the required time in: * **Number of hours** * **Number of minutes** This defines how long the link will remain active.\

**3.Generate the Link**\ Click on **Create Link** to generate the presigned URL.\ After generation, a **Presigned URL** is displayed along with its expiration time.

Click on **Copy URL** to copy the link and share it with the intended user. The link will remain active until the specified expiration time, even if the bucket and object are private.\ \ After copying the URL to paste these URLs your browser and the object is downloaded automatically. # Delete and Restore Object in Zata First, upload an object into the bucket.

**To Delete an Object:** * Click on the **Actions (three dots)** next to the object. * Select **Delete**. * The object will be removed from the main object list.

After deleting the object: * Enable the **Show Versions** option. * The deleted object will appear with a **Delete Marker**.The Delete Marker indicates that the object is deleted but not permanently removed.

**To Restore the Object:** * Click on the **Actions (three dots)** of the **Delete Marker**. * Select **Remove Marker**.

After removing the Delete Marker, the object becomes visible again in the bucket and is successfully restored.

In Zata, the restore operation is performed using the **Remove Marker** option. Removing the Delete Marker automatically restores the object. # Bucket Policy Configuration Bucket Policy is used to manage access control for a bucket by defining who can access it and what actions they can perform. It allows secure and fine-grained permission management without changing the bucket’s public visibility. By creating a bucket policy, specific users or the public can be granted limited access such as read-only or download permissions. This ensures better security and controlled usage of object storage resources.
### Creating an Access Policy 1. From the left sidebar menu, navigate to **Policies**. 2. Click on the **+ Create Policy** button.

The policy creation process follows a simple 4-step wizard: #### Step 1: Grantee Choose who should get access to your bucket. You can grant access to: * **Public**: Anyone on the internet. * **Subuser**: A specific team member. After selecting the grantee, choose the **Region** from the dropdown menu and select the specific subuser if applicable.

#### Step 2: Bucket and scope Select the specific bucket you want to apply this access policy to.

Next, define the **Access scope**: * **Entire bucket**: Access all objects within the selected bucket. * **Specific folders**: Restrict access to specific paths within the bucket.

#### Step 3: Permissions Choose the specific actions that are allowed or denied for the grantee. You can select individual Object operations (e.g., Download files, View file tags) or Bucket operations.

#### Step 4: Review Review the details of your policy setup, including the Grantee, Bucket, and Permissions. * Select the **Effect**: Choose `Allow` to grant the permissions or `Deny` to explicitly restrict them. * (Optional) Enter a **Policy name** for easier identification later. Click **Create access policy** to finalize and apply the rules.

### Managing Policies After successful creation, your new policy will appear in the Access Policies list. From here, you can view, edit, or delete existing policies.

**Delete a Bucket policy:** To delete a policy, navigate to the **Policies** section, locate the policy you want to remove, and select the delete option from the actions menu. This removes all custom access rules defined in that policy. # Applying Limitations with Bucket Policies We have support a subset of the Amazon s3 policy language applied to buckets. ## Policy Creation and Removal Bucket policies are managed through standard S3 operations. For example, I have created a policy to access objects inside the bucket. ``` { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": {"AWS": ["arn:aws:iam:::user/4fe084dd-8531-4087-bc89-91cca2c9ea8d:Access"]}, "Action": "s3:GetObject", "Resource": [ "arn:aws:s3:::pankimages/*" ] }] } ``` ## Limitations Currently, we support only the following actions: * s3:AbortMultipartUpload * s3:CreateBucket * s3:DeleteBucketPolicy * s3:DeleteBucket * s3:DeleteBucketWebsite * s3:DeleteObject * s3:DeleteObjectVersion * s3:DeleteReplicationConfiguration * s3:GetAccelerateConfiguration * s3:GetBucketAcl * s3:GetBucketCORS * s3:GetBucketLocation * s3:GetBucketLogging * s3:GetBucketNotification * s3:GetBucketPolicy * s3:GetBucketRequestPayment * s3:GetBucketTagging * s3:GetBucketVersioning * s3:GetBucketWebsite * s3:GetLifecycleConfiguration * s3:GetObjectAcl * s3:GetObject * s3:GetObjectTorrent * s3:GetObjectVersionAcl * s3:GetObjectVersion * s3:GetObjectVersionTorrent * s3:GetReplicationConfiguration * s3:IPAddress * s3:NotIpAddress * s3:ListAllMyBuckets * s3:ListBucketMultipartUploads * s3:ListBucket * s3:ListBucketVersions * s3:ListMultipartUploadParts * s3:PutAccelerateConfiguration * s3:PutBucketAcl * s3:PutBucketCORS * s3:PutBucketLogging * s3:PutBucketNotification * s3:PutBucketPolicy * s3:PutBucketRequestPayment * s3:PutBucketTagging * s3:PutBucketVersioning * s3:PutBucketWebsite * s3:PutLifecycleConfiguration * s3:PutObjectAcl * s3:PutObject * s3:PutObjectVersionAcl * s3:PutReplicationConfiguration * s3:RestoreObject Instead of the Amazon twelve-digit account ID, we utilize the RGW 'tenant' identifier. In the future, assigning an account ID to a tenant may be possible. However, for now, when creating users for policies between AWS S3 and RGW S3, you must use the Amazon account ID as the tenant ID In AWS, a single namespace is shared by all tenants. RGW provides each tenant with a dedicated namespace for their buckets. In future releases, there might be a choice to activate a 'flat' bucket namespace similar to AWS. Currently, in order to reach a bucket owned by a different tenant, refer to it as "tenant:bucket" when making an S3 request In AWS, a bucket policy allows giving access to a different account, which can further grant access to specific users by assigning user permissions. As user, role, and group permissions are not yet supported, account owners must currently give access to individual users directly. Granting access to a bucket for an entire account will give access to all users in that account. String interpolation is not currently supported by bucket policies. The condition keys we support for all requests are: - aws:CurrentTime - aws:EpochTime - aws:PrincipalType - aws:Referer - aws:SecureTransport - aws:SourceIp - aws:UserAgent - aws:username We uphold specific s3 condition keys for requests related to buckets and objects. Functionality for the specified bucket operations has been included. ### Bucket Related Operations


Permission	Condition Keys
s3:createBucket	s3:x-amz-acl s3:x-amz-grant-<perm> where perm is one of read/write/read-acp write-acp/ full-control
s3:ListBucket & s3:ListBucketVersions	s3:prefix s3:delimiter s3:max-keys
s3:PutBucketAcl	s3:x-amz-acl s3:x-amz-grant-<perm>

### Object Related Operations


Permission	Condition Keys	Comments
	s3:x-amz-acl & s3:x-amz-grant-<perm> s3:x-amz-copy-source
	s3:x-amz-server-side-encryption
s3:PutObject	s3:x-amz-server-side-encryption-aws-kms-key-id
	s3:x-amz-metadata-directive	PUT & COPY to overwrite/preserve metadata in COPY requests
	s3:RequestObjectTag/<tag-key>
s3:PutObjectAcl s3:PutObjectVersionAcl	s3:x-amz-acl & s3-amz-grant-<perm> s3:ExistingObjectTag/<tag-key>
s3:PutObjectTagging & s3:PutObjectVersionTagging	s3:RequestObjectTag/<tag-key> s3:ExistingObjectTag/<tag-key>
s3:GetObject & s3:GetObjectVersion	s3:ExistingObjectTag/<tag-key>
s3:GetObjectAcl & s3:GetObjectVersionAcl	s3:ExistingObjectTag/<tag-key>
s3:GetObjectTagging & s3:GetObjectVersionTagging	s3:ExistingObjectTag/<tag-key>
s3:DeleteObjectTagging & s3:DeleteObjectVersionTagging	s3:ExistingObjectTag/<tag-key>

Additional support may be available in the near future as we merge with the recently revamped Authentication/Authorization subsystem. # Generating a Public Access URL for an Object ### Accessing an Object Using Public URL 1. Log in to the **Zata.ai Dashboard**. 2. Go to the **Buckets** section and select your required bucket. ***

\ 3\. Click on **Bucket Settings**.\ 4\. Open the **Permissions** tab.

5\. Enable public access by adding the following bucket policy: ```json { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": "*", "Action": "s3:GetObject", "Resource": [ "arn:aws:s3:::/*" ] }] } ``` Explanation for documentation: * **Effect: Allow** → Grants permission. * **Principal: "\*"** → Allows access to everyone (public access). * **Action: s3:GetObject** → Allows only read/download access. * **Resource** → Applies to all objects inside the bucket. Replace `` with your actual bucket name.\ Example: ``` arn:aws:s3:::prertest/* ```

\ 7\. Open your **S3 Browser** application.\ 8\. Connect using your access credentials. *** 9\. Your bucket will now be accessible publicly.\ 10\. Navigate inside the bucket and select the required object.

***

\ 11\. Right-click on the object.\ 12\. Select **Generate Web URL**. ***

\ Click on **Copy** . \ 13\. Paste the copied URL into any web browser and press Enter, The object will open directly in the browser using the public URL. \ \
# Object Lock (WORM) Zata.ai provides **S3 Object Lock**, which follows the Write-Once-Read-Many (WORM) model. This feature allows you to store objects using a model that prevents them from being deleted or overwritten for a fixed amount of time or indefinitely. Object Lock helps you meet regulatory requirements that require WORM storage or simply add an extra layer of protection against object changes and deletion. > **IMPORTANT** Object Lock capability can **only be enabled during bucket creation**. It cannot be turned on for an existing bucket. Enabling Object Lock will permanently turn on Bucket Versioning. *** ## Retention Modes and Features Zata.ai's Object Lock offers three distinct ways to protect your data. You can learn how to use and configure each of these by visiting their dedicated pages: * [**Governance Mode**](/manage/bucket/object-lock/governance-mode)**:** Users cannot delete or overwrite an object version or alter its lock settings unless they have special permissions. * [**Compliance Mode**](/manage/bucket/object-lock/compliance-mode)**:** A protected object version cannot be overwritten or deleted by **anyone** until its retention period has expired. * [**Legal Hold**](/manage/bucket/object-lock/legal-hold)**:** Provides the same protection as a retention period, but it has no expiration date and must be explicitly turned off. *** ## Retention Ceilings (Recommended Maximum Dates) When you select a "Retain Until" date in the Zata dashboard for either Governance or Compliance mode, you will see a **Recommended Maximum Date**. Because Zata is a prepaid cloud platform, your data is tied to your billing lifecycle. The recommended maximum date ensures that you don't lock your data past the point when your account might naturally expire or be suspended (e.g., due to the end of a free trial or an unpaid invoice). * **For Trial Users:** The recommended date is usually up to 45 days from account creation. * **For Billed Users:** The recommended date is usually up to 120 days from the start of the current billing cycle. > **NOTE** You can set retention dates beyond this ceiling, but doing so will not prevent data from being wiped if your account is suspended and permanently terminated due to non-payment. *** ## Bulk Retention (Apply to All Unprotected Versions) If you have many objects in a bucket that are not currently protected (e.g., they were uploaded before you enabled a default rule, or their previous retention expired), you can lock them all at once. This action will lock every version that currently has no active retention, while leaving already-locked versions unchanged. You can initiate Bulk Retention from two different places in the Zata Dashboard: **Option 1: From Bucket Settings** Navigate to **Bucket > Settings** and locate the **Object Lock** section. Click the **Apply Retention...** button under the *Protect Existing Versions* section.

**Option 2: From the Files View** Navigate to your bucket's file list and toggle **Show Versions** to ON. Then, click the **Protect All** button.

### Applying the Bulk Retention Regardless of which option you choose, a modal will appear where you can define the retention settings: 1. Select the **Retention Mode** (Governance or Compliance) and set the **Retention Period (Days)**. Then click **Continue**.

2. You will be asked to confirm your choice by typing "CONFIRM".

3. Click **Apply Retention** to instantly apply the chosen retention mode and period to every unprotected version in the bucket. > **Note on Reapplying Retention to Expired Versions** When using Bulk Retention on versions whose previous retention has expired, the success depends on the previous retention mode: > > * If the expired version was previously in **Governance** mode, you can successfully apply either a new Governance or Compliance rule. > * If the expired version was previously in **Compliance** mode, you cannot downgrade it to Governance mode (the new rule will not apply). You can only apply a new Compliance rule. # Governance Mode In **Governance Mode**, users cannot delete or overwrite an object version or alter its lock settings unless they have special permissions. * **Root User Bypass:** The Root User (account owner) can bypass this lock to delete a protected object. This requires explicitly confirming the deletion in the dashboard by typing "confirm". * **Subusers:** Subusers cannot bypass Governance Mode. ## Applying a Default Governance Rule If your bucket was created with Object Lock enabled, you can configure a **Default Retention Rule** in your Bucket Settings so that all new uploads are automatically protected under Governance Mode. 1. Navigate to **Bucket > Settings**. 2. Locate the **Default Retention Rule** section. 3. Select **Governance** from the mode dropdown, and enter the retention period (in days). 4. Click **Apply Changes**.

You will be asked to confirm your choice by typing "CONFIRM".

## Removing a Default Governance Rule To stop automatically locking new uploads under this rule, you can remove it: 1. In the **Default Retention Rule** section, click **Remove Rule**.

2. Confirm the removal.

> **INFO** Removing the default retention rule stops auto-locking new uploads, but it **does not** unlock objects that are already protected. ## Managing Governance on Individual Versions You can view and modify Governance settings for specific object versions directly from the Zata Dashboard. 1. Navigate to your bucket and click on an object to expand its versions list.

2. Click on the three dots (Actions) next to a specific version and select **Lock Settings**.

3. This opens the **Version Details** panel. To change the retention settings, click **Edit**.

4. You can upgrade the retention mode (e.g., from Governance to Compliance) or extend the retention date.

5. After selecting the new settings, click **Save Retention**.

6. Confirm the new settings.

7. The version is now protected under the new settings!

## Deleting a Governance-Protected Version > **Note:** Only the Root User (account owner) can bypass the Governance mode and delete the version. Subusers cannot perform this action. If you are logged in as the root user and attempt to delete a version protected by Governance mode, you will be asked to explicitly type "CONFIRM" to bypass the lock and delete the version.

# Compliance Mode In **Compliance Mode**, a protected object version cannot be overwritten or deleted by **anyone** until its retention period has expired. * **Strict Enforcement:** Not even the Root User or Zata.ai Support can bypass or shorten the retention period. * **Flexibility:** You can extend a Compliance retention period, but you can never shorten it. ## Applying a Default Compliance Rule If your bucket was created with Object Lock enabled, you can configure a **Default Retention Rule** in your Bucket Settings so that all new uploads are automatically protected under Compliance Mode. 1. Navigate to **Bucket > Settings**. 2. Locate the **Default Retention Rule** section. 3. Select **Compliance** from the mode dropdown, and enter the retention period (in days). 4. Click **Apply Changes**.

Confirm your choice by typing "CONFIRM". Remember that Compliance locks cannot be bypassed!

## Managing Compliance on Individual Versions You can view and extend Compliance settings for specific object versions directly from the Zata Dashboard. 1. Navigate to your bucket and click on an object to expand its versions list.

2. Click on the three dots (Actions) next to a specific version and select **Lock Settings**.

3. This opens the **Version Details** panel. Here, you can view the active Compliance lock and its expiration date. To change it, click **Edit**.

> **Note:** You can extend an active Compliance retention period, or re-apply retention to a version that has already expired, but you can never shorten an active Compliance lock. ## Deleting a Compliance-Protected Version > **Note:** Nobody can delete a version that is protected by Compliance mode until the retention period expires. If you attempt to delete a version protected by Compliance mode, the system will block the action entirely.

# Legal Hold **Legal Hold** provides the same protection as a retention period, but it has no expiration date. Instead, a Legal Hold remains in place indefinitely until you explicitly turn it **OFF**. ## How Legal Hold Works * **Independent Protection:** Legal Hold operates completely independent of Retention Modes (Governance and Compliance). An object can have both a retention period and a Legal Hold active at the same time. * **No Expiration:** If an object's retention period expires, but Legal Hold is still ON, the object still cannot be deleted. * **Toggle Freedom:** Unlike Compliance mode which cannot be removed, Legal Hold can be toggled ON and OFF freely at any time by users with the appropriate permissions. ## Managing Legal Hold on Individual Versions Legal Hold is applied on a per-version basis rather than as a default bucket rule. Legal Hold can apply double protection alongside both Governance and Compliance modes, and it is also applicable as a single protection on its own. To turn Legal Hold on or off for an object version: 1. Navigate to your bucket and click on an object to expand its versions list.

2. Click on the three dots (Actions) next to a specific version and select **Lock Settings**.

3. This opens the **Version Details** panel. Under the **Legal Hold** section, click the toggle switch to turn it **ON**.

4. Confirm the Legal Hold activation.

5. The Legal Hold is now active for this version.

6. To turn it off, simply click the toggle switch again and confirm.

## Deleting a Legal Hold Protected Version > **Note:** Nobody can delete the version whenever the toggle is not turned off. If you attempt to delete a version that has an active Legal Hold, the system will block the action entirely until you explicitly toggle the Legal Hold off.

# Lifecycle Rules Lifecycle Rules allow you to automate the management of your objects over time, helping you optimize storage costs by cleaning up old data, expiring objects, and removing incomplete uploads. You can manage your lifecycle rules by navigating to **Bucket > Settings > Lifecycle Rules**. From here, you can add new rules, edit existing ones, toggle them ON/OFF, or delete them.

> **INFO** Lifecycle rules run once daily on the storage cluster. Any changes you make to rules take effect within 24–48 hours and will apply to all existing objects that already match the criteria. *** ## Types of Lifecycle Rules When creating a new rule, you can choose one or more actions to automate bucket cleanup: ### 1. Expire Objects This rule hides the current version of an object behind a delete marker after it reaches a set age (e.g., 30 days). * **If Versioning is OFF:** The object is deleted permanently after the set time. * **If Versioning is ON:** The object is not permanently deleted, but a delete marker is created, hiding the current version. To free up actual storage space on a versioned bucket, use the **Clear Old Versions** rule instead.

### 2. Clear Old Versions > **Note:** This rule is only available if **Bucket Versioning is Enabled**. If versioning is off, this option will not appear. This is the only action that frees up space on a versioned bucket. It permanently deletes superseded (non-current) versions after a set age. * **Keep Newest Versions (Optional):** You can optionally choose to retain a specific number of the most recent versions. For example, if you set the rule to clear versions after **10 days** but keep the newest **3 versions**, Zata will delete all versions older than 10 days *except* for the 3 most recent ones, ensuring you always have recent backups. * *Note: The "Keep Newest Versions" feature is currently supported in the **Mumbai** region, but is not supported in the **Indore** region.*

### 3. Tidy Delete Markers > **Note:** This rule is only available if **Bucket Versioning is Enabled**. If versioning is off, this option will not appear. This rule automatically cleans up expired object delete markers. If an object has only one version remaining and that version is a delete marker, this rule will permanently remove the delete marker, completely tidying up the object from the bucket. * Note: This option is not available in the same rule as "Expire Objects".

### 4. Discard Unfinished Uploads Sometimes, multipart uploads are interrupted (e.g., due to network failure) and never completed, leaving unused data taking up storage space. This rule automatically frees space held by these interrupted uploads after a specified number of days (e.g., after 7 days).

*** ## Multiple Rules and Management You can also select multiple lifecycle rules to run simultaneously on your bucket.

Once a rule is created, you can disable, edit, and delete the lifecycle rule at any time directly from the settings.

# Access Control (ACL) Decide who can see your file list, who can download your files and who can upload Access Control decides **who can see, download and change the things you store in Zata.ai**. There are two separate settings, and each one does a different job: * **Bucket ACL** — can people see the **list of files** in your bucket, and can they **upload** to it? * **Object ACL** — can people **download** a particular file? You set them in two different places, and changing one never changes the other. > **INFO** Think of a bucket as a folder. The bucket setting decides whether people can look inside the folder and read the file names, and whether they can put new things in. The object setting decides whether they can actually open a file. *** ## The one rule to remember **Making a bucket public does not make your files downloadable.** Someone can see that a file called `invoice-2026.pdf` exists and how big it is, but the download is refused until you make that file public too. **Making a file public does not show people the rest of your bucket.** They can open the file you shared, and nothing else. So if you want visitors to browse your files *and* download them, you have to turn on both settings. *** ## Where to find each setting | Setting | Where you change it | The question it answers | | ---------- | ------------------------------------------------------------- | -------------------------------------------------- | | Bucket ACL | **Bucket > Bucket Settings > Access Control** | Who can see the list of files, and who can upload? | | Object ACL | **Bucket Details > Actions (⋮) > Make public / Make private** | Who can download this one file? | Each one has its own page: * [**Bucket ACL**](/manage/bucket/access-control/bucket-acl) — set your bucket to Private, Public read, Authenticated User, or one of the two write settings. * [**Object ACL**](/manage/bucket/access-control/object-acl) — make a single file public or private, and copy its link. *** ## Your choices **For a bucket**, you pick one of five. The first three are read-only; the last two also let other people upload. | Option | Who can see the file list | Who can upload, overwrite and delete | | ----------------------------------- | --------------------------------------------------------------------------- | --------------------------------------- | | **Private** | Only you. This is the default. | Only you | | **Public read** | Anyone on the internet, with no sign-in | Only you | | **Authenticated User** | Anyone signed in to *any* Zata.ai account — not only people in your account | Only you | | **Public read + write** | Anyone on the internet | Anyone on the internet | | **Authenticated User read + write** | Anyone signed in to any Zata.ai account | Anyone signed in to any Zata.ai account | **For a file**, you pick one of two: | Option | Who can download it | | ----------- | -------------------------------------------------------------- | | **Private** | Only you. This is the default for every upload. | | **Public** | Anyone with the link, with no sign-in. The link never expires. | > **IMPORTANT** The two write settings let other people **overwrite and permanently delete** your files, not just add new ones — upload and delete are a single S3 permission. Read [Write access](/manage/bucket/access-control/bucket-acl#write-access) before you turn either one on. *** ## What a visitor can actually do Here is what someone **with no Zata.ai account** can do, for each combination of the read-only settings: | Bucket setting | File setting | Can they see the file list? | Can they download the file? | | ------------------ | ------------ | --------------------------- | --------------------------- | | Private | Private | No | No | | Private | Public | No | Yes, if they have the link | | Public read | Private | Yes | No | | Public read | Public | Yes | Yes | | Authenticated User | Private | No | No | | Authenticated User | Public | No | Yes, if they have the link | With **Authenticated User**, visitors cannot see the list — but anyone signed in to a Zata.ai account can. The two write settings behave like their read-only versions in this table, and add the ability to upload, overwrite and delete. *** ## When ACL is not the right tool An ACL is all-or-nothing: it opens your bucket to *everyone* in a group, and you cannot pick individual people or folders. When you need that kind of control, use one of these instead: | What you want to do | Use this | | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | Share one file with someone for a limited time | [Presigned URL](https://docs.zata.ai/manage/bucket/storing-objects-in-a-bucket/sharing-an-object-using-presigned-url) — it expires on its own | | Give a colleague ongoing access you control | [Subuser](https://docs.zata.ai/subusers/create-a-subuser) with a [policy](https://docs.zata.ai/subusers/create-a-subuser/policies) | | Let a specific person upload, without opening the bucket to everyone | [Subuser](https://docs.zata.ai/subusers/create-a-subuser) with a write policy | | Share only one folder, not the whole bucket | [Bucket Policy](https://docs.zata.ai/manage/bucket/bucket-policy-configuration) | *** ## Good to know > **IMPORTANT** A public file list shows your file names to everyone. File names often contain customer names, invoice numbers or project names, so treat the list itself as information worth protecting — even when the files stay private. * Both browsing and downloading count towards your egress usage. See [Ingress and Egress Policy](https://docs.zata.ai/account/ingress-and-egress-policy). * All public access stops working if your account is suspended. * You can switch any of these settings back at any time — but switching off write access does not undo anything that was already uploaded or deleted. * A bucket policy can block public access even when the ACL allows it. If a setting seems to have no effect, see [ACL and bucket policies](#acl-and-bucket-policies) below. *** ## ACL and bucket policies Zata.ai checks the ACL **and** your bucket policies. If a policy says no, the answer is no — a policy that blocks access always wins over an ACL that allows it. The Access Control section repeats this on screen: > **NOTE** The Public Access toggle above writes a bucket policy — an explicit Deny there overrides this. So if you set a bucket to **Public read** and nothing changes, check the **Security & Access** section of Bucket Settings and the **Policies** page for a rule that is blocking it. *** ## If you use the S3 API Zata.ai follows the standard S3 ACL model, so the dashboard options match standard S3 permissions: | Dashboard option | S3 canned ACL | Who it grants access to | | ------------------------------- | -------------------- | ---------------------------------------------------------------------- | | Private | `private` | The owner only | | Public read | `public-read` | READ for the `AllUsers` group — everyone | | Authenticated User | `authenticated-read` | READ for the `AuthenticatedUsers` group — every signed-in Zata.ai user | | Public read + write | `public-read-write` | READ and WRITE for the `AllUsers` group | | Authenticated User read + write | *no canned name* | READ and WRITE granted explicitly to the `AuthenticatedUsers` group | In S3, "read" means different things depending on what the ACL is attached to: * On a **bucket**, read means *list the objects*. * On an **object**, read means *download the contents*. Same permission name, two different results. That is the reason the two settings have to be applied separately. WRITE has no such split — it exists only on a bucket, and it covers adding, replacing and deleting objects together. That is why Zata.ai cannot offer an upload-only setting. # Bucket ACL Set who can see your file list and who can upload to your bucket The Bucket ACL controls two things: * **Who can see the list of files** in your bucket — the file names, their sizes and when they were last changed. * **Who can upload, overwrite and delete** files in your bucket. It does **not** control who can download your files. That is set on each file separately, on the [Object ACL](/manage/bucket/access-control/object-acl) page. To change it, open your bucket, click **Bucket Settings**, and open the **Access Control** section.

Access Control section in Bucket Settings

*** ## The five settings Your bucket uses **one** setting at a time. Three of them are read-only. The other two also let other people upload. | Setting | Who can see the file list | Who can upload, overwrite and delete | | ----------------------------------- | -------------------------- | ------------------------------------ | | **Private** | Only you | Only you | | **Public read** | Anyone on the internet | Only you | | **Authenticated User** | Any signed-in Zata.ai user | Only you | | **Public read + write** | Anyone on the internet | Anyone on the internet | | **Authenticated User read + write** | Any signed-in Zata.ai user | Any signed-in Zata.ai user | The three read-only settings appear as cards at the top of the section. The two write settings are inside **ALLOW OTHERS TO UPLOAD** just below them. Whichever setting you are using is marked **Active**, and its button reads **Current setting**. The others have an **Apply** button. > **INFO** These five settings are alternatives, not layers. When you turn on a write setting, it replaces your read setting — which is why the cards at the top stop showing **Active** once **Public read + write** or **Authenticated User read + write** is in use. *** ## Read-only settings ### Private *Only you can access this bucket.* Every new bucket starts here. Nobody else can see what is inside, and nobody else can upload. You can still share individual files while the bucket stays private — either by making a file public, or with a [presigned URL](https://docs.zata.ai/manage/bucket/storing-objects-in-a-bucket/sharing-an-object-using-presigned-url). **Choose this** unless you have a specific reason not to. ### Public read *Anyone on the internet can see the list of files. Downloading a file still requires that file to be public.* Anyone can open your bucket URL and read the file names, with no sign-in. Downloads are still blocked until you make each file public, and nobody else can upload. **Choose this** when you want visitors to browse a set of files you are publishing on purpose. ### Authenticated User *Any signed-in Zata user can list this bucket — not just people in your account.* This one is easy to misread. It does **not** mean "people in my company". It means **every Zata.ai account in existence**, including strangers who signed up on their own. **Do not choose this** to share with your team. Create a [subuser](https://docs.zata.ai/subusers/create-a-subuser) and give it a policy instead — that way you decide exactly who gets in. *** ## Setting a bucket to Public read 1. In **Bucket Settings > Access Control**, click **Apply** on the **Public read** card.

2. A box appears asking **Allow anyone to list this bucket?**. It shows the bucket name and explains what will change. Read it, then click **Set to Public read**.

Allow anyone to list this bucket confirmation

3. The **Public read** card is now marked **Active** and a message confirms *Bucket access set to "Public read"*. A new **PUBLIC BUCKET URL** field appears, with buttons to copy the link or open it in a new tab.

Public read active with public bucket URL

To undo this, click **Apply** on the **Private** card. ### Your public bucket URL The link looks like this: ``` https://// ``` Use the service URL for the region your bucket is in: | Region | Public bucket URL | | ----------------------- | -------------------------------------- | | Central India (Indore) | `https://idr01.zata.ai//` | | Southern India (Mumbai) | `https://bom01.zata.ai//` | The `kriswebsite` bucket above is in Mumbai, so its link is `https://bom01.zata.ai/kriswebsite/`. Opening it shows the file list. For the full list of regions, see [Service URLs for Zata.ai S3](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). *** ## Setting a bucket to Authenticated User 1. In **Bucket Settings > Access Control**, click **Apply** on the **Authenticated User** card.

2. A box appears asking **Allow any Zata account to read?**. It warns you that this includes people outside your organisation, and suggests subusers as the safer option. Click **Set to Authenticated User** if you are sure.

Allow any Zata account to read confirmation

3. The **Authenticated User** card is now marked **Active** and a message confirms *Bucket access set to "Authenticated User"*.

There is no public bucket URL for this option. Visitors without an account still get turned away — only a signed-in Zata.ai user can see the list. *** ## Write access Everything above is read-only. If you want other people to **put files into** your bucket, open the **ALLOW OTHERS TO UPLOAD** row underneath the three cards.

Inside you will find a **Write access** status line and the two write settings.

**Write access** shows whether anyone else can write to the bucket at the moment: * **Off** — *Only you can add, replace or delete objects in this bucket.* This is the default. * **On** — other people can write to it right now, and the line tells you who. The two settings you can apply are: | Setting | Who can upload, overwrite and delete | | ----------------------------------- | ----------------------------------------------------------------------- | | **Public read + write** | Anyone on the internet. *You are billed for whatever they store.* | | **Authenticated User read + write** | Any signed-in Zata.ai user, including people outside your organisation. | Each one also grants the matching read access, so those visitors can list the bucket as well as write to it. ### Before you turn this on > **IMPORTANT** Upload, overwrite and delete are a **single S3 permission**. There is no upload-only option. Anyone you allow to add files can also replace and permanently delete the files you already have. The dashboard makes the same point when you apply either setting: > **NOTE** Upload, overwrite and delete are a single S3 permission — there is no upload-only option. Turn on versioning first if you need to recover a file someone overwrites. So if the files in this bucket matter, turn on [Versioning](https://docs.zata.ai/manage/bucket/create-bucket/bucket-settings) first. With versioning on, an overwrite creates a new version instead of destroying the old one, so you can go back. Two more things to know before you decide: * **You pay for what other people do.** Whatever they upload is stored on your account, and their downloads generate egress billed to you. See [Ingress and Egress Policy](https://docs.zata.ai/account/ingress-and-egress-policy). * **Turning it off later is not a rewind.** Setting the bucket back to Private stops further access, but it does not undo anything that was already uploaded or deleted. *** ## Setting a bucket to Public read + write This is the most open setting Zata.ai offers. Anyone who knows the bucket name can write to it, with no account and no sign-in. 1. Expand **ALLOW OTHERS TO UPLOAD** and click **Apply** on the **Public read + write** row.

2. A box appears asking **Allow anyone on the internet to write?**. It names the bucket and its region, and lists exactly what strangers will be able to do: * Upload files of any size or type * Overwrite the files you already have * Permanently delete your files * Store data and generate egress that is billed to you Because of that, the dashboard asks you to **type the bucket name to confirm**. The **Allow write access** button stays greyed out until you do.

Allow anyone on the internet to write confirmation

3. Type the bucket name and click **Allow write access**. The **ALLOW OTHERS TO UPLOAD** row now shows a yellow **On** badge, **Write access** reads *On — Anyone on the internet can upload, overwrite and delete files in this bucket right now*, and **Public read + write** is marked **Active**. A message confirms *Bucket access set to "Public read + write"*.

Notice that the three cards at the top no longer show **Active** — the write setting has replaced your read setting. A **PUBLIC BUCKET URL** row appears as well, because this setting includes public read. > **IMPORTANT** Only use this for a bucket you would not mind losing. A publicly writable bucket can be filled with other people's data, used to host content you did not choose, or emptied by anyone who finds the name. If you need a drop-box where people send you files, use a [subuser](https://docs.zata.ai/subusers/create-a-subuser) with a write policy instead, so you know who is uploading. *** ## Setting a bucket to Authenticated User read + write This is narrower than Public read + write, because a visitor has to be signed in to a Zata.ai account. It still covers **every** Zata.ai account, though — not only your own team. 1. Expand **ALLOW OTHERS TO UPLOAD** and click **Apply** on the **Authenticated User read + write** row.

Apply on the Authenticated User read plus write row

2. A box appears asking **Allow any Zata account to write?**. It spells out that this includes people outside your organisation, lists the same four abilities, and asks you to type the bucket name to confirm.

Allow any Zata account to write confirmation

3. Type the bucket name and click **Allow write access**. **Write access** now reads *On — Any signed-in Zata user can upload, overwrite and delete files in this bucket right now*, and **Authenticated User read + write** is marked **Active**. A message confirms *Bucket access set to "Authenticated User read + write"*.

Authenticated User read plus write active

There is no public bucket URL here, because anonymous visitors are still turned away. *** ## Turning write access off 1. In the **ALLOW OTHERS TO UPLOAD** section, click **Make private** on the **Write access** row.

Make private button on the Write access row

2. **Write access** goes back to **Off**, the **Private** card is marked **Active**, and a message confirms *Bucket access set to "Private"*.

Write access off and bucket private again

**Make private** returns the bucket to Private in one step — it switches off write access and public listing together. If you wanted to keep the file list public, apply **Public read** again afterwards. Remember that this stops future access only. Files other people already uploaded stay in your bucket, and files they deleted are gone. *** ## Good to know > **IMPORTANT** A public file list shows your file names to everyone. File names often contain customer names, invoice numbers or project names, so treat the list itself as information worth protecting — even when the files stay private. * **Changing this setting never changes your files.** A file you made public earlier stays downloadable, even after you set the bucket back to Private. To stop that, make the file private. * **A bucket policy can block public access.** If a setting seems to do nothing, check the **Security & Access** section and the **Policies** page. See [ACL and bucket policies](/manage/bucket/access-control#acl-and-bucket-policies). * Browsing and downloading both count towards your egress usage. * Public access stops working if your account is suspended. # Object ACL Make a single file public or private and copy its public link The Object ACL decides **who can download one particular file**. You set it on each file, from the file list. This is the setting that actually puts a file on the internet. The [Bucket ACL](/manage/bucket/access-control/bucket-acl) only controls whether people can see your file names. Every file has two states: | State | What it means | | ----------- | --------------------------------------------------------------------------------------------- | | **Private** | Only you can download it. Every file starts out private. | | **Public** | Anyone with the link can view and download it. No sign-in needed, and the link never expires. | > **INFO** Making one file public does not expose the rest of your bucket. Someone with the link gets that one file and nothing else — unless you have also set the bucket to Public read, which lets them browse the file names as well. *** ## Making a file public 1. Open your bucket to see the **Bucket Details** page. Find your file in the list, click the **Actions (⋮)** menu on its row, and choose **Make public**.

2. A box appears asking **Make this file public?**. It tells you that anyone with the link can view and download the file, that no sign-in is needed, and that the link does not expire. Click **Make public**.

3. A small green globe now appears next to the file name. This is how you spot which files in a bucket are public.

Green globe icon marking a public object

*** ## Getting the link Once a file is public, its **Actions (⋮)** menu changes. **Make public** is replaced by two new items: **Copy public link** and **Make private**. Click **Copy public link** to copy the link to your clipboard.

Copy public link in the object actions menu

The link looks like this: ``` https://// ``` For `index.html` in the `kriswebsite` bucket in Mumbai, that is `https://bom01.zata.ai/kriswebsite/index.html`. Paste it into any browser and the file opens straight away, with no sign-in.

Use the service URL for your bucket's region — `idr01.zata.ai` for Central India, `bom01.zata.ai` for Southern India. If your file sits inside a folder, include the folder name in the link: ``` https://bom01.zata.ai/kriswebsite/assets/logo.png ``` *** ## Making a file private again 1. Open the **Actions (⋮)** menu for the file and choose **Make private**.

2. A box appears asking **Make this file private?**. It warns you that the link stops working straight away, and that anyone who saved it will now get an access-denied error. Click **Make private**.

3. The green globe disappears. The file is private again.

This is the only way to switch off a public link. Because the link never expires by itself, **Make private** is what you use if you shared a file by mistake. *** ## Good to know > **IMPORTANT** A public link works forever until you switch it off. It can be forwarded to other people, found by search engines, or saved by anyone who opens it. If you only want to share a file for a short while, use a [presigned URL](https://docs.zata.ai/manage/bucket/storing-objects-in-a-bucket/sharing-an-object-using-presigned-url) instead — it expires on its own. * **You set this one file at a time.** There is no single switch that makes every file in a bucket public. * **New uploads are always private**, even in a bucket set to Public read. Files you add later have to be made public one by one. * **Making a file private does not delete it.** Its versions and any [Object Lock](https://docs.zata.ai/manage/bucket/object-lock) protection stay exactly as they were. * Downloads count towards your egress usage, and the link stops working if your account is suspended. # Preview Manager **Notice: Egress Usage Applies** - Browsing or previewing files through the File Manager will count against your included egress quota. This includes actions such as viewing, downloading, or streaming files. If your egress usage exceeds your plan limit, services may be temporarily restricted as per your account terms. The Preview Manager is used to preview and manage media files, images, and documents stored inside your buckets without downloading them. To access the Preview Manager: 1. Log in to your **Zata.ai Dashboard**. 2. From the left sidebar menu, go to:\ **Manage → Preview Manager**. ### Buckets Overview Once you open the Preview Manager, all your available buckets are displayed.\ In your case, the buckets visible are: * **preparcona** * **prertest** Each bucket shows basic information such as: * Bucket name * Region (e.g., Indore or Mumbai) * Storage used * Number of objects These buckets act as containers where your files and objects are stored.

### Previewing Files Inside a Bucket 📸 *Screenshot: Bucket opened in Preview Manager* To preview files: 1. Click on any bucket (for example: **prertest**). 2. The Preview Manager will display all objects stored inside that bucket.

### Previewing an Object 3. Click on any file to open its preview. 4. The file will open in a preview window without downloading.

Supported preview formats include: * Images: `.jpg`, `.png`, `.gif` * Videos: `.mp4` * Documents: `.pdf` * Other supported media formats This feature helps you: * Quickly verify file content * Check uploaded data * Avoid unnecessary downloads # Access Keys An Access Key is used to authenticate and make secure programmatic API calls to the Zata.ai S3 service. It allows applications and S3-compatible tools to interact with object storage for operations such as uploading, downloading, listing, and managing files. Each access key consists of two parts: * **Access Key ID** – Acts as a public identifier (similar to a username). * **Secret Access Key** – Acts as a private credential (similar to a password). Both are required to authenticate requests to the Zata.ai API. Access keys are used to make secure REST or Query protocol requests to the Zata.ai service. When configuring any S3-compatible client such as S3 Browser or Cyberduck, you must enter the Access Key ID and Secret Access Key in the respective fields. The Zata.ai S3 endpoints are: | Region | Endpoint | | -------------- | ------------- | | Central India | idr01.zata.ai | | Southern India | bom01.zata.ai | For security reasons, the Secret Access Key should never be shared with anyone. It is recommended to store access keys securely and rotate them periodically as a best practice. Access keys provide a standardized and secure way to connect applications and tools with Zata.ai Object Storage. # Creating a New Access Key You can create only five access keys. * Log in to the **Zata.ai Panel**. * From the left-side menu, click on **Access Keys**. The Access Keys page displays all your existing keys across both regions (Indore and Mumbai), along with summary cards for **Total Keys**, **Root Keys**, and **Sub-user Keys**.

* Click on **Generate Key**. You will see the **Create Access Key** dialog with two options: * **Root User** – Full administrative access * **Sub User** – Limited user-level access Select the appropriate option based on your requirement and choose your **Region** (Indore or Mumbai) from the dropdown. **Example: Generating a Root Key for Indore region**

**Example: Generating a Root Key for Mumbai region**

After selecting the user type and region, click **Continue**. You will see an **Important Note** reminding you to download your key file immediately. * Click **Generate Key** to create the access key.

### Generating a Sub-user Key To generate a key for a **Sub-user**, select the Sub User option in the Create Access Key dialog.

* Choose the required sub-user from the list (for example: `accessuser`). * Click on **Generate Key**.

### After Key Generation * As soon as you click **Generate Key**, a `.txt` file is automatically downloaded to your local system. * Open the downloaded `.txt` file. It will contain: * Access Key ID * Secret Access Key * Save this file in a secure location on your system. * Use these keys to configure: * S3 Browser * Cyberduck * Any application using the Zata.ai S3 API The newly generated key will appear in the Access Keys list with its associated region.

Access Keys list with all keys across both regions

If the downloaded file is lost, you must delete the existing access key and generate a new one, as the Secret Access Key cannot be recovered. # Service URLs for Zata.ai S3 This page provides the service endpoints required to connect to Zata.ai Object Storage using S3-compatible tools and applications. Each region has its own unique service URL, which must be used while configuring clients such as S3 Browser, Cyberduck, AWS CLI, or any application using the S3 API. | Region | Service URL | Region Code | | -------------- | ----------------------- | ------------ | | Central India | | CentralIndia | | Southern India | | SouthIndia | The **Service URL** is the endpoint through which all S3 API requests are sent to Zata.ai. When configuring any S3-compatible client, this URL must be provided as the S3 endpoint. The **Region Code** is used for identifying the storage region while creating buckets or configuring applications that require region-specific settings. Use this service URL along with your **Access Key ID** and **Secret Access Key** to establish a secure connection between your application and Zata.ai S3 Object Storage. # Migration The Migration feature enables seamless transfer of data from external storage platforms to Zata.ai S3 storage. It is designed to simplify data movement, reduce manual effort, and ensure secure and efficient data handling. This module helps in centralizing data by allowing users to bring content from multiple sources into a single S3-compatible storage environment. It supports reliable data transfer while maintaining data integrity and accessibility. The Migration feature is built to be scalable and extensible, allowing additional storage sources and migration options to be integrated in the future as needed. This makes it suitable for growing data requirements and evolving storage ecosystems. # Migrate from AWS S3 storage to Zata.ai S3 storage **Prerequisites** * Select any Linux operating system to perform the migration process. * In this setup, we have chosen **Ubuntu 22.04** as the operating system. * Click on the provided link to **Launch the Instance** [Instance](https://docs.neevcloud.com/neevcloud-products/computes/getting-started-launch-vms). **AWS Setup** For AWS configuration: * Log in to the **AWS Management Console**. * This console will be used to create and manage the S3 bucket and generate access credentials required for migration.

**Create a Bucket in AWS S3** * After logging in to the AWS Management Console, search for **S3** in the services search bar. * Open the **S3** service and click on **Create bucket**. * Provide the required details such as bucket name and region, and complete the bucket creation process.

**Set Bucket Policy and Permissions** * After creating the bucket, apply the required bucket permissions and bucket policy. * Click on the created bucket, then navigate to **Permissions → Bucket Policy → Edit**. * Update the policy by modifying the bucket name, user name, and user account ID according to your requirements before saving it. When applying a bucket policy, ensure you customize the values based on your requirements. Do not copy this policy directly.

**Create Access and Secret Key** * Navigate to the **IAM** service from the AWS Management Console. * Go to the **Users** section and select an existing user to create an access and secret key. * If the user does not exist, create a new user and assign **AdministratorAccess** permissions.

Verify that the selected user has sufficient permissions to access and manage the S3 buckets. Then, navigate to the **Security Credentials** section to generate the Access Key ID and Secret Access Key.

Now create the security credentials to click on the security credentials to create the access key.

Before clicking on "Done," first copy the access and secret keys to your notepad.

After performing these processes in AWS, configure the Zata.ai settings. **Setup Zata.ai** For Zata.ai configuration: * Open the Zata.ai login page and sign in to your account [login page](https://auth.zata.ai/realms/zata/protocol/openid-connect/auth?client_id=zatacloud_client\&redirect_uri=https%3A%2F%2Fmy.zata.ai%2F\&state=dd2b5305-f7f5-4922-8639-4b0c62060c2f\&response_mode=fragment\&response_type=code\&scope=openid\&nonce=646d8811-0870-469c-9045-9e13d0fdd1b3\&code_challenge=wRG6I1qb9wdmY4unvHhPYaYq5WWM-801w72AYyLi8xY\&code_challenge_method=S256). * Create a bucket by following the *Zata Bucket Creation Guide* [Bucket Creation Guide](https://docs.zata.ai/manage/bucket/create-bucket) * Generate the Access Key ID and Secret Access Key by following the *Access Keys Guide* [Access Keys Guid](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key)e * Refer to the Zata.ai documentation for more detailed information and features [zata.ai](https://zata.ai/) **Guide to Move Data from AWS to Zata.ai** Ubuntu 22.04 is used as an intermediary system to facilitate the data migration from AWS S3 to Zata.ai S3. This system acts as a bridge between both storage platforms during the transfer process. For the first process (AWS side setup): * Update and upgrade the Ubuntu system to ensure all packages are up to date. ``` sudo apt-get update -y sudo apt-get upgrade -y ``` For migrating data from AWS to Zata.ai, use **rclone** ### Install the configure the rclone Install and configure the rclone. ``` sudo apt-get install rclone -y ``` * To migrate data, rclone must be configured for both AWS and Zata.ai. * First, configure rclone for AWS, and then configure it for Zata.ai. * Run the following command to start the rclone configuration: ``` sudo rclone config ``` * When the rclone configuration starts, choose **`n`** to create a new remote. * Enter **AWS** as the name of the remote.

For the storage type, choose option **`4`** to select the AWS S3–compliant storage provider.

Select your S3 provider by choosing option **`1`** for **AWS S3**.

* When prompted for `env_auth`, select **false** (press Enter to use the default value). * This option is used only if credentials are taken from environment variables or EC2/ECS metadata. * Since the Access Key ID and Secret Access Key were already created in the AWS section, manual entry will be used. * Enter the **AWS Access Key ID** and **AWS Secret Access Key** when prompted.

* Set the endpoint according to your AWS region. * In our case, we are using the **Mumbai region**, so the endpoint is: ``` s3.ap-south-1.amazonaws.com ``` * When asked for the region, choose option **`17`** for **Asia Pacific (Mumbai)**.

* When prompted for the S3 API endpoint, enter the following value: ``` s3.ap-south-1.amazonaws.com ``` * This sets the S3 API endpoint for the Mumbai (Asia Pacific) region.

* Press **Enter** to accept all default values. * When prompted for **Storage Class**, change the value and choose option **`2`**.

* For the ACL option, choose **`4`**. * This setting applies only when creating buckets. * Keep all remaining options as default by pressing **Enter** until the configuration is completed.

This is the remote configuration completed after following these steps:

### Second process for Zata.ai **Configure rclone for Zata.ai** * Choose **`n`** to create a new remote. * Set the remote name as **zata**. * Choose option **`4`** for **S3 Compliant Storage Provider**. * Choose option **`13`** for **S3 Compatible Provider**. * Set `env_auth` to **false** to use manual credentials. * Enter the **Zata Access Key ID** and **Zata Secret Access Key** (refer to the Access Keys Guide).[Access Keys Guid](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key)e * Set the endpoint as per your region: ``` idr01.zata.ai (for Central India / Indore) bom01.zata.ai (for Southern India / Mumbai) ```

Ensure you have created buckets in both **AWS** and Zata.ai before running these commands. **Copy Data from AWS S3 to Zata.ai S3** * After completing the rclone configuration for both AWS and Zata.ai, you can start the data transfer. * Use the following command to copy data from the AWS bucket to the Zata.ai bucket: ```bash rclone copy AWS: zata: --s3-region ap-south-1 --progress ``` * Replace `` with your AWS S3 bucket name. * Replace `` with your Zata.ai bucket name. * The `--progress` option shows real-time transfer status. * This command securely copies all objects from AWS S3 to Zata.ai S3.

After completing the data transfer, return to both the AWS S3 console and the Zata.ai dashboard to verify the status of the buckets and confirm that all data has been successfully copied. # Migrate from Wasabi S3 storage to Zata.ai S3 storage Wasabi Storage is a cloud-based object storage service that provides high performance, scalability, and cost-effective storage solutions. It is commonly used for backup, disaster recovery, and archiving purposes. **Prerequisites** * Select any Linux operating system to perform this process. * In this setup, **Ubuntu 22.04** is used as the operating system. * Launch the Ubuntu [Instance](https://docs.neevcloud.com/neevcloud-products/computes/getting-started-launch-vms). **Setup Wasabi** * Open the Wasabi login page. * Log in to the **Wasabi Console** to start the configuration [Wasabi Console.](https://console.wasabisys.com/login)

**Create a Bucket in Wasabi** * After logging in to the Wasabi Console, navigate to the **Buckets** section. * Click on **Create Bucket** and complete the bucket creation process by providing the required details.

**Create Access & Secret Key** * Navigate to the **Access Keys** section in the Wasabi Console. * Generate a new **Access Key ID** and **Secret Access Key**, and store them securely for later use.

**Setup Zata.ai** For Zata.ai configuration: * Open the Zata.ai login page and sign in to your account [login page](https://auth.zata.ai/realms/zata/protocol/openid-connect/auth?client_id=zatacloud_client\&redirect_uri=https%3A%2F%2Fmy.zata.ai%2F\&state=dd2b5305-f7f5-4922-8639-4b0c62060c2f\&response_mode=fragment\&response_type=code\&scope=openid\&nonce=646d8811-0870-469c-9045-9e13d0fdd1b3\&code_challenge=wRG6I1qb9wdmY4unvHhPYaYq5WWM-801w72AYyLi8xY\&code_challenge_method=S256). * Create a bucket by following the *Zata Bucket Creation Guide* [Bucket Creation Guide](https://docs.zata.ai/manage/bucket/create-bucket) * Generate the Access Key ID and Secret Access Key by following the *Access Keys Guide* [Access Keys Guid](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key)e * Refer to the Zata.ai documentation for more detailed information and features [zata.ai](https://zata.ai/) **Guide to Move Data from Wasabi to Zata.ai** Ubuntu 22.04 is used as an intermediary system to facilitate the data migration from Wasabi S3 to Zata.ai S3. **First Process (Wasabi Side Setup)** * Update and upgrade the Ubuntu system to ensure all packages are up to date. ``` sudo apt-get update -y sudo apt-get upgrade -y ``` For migrating data from Wasabi to Zata.ai, use **rclone.** ### Install and configure the **rclone.** ``` sudo apt-get install rclone -y ``` **Configure rclone for Wasabi and Zata.ai** To migrate data, rclone must be configured for both Wasabi and Zata.ai. First configure rclone for Wasabi, and then repeat the same process for Zata.ai.\ \ Run the following command to start the rclone configuration: ``` sudo rclone config ``` When the rclone configuration starts, choose **`n`** to create a new remote.\ Enter **Wasabi** as the name of the remote.

Select **`4`** as the storage type to choose an S3-compatible storage provider. Note: The option number may vary depending on the rclone version

Choose your S3 Provider to choose '12' for Wasabi object storage, these numbers are very dependent on the rclone versions.

* `env_auth: true` is used to fetch credentials from environment variables. * This option applies only when `access_key_id` and `secret_access_key` are left blank. * Setting it to **true** means credentials will be taken automatically from the system environment. * Setting it to **false** means credentials will be entered manually.

Access & Secret key - We have created the above in the Wasabi section.

* Enter the region to connect to your S3 service. * If you are using an S3-compatible provider (like Wasabi) and no region is required, leave it blank. * Press **Enter** to use the default value

Enter the S3 API endpoint for Wasabi (required for S3-compatible storage) and press Enter to continue.

Note that this ACL is applied when server-side copying objects as S3

Note that this ACL is applied only when creating buckets. After completing these processes, simply press Enter at each step

This is the remote configuration completed after following these steps:

Make sure to choose a number these values vary depending on the rclone version. **Second Process for Zata.ai** * Repeat the same rclone configuration process for Zata.ai. * Choose **`n`** to create a new remote. * Set the remote name as **zata**. * Choose **`4`** for **S3 Compliant Storage Provider**. * Choose **`13`** for **S3 Compatible Provider**. * Set `env_auth` to **true**. * Enter the **Zata Access Key ID** and **Secret Access Key** (refer to the Access Keys Guide). * Set the endpoint as per your region: ``` idr01.zata.ai (for Central India / Indore) bom01.zata.ai (for Southern India / Mumbai) ```

Ensure you have created buckets in both **Wasabi** and **Zata.ai** before running these commands. After completing the rclone configuration for both Wasabi and Zata.ai, you can start the data transfer process. Use the following command to copy data from the Wasabi bucket to the Zata.ai bucket: ```bash rclone copy Wasabi: Zata: --s3-region ap-northeast-1 --progress ``` Replace `` with your Wasabi bucket name and `` with your Zata.ai bucket name. The `--progress` option displays the real-time status of the data transfer.

After the migration is completed, return to both the **Wasabi Console** and the **Zata.ai Dashboard** to verify the bucket status and confirm that all data has been transferred successfully. # Migrate from Google Drive to Zata.ai S3 storage To migrate data from Google Drive to Zata you have to use Rclone. The Rclone software package is a command-line tool which allows a variety of modes of operation for managing data in two or more locations. This article describes how to use Rclone to migrate data from Google Drive to Zata. For more information about Rclone, please visit [the Rclone project page](https://rclone.org/). **1. Prerequisites** * Active Zata.ai Account * Zata Bucket * Zata Endpoint, Access & Secret Key Pair * [Rclone Executable](https://rclone.org/downloads/) Version 1.63.1 **2. Configure Google Drive as a Remote Location** 2.1 Open your OS specific terminal and navigate to the folder location where the Rclone executable is stored. 2.2 Type in rclone config to create a new Remote ```powershell rclone config ``` 2.3 Type in/Select "n" for a new remote connection ```powershell ExplainNo remotes found, make a new one? n) New remote r) Rename remote c) Copy remote s) Set configuration password q) Quit config n/r/c/s/q> n ``` 2.4 Enter a name for your google drive remote connection Example : ``` Enter name for new remote. name> drive ``` 2.5 Type in/Select Google Drive ``` 1 / 1Fichier \ (fichier) 2 / Akamai NetStorage \ (netstorage) 3 / Alias for an existing remote \ (alias) 4 / Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Outscale, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, Selectel, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others \ (s3) 5 / Backblaze B2 \ (b2) 6 / Better checksums for other remotes \ (hasher) 7 / Box \ (box) 8 / Cache a remote \ (cache) 9 / Citrix Sharefile \ (sharefile) 10 / Cloudinary \ (cloudinary) 11 / Combine several remotes into one \ (combine) 12 / Compress a remote \ (compress) 13 / Dropbox \ (dropbox) 14 / Encrypt/Decrypt a remote \ (crypt) 15 / Enterprise File Fabric \ (filefabric) 16 / FTP \ (ftp) 17 / Files.com \ (filescom) 18 / Gofile \ (gofile) 19 / Google Cloud Storage (this is not Google Drive) \ (google cloud storage) 20 / Google Drive \ (drive) 21 / Google Photos \ (google photos) ``` 2.5 Leave Blank and Hit Enter ``` Option client_id. Google Application Client Id Setting your own is recommended. See https://rclone.org/drive/#making-your-own-client-id for how to create your own. If you leave this blank, it will use an internal key which is low performance. Enter a value. Press Enter to leave empty. client_id> ``` 2.6 Leave Blank and Hit Enter ``` Option client_secret. OAuth Client Secret. Leave blank normally. Enter a value. Press Enter to leave empty. client_secret> ``` 2.7 Choose 1 or your scope and hit enter ``` Option scope. Scope that rclone should use when requesting access from drive. Choose a number from below, or type in your own value. Press Enter to leave empty. 1 / Full access all files, excluding Application Data Folder. \ (drive) 2 / Read-only access to file metadata and file contents. \ (drive.readonly) / Access to files created by rclone only. 3 | These are visible in the drive website. | File authorization is revoked when the user deauthorizes the app. \ (drive.file) / Allows read and write access to the Application Data folder. 4 | This is not visible in the drive website. \ (drive.appfolder) / Allows read-only access to file metadata but 5 | does not allow any access to read or download file content. \ (drive.metadata.readonly) scope> 1 ``` 2.8 Leave Blank and Hit Enter ``` Option service_account_file. Service Account Credentials JSON file path. Leave blank normally. Needed only if you want use SA instead of interactive login. Leading `~` will be expanded in the file name as will environment variables such as `${RCLONE_CONFIG_DIR}`. Enter a value. Press Enter to leave empty. service_account_file> ``` 2.9 Type in/Select "n" for No ``` Edit advanced config? y) Yes n) No (default) y/n> n ``` 2.10 Type in "y" for Yes to authenticate to your google drive using a web browser ``` Use web browser to automatically authenticate rclone with remote? * Say Y if the machine running rclone has a web browser you can use * Say N if running rclone on a (remote) machine without web browser access If not sure try Y. If Y failed, try N. y) Yes (default) n) No y/n>y 2023/07/27 13:16:20 NOTICE: If your browser doesn't open automatically go to the following link: http://127.0.0.1:53682/auth?state=hy8ONFPQCykB30YldCCQfA 2023/07/27 13:16:20 NOTICE: Log in and authorize rclone for access 2023/07/27 13:16:20 NOTICE: Waiting for code... ``` 2.11 A web browser window will pop up allowing you to enter in your credentials for your Google Drive Account

2.12 After signing in you will get a Success Message and then you can go back to command prompt to continue with setup.

2.13 Type in/Select "n" for no in regards to configuring as a Shared Drive. ``` 2023/07/27 13:24:14 NOTICE: Got code Configure this as a Shared Drive (Team Drive)? y) Yes n) No (default) y/n> n ``` 2.14 Configuration of Google Drive is complete. Review the information for accuracy and then type in/select "y" for yes to save the configuration and you are done. ``` Configuration complete. Options: - type: drive - scope: drive - token: {"access_token":"ya29.a0AbVbYH7EgnFk1J2fKDtmXsqIlSff9lQnejKJweBLU9NteOyJtPxsqUTNAqMu-cJIuqwsgQOfO_SH7zbsKGoql0w4v0H3L80VDRsoK4U48LVXppsfgNb0-wJh3_YdAnTOcZQrqeLkaguSJAupy3IIhaCgYKAZQSARMSFQFWKvPlsfpcY6uxG-vsoPowhX3p-Q0163","token_type":"Bearer","refresh_token":"1//01c-s3KbSkfWzCgYIARAAGAESNwF-L9IrkIUDhEWLzb8MUJefx5INb8WAgj6tGm4QH7tvCQ-O3T-AnrztykMfFsv6KM0t9Inv7co","expiry":"2023-07-27T14:24:13.4851761-07:00"} - team_drive: Keep this "google drive" remote? y) Yes this is OK (default) e) Edit this remote d) Delete this remote y/e/d>y ``` **Step3. Configure Zata as a Remote Location** 3.1 Enter "n" for a new remote connection ``` e) Edit existing remote n) New remote d) Delete remote r) Rename remote c) Copy remote s) Set configuration password q) Quit config e/n/d/r/c/s/q> n ``` 3.2 Type in a name corresponding to Zata for your Remote location Example : ``` Enter name for new remote. name> zata ``` 3.3 Type in/select "4" or choose Amazon S3 compliant provider ``` Option Storage. Type of storage to configure. Choose a number from below, or type in your own value. 1 / 1Fichier \ (fichier) 2 / Akamai NetStorage \ (netstorage) 3 / Alias for an existing remote \ (alias) 4 / Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Outscale, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, Selectel, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others \ (s3) 5 / Backblaze B2 \ (b2) 6 / Better checksums for other remotes \ (hasher) ``` 3.4 Type in/select "34" or choose "Any other S3 compatible provider" from the list ``` 29 / Storj (S3 Compatible Gateway) \ (Storj) 30 / Synology C2 Object Storage \ (Synology) 31 / Tencent Cloud Object Storage (COS) \ (TencentCOS) 32 / Wasabi Object Storage \ (Wasabi) 33 / Qiniu Object Storage (Kodo) \ (Qiniu) 34 / Any other S3 compatible provider \ (Other) ``` 3.5 Choose Option 1 to type in your Zata Credentials in the following Steps ``` Option env_auth. Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars). Only applies if access_key_id and secret_access_key is blank. Choose a number from below, or type in your own boolean value (true or false). Press Enter for the default (false). 1 / Enter AWS credentials in the next step. \ (false) 2 / Get AWS credentials from the environment (env vars or IAM). \ (true) env_auth> 1 ``` 3.6 Type in your Zata Access Key ``` Option access_key_id. AWS Access Key ID. Leave blank for anonymous access or runtime credentials. Enter a value. Press Enter to leave empty. access_key_id> xxxxxxxxxxx ``` 3.7 Type if your Zata Secret Key ``` Option secret_access_key. AWS Secret Access Key (password). Leave blank for anonymous access or runtime credentials. Enter a value. Press Enter to leave empty. secret_access_key> xxxxxxxxxxxxxxxxxxx ``` 3.8 Choose Option 1 for your Region selection ``` Option region. Region to connect to. Leave blank if you are using an S3 clone and you don't have a region. Choose a number from below, or type in your own value. Press Enter to leave empty. / Use this if unsure. 1 | Will use v4 signatures and an empty region. \ () / Use this only if v4 signatures don't work. 2 | E.g. pre Jewel/v10 CEPH. \ (other-v2-signature) region> 1 ``` 3.9 Type in your endpoint for Zata where your bucket is located. ``` Option endpoint. Endpoint for S3 API. Required when using an S3 clone. Enter a value. Press Enter to leave empty. endpoint> https://idro1.zata.ai ``` 3.10 Leave Blank and Hit Enter ``` Option location_constraint. Location constraint - must be set to match the Region. Leave blank if not sure. Used when creating buckets only. Enter a value. Press Enter to leave empty. location_constraint> ``` 3.11 Choose Option 1 or the ACL option you wish to use. ``` Option acl. Canned ACL used when creating buckets and storing or copying objects. This ACL is used for creating objects and if bucket_acl isn't set, for creating buckets too. For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl Note that this ACL is applied when server-side copying objects as S3 doesn't copy the ACL from the source but rather writes a fresh one. If the acl is an empty string then no X-Amz-Acl: header is added and the default (private) will be used. Choose a number from below, or type in your own value. Press Enter to leave empty. / Owner gets FULL_CONTROL. 1 | No one else has access rights (default). \ (private) / Owner gets FULL_CONTROL. 2 | The AllUsers group gets READ access. \ (public-read) / Owner gets FULL_CONTROL. 3 | The AllUsers group gets READ and WRITE access. | Granting this on a bucket is generally not recommended. \ (public-read-write) / Owner gets FULL_CONTROL. 4 | The AuthenticatedUsers group gets READ access. \ (authenticated-read) / Object owner gets FULL_CONTROL. 5 | Bucket owner gets READ access. | If you specify this canned ACL when creating a bucket, Amazon S3 ignores it. \ (bucket-owner-read) / Both the object owner and the bucket owner get FULL_CONTROL over the object. 6 | If you specify this canned ACL when creating a bucket, Amazon S3 ignores it. \ (bucket-owner-full-control) acl> 1 ``` 3.12 Type in/Select "n" for No ``` Edit advanced config? y) Yes n) No (default) y/n> n ``` 3.13 Configuration of your Remote Location for Zata is now complete. Review the information for accuracy and type in/select "y" for yes and you are done. ``` Configuration complete. Options: - type: s3 - provider: Other - access_key_id: XXXXXXXXXXXXXX - secret_access_key: XXXXXXXXXXXXXXXXXXX - endpoint: https://idro1.zata.ai - acl: private Keep this "Zata" remote? y) Yes this is OK (default) e) Edit this remote d) Delete this remote y/e/d> y ``` 3.14 Type in/Select "q" to quit from the Remote Configuration and go back to the root level ``` e) Edit existing remote n) New remote d) Delete remote r) Rename remote c) Copy remote s) Set configuration password q) Quit config e/n/d/r/c/s/q> q c:\rclone-v1.63.1> ``` **Step4. Move Data to Zata** **4.1 Copy Data from Drive to Zata(Without Deleting Data from Google Drive)** If you just want to copy the data from Google Drive to Zata you have to use this command. ``` rclone move "drive": "Zata:bucket name" -P ``` Note : 1. All the variables to be written with ""(double quotes)"". 2. "drive" is just an example instead of drive you have to write name that you have given for google drive remote connection. 3. "Zata" is just an example instead of drive you have to write name that you have given for Zata remote connection. 4. "bucket name" is just an example instead of drive you have to write the name of the bucket in which you wish to copy your Google Drive data. **4.2 Copy Data from Drive to Zata(With Deleting Data from Google Drive)** If you just want to copy the data from Google Drive to Zata and also want to delete data from Google Drive, you have to use this command. ``` rclone move "drive": "Zata:bucket name" -P -v ``` Note : 1. All the variables to be written with ""(double quotes)"". 2. "drive" is just an example instead of drive you have to write name that you have given for google drive remote connnection. 3. "Zata" is just an example instead of drive you have to write name that you have given for Zata remote connnection. 4. "bucket name" is just an example instead of drive you have to write the name of the bucket in which you wish to copy your Google Drive data. # Subusers subuser Management page The **subuser Management** page provides a centralized view to manage all users and sub-users in Zata.ai. It allows administrators to create, monitor, and control user access to storage resources. From this section, you can view user details such as username, ARN, status, and assigned role, as well as manage permissions and delete users when required. This page helps ensure secure access control by assigning appropriate roles and permissions to each user. # Create a Subuser **Step 1: Open the Sub-user Management** You can create only three SubUsers. * Log in to the Zata.ai dashboard. * From the left sidebar, go to **Subusers → Subusers** * You will see the **Sub-user Management** page

**Step 2: Create a New Subuser** * Click on **Create Subuser** (top right button) A popup will open: **Create Subuser** **Required Fields** * Username: * Must be unique * Allowed characters: * Letters (a–z, A–Z) * Numbers (0–9) * Dot (.) * Underscore (\_) * Dash (-) * Length: **1–64 characters** * Email: * Enter a valid email address * Region: * Select the required region from dropdown (e.g., Indore or Mumbai) **Optional Field** * Description * Add any note (optional)

**Step 3: Create the Sub-user** * Click on **Create Subuser** After clicking: * Sub-user is created successfully * A **credentials file is automatically downloaded** Important Note: * This file contains: * Access Key * Secret Key * You **cannot retrieve the Secret Key again later.** **Step 4: Save Credentials Securely** * Downloaded file must be stored securely * If lost: * You need to **generate a new key** * Old key must be deleted. **Step 5: Verify Sub-user Creation** After creation, you will see the sub-user listed with: * Username * Assigned Buckets * Status (**Active**) * Last Active * Actions Status should be **Active** but Initially, no bucket is assigned

**Step 6: Open Sub-user Details** * Click on the **Sub-user name** You will open **Bucket Access Management page** **Step 7: Assign Bucket** * Click on **+ Assign New Bucket** You will proceed to assign access to a bucket

**Step 8: Configure Access Rule** A popup will appear: **Add Access Rule** Select permission: | Permission | Description | | ------------- | ---------------- | | View Only | Read access | | Upload Only | Upload only | | View & Upload | Read + Write | | Full Access | Complete control | For testing, select **Full Access** * Click **Create Rule**

**Step 9: Verify Access Rule** You will be redirected to **Manage Bucket Access Rules page** Check: * Permission → Full Access * Status → Active This confirms access is successfully configured

**Step 10: Final Verification** Go back to **Sub-user Management page.** Check: * Assigned Buckets : 1 * Status : Active Sub-user is now ready to use

Sub-user creation and access configuration is successfully completed.\ The user can now access assigned buckets using S3-compatible tools.

# Policies #### Overview Bucket policies are used to control access to objects within a bucket. These policies define **who can access the bucket and what actions they are allowed to perform**. Using the **Policy Setup Wizard**, administrators can configure access by selecting the bucket, assigning permissions, and defining the target users. *** #### Prerequisites Before creating a bucket policy, ensure that: * A bucket is already created. * You have access to the **Zata.ai Dashboard**. * You have permission to manage bucket policies. *** #### Procedure **Step 1: Navigate to Access Policies** 1. Log in to the **Zata.ai Dashboard**. 2. Open the **Object Storage** section. 3. Click **Access Policies**. 4. Click **Create Policy**. *** **Step 2: Select Bucket and Scope** 1. Select the **bucket name** from the dropdown list. Example:`prertest` 2. Choose the **Access Scope**: **Entire Bucket** * Applies the policy to all objects within the bucket. **Specific Folders** * Applies the policy only to selected folders inside the bucket. 3. Click **Next** to continue.

*** **Step 3: Select Grantee** In this step, define **who will receive the permissions**. Select the Available options include: * **Public (Anyone)** – Allows access to all users. * **Authenticated Users** – Allows access only to logged-in users. * **Specific Users or Roles** – Allows access only to selected identities. Click **Next**.

*** **Step 4: Configure Permissions** Permissions define **what actions users are allowed to perform**. **A. Object Operations** These permissions apply to files stored in the bucket. Recommended configuration for **public read access**: Enable: Download files Disable: Upload files\ Add/Edit file tags\ Remove file tags\ Cancel uploads\ Restore archived files

*** #### Bucket Operations These permissions control bucket-level actions. Optional: List files (allows users to view objects in the bucket) Disable: List file versions\ View bucket tags\ View versioning status Click **Next**.

*** **Step 5: Review and Create Policy** The **Review** page displays a summary of the policy configuration. Verify the following details: * Bucket name * Region * Grantee * Scope * Selected permissions * Policy effect (Allow or Deny) Enter a **Policy Name** (optional but recommended). Example: `public-read-policy` Click **Create Policy**.

*** **Result** After the policy is created, the defined permissions are applied to the selected bucket. With this configuration: * Users can **download objects** * Users can **view files (optional)** * Users **cannot upload, modify, or delete objects** This ensures **secure read-only access** to bucket contents. *** **Best Practices** * Grant only the permissions that are required. * Avoid enabling write or delete permissions for public access. * Use **specific folder scope** if access should be limited to certain objects. # Create a new access key and secret key for the specific subuser. Remember that when a user is created, an access key is automatically generated in the **Access Keys** section. However, this access key cannot be used to access the user directly. To access the user, you must create a new access key and secret key for the same user. * Navigate to the **Access Keys** section from the dashboard. * Click on **Generate Key**. * Select the required **Subuser** from the list. * Click on **Generate Key** to create a new access key and secret key. After generation, a key file will be provided for download.

As soon as you generate the access key, the key file is automatically downloaded. This file contains both the **Access Key** and the **Secret Key**. Now that the subuser keys have been generated, use these Access Key and Secret Key to authenticate and access the user.

# Roles A role defines the permissions assigned to a user in the Zata.ai environment. It controls what actions a user is allowed to perform, such as reading data, writing data, or managing system configurations. Roles help in maintaining security and proper access control by ensuring that each user has only the permissions required for their responsibilities. Common roles include: * **Read:**\ Allows the user to view and download data. No changes can be made. * **Write:**\ Allows the user to upload and modify data but does not allow deletion or management of system settings. * **Read and Write:**\ Allows the user to both view and modify data. * **Full Access:**\ Provides complete control over the account, including managing users, buckets, policies, and settings. steps to create a subuser and assign a role: [subuser](https://docs.zata.ai/user/create-a-subuser) # Account The Account section provides access to all account-related settings and support resources. It allows users to manage billing information, view official documentation, and get assistance when required. This section is mainly used for administrative and support purposes to ensure smooth account operations and proper usage of the platform. It includes the following options: * **Billing:**\ Used to manage subscription plans, view usage details, and handle payment-related information. * **Docs:**\ Provides access to platform documentation, guides, and references for understanding features and functionalities. * **Support:**\ Allows users to raise support requests, report issues, and get help from the Zata.ai support team. The Account section helps users manage their account efficiently and stay informed about platform usage and support resources. # Billing Zata.ai follows a **prepaid monthly billing** model, where customers pay in advance for a fixed amount of storage. Every subscription is valid for **30 days**, regardless of the calendar month, providing predictable billing and transparent pricing. ### Monthly Plans > **Note:** The revised pricing shown below is **effective from 1 October 2026**. Current pricing applies to subscriptions until **30 September 2026**. See [Zata Pricing Update — October 2026](https://docs.zata.ai/announcements-and-updates/zata-pricing-update-october-2026) for details. | Plan | Storage | Price / Month (Before GST) | New Price / Month (w\.e.f. Oct 1st) | | ----------- | -------------: | ------------------------------------: | ----------------------------------: | | Basic | 1 TB | ₹599 | ₹699 | | Standard | 5 TB | ₹2,970 | ₹3,470 | | Pro | 10 TB | ₹5,880 | ₹6,880 | | Business | 25 TB | ₹14,550 | ₹17,050 | | Enterprise | 50 TB | ₹28,800 | ₹33,800 | | Enterprise+ | 100 TB | ₹57,000 | ₹67,000 | | Custom | Custom Storage | Contact Solutions | Custom | > **Note:** Prices shown are exclusive of GST. Applicable taxes will be added during billing. *** ### Billing Cycle * All subscriptions are billed **monthly**. * One billing month is always **30 days**. * The billing cycle begins on the **date of payment**. *** ### Subscription Lifecycle If a subscription is not renewed, the account progresses through the following stages: | Stage | Duration | Description | | --------------------- | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | **Active** | 30 days | All services function normally. | | **Grace Period** | 5 days after expiry | Services continue to operate, allowing time to renew without interruption. | | **Retention** | Up to 90 days after expiry | The account is suspended and cannot be accessed, but all stored data is safely retained. Renewing the subscription restores access. | | **Deletion Deletion** | After 90 days | If a subscription is not renewed within 90 days of its expiry, all stored data is permanently deleted. | *** ### Renewing a Subscription Customers can renew their subscription during the **last 5 days** of the current billing period or any time after it expires. The following scenarios demonstrate how renewals, late payments, and plan upgrades & downgrades are handled under Zata.ai's billing system: ### 1. Renew Before Expiry If the same plan is renewed before expiry: * The new subscription is added after the current billing period. * No remaining subscription days are lost. * The next 30-day billing period starts immediately after the current one ends. ### 2. Renew After Expiry If payment is made after the subscription has expired: * A **Data Retention Fee** is charged for the number of days between the expiry date and the payment date. * The fee is calculated using the plan's daily rate. **Daily Rate = Monthly Plan Price ÷ 30** After payment: * A new 30-day subscription begins from the **payment date**. * The Data Retention Fee is displayed as a separate line item on the invoice. The Data Retention Fee may be charged for a maximum of **90 days** after the subscription expires. ### 3. Upgrading a Storage Plan Customers can upgrade to a larger storage plan at any time. When upgrading: * The unused value of the current subscription is converted into credit. * The credit is automatically deducted from the price of the new plan. * A new 30-day billing period starts from the payment date. This ensures customers only pay for the additional value of the upgraded plan. ### 4. Downgrading a Storage Plan Downgrades are **not permitted during an active billing period**. Once the current subscription expires, customers may switch to a smaller plan provided that: * The total stored data fits within the storage capacity of the selected plan. *** ### Free Trial Every new account receives a **15-day free trial** with access to all available storage locations. If a paid subscription is not purchased, the account is suspended after the trial ends. *** ### Important Notes * Billing is prepaid and charged monthly. * Every billing period is exactly **30 days**. * Renewing before expiry extends the subscription without losing any remaining days. * Renewing after expiry starts a new 30-day billing period from the payment date and includes a Data Retention Fee for the unpaid days. * Upgrading a plan immediately starts a new billing period, with unused subscription value automatically applied as credit. * Stored data is never deleted immediately after expiry. Data becomes eligible for deletion only after **90 days**, and cannot be retrieved. # Ingress and Egress Policy #### Ingress Policy Ingress refers to data uploaded into Zata.ai, such as files, backups, or objects transferred from applications and systems to Zata storage. * Data uploads to Zata.ai are free and unlimited. * There are no ingress restrictions on incoming data. * Users can upload any amount of data without additional charges. *** #### Egress Policy Egress refers to data downloaded or transferred out from Zata.ai storage to external systems or users. * Users get free egress equal to their active storage volume per month. * If egress usage exceeds the active storage volume, the account will be temporarily suspended. * Service will resume after upgrading the storage plan or when the next billing cycle begins. **Example:**\ If a user has 100 TB of active storage, they can download up to 100 TB for free in a month.\ If downloads exceed 100 TB, the account will be suspended until the plan is upgraded or the next billing cycle starts. # KnowledgeBase The KnowledgeBase section is a centralized place for documentation, guides, and learning resources related to Zata.ai. It helps users understand features, configurations, and best practices for using the platform effectively. This section includes: * Step-by-step guides and tutorials * Feature explanations and usage instructions * Troubleshooting and common issues * Integration setup references The KnowledgeBase acts as a self-help resource that enables users to quickly find solutions and learn how to use Zata.ai efficiently. # Integration The Integration section provides options to connect Zata.ai with third-party tools and platforms. It allows users to link their existing backup systems, storage tools, and applications with Zata.ai storage for seamless data transfer and management. This section helps in: * Connecting external backup solutions with Zata.ai * Enabling automated data backup and recovery * Simplifying data movement between different platforms * Centralizing storage operations using Zata.ai as a backend Integrations make Zata.ai more powerful by allowing it to work smoothly with existing enterprise tools and backup solutions. # Connect Acronis Backup Gateway With Zata.ai #### Prerequisites * Zata.ai S3-Storage Account * Zata.ai Bucket - See our Bucket Creation Guide * Access & Secret Key Pair - See our Access Keys Guide * Acronis Cyber Protect Cloud Partner account - [Acronis Partner Page](https://www.acronis.com/en-us/partners/) * Acronis Backup Gateway (VM or Bare Metal) - [Acronis Backup Gateway Guide](https://dl.acronis.com/u/storage2/html/AcronisStorage_2_quick_start_guide_en-US/index.html) * Acronis Agent installed on a VM or Server you wish to protect - [Acronis Agent Install Guide](https://kb.acronis.com/content/55052) ***Note:** your specific backup software handles the restoration process. As many potential variables will affect your unique environment, it is strongly recommended that you seek the guidance of your backup software's technical support team if you encounter difficulty, or have application-specific inquiries.* #### Reference Architecture

#### Create Backup Storage 1.1 Click “Storage Services > Backup Storage”, then click “Create backup storage”.

1.2 Choose “Public Cloud”, then click “Next”.

1.3 Check the box for your storage node, then click “Next”.

1.4 Select S3 Compatible storage like `“`AuthV2 compatible (S3)`”` in the dropdown.

1.5 Enter the Endpoint URL, Bucket Name, Access Key, and Secret Key, then click `“Next”`. * Endpoint URL: **** (Central India) or **** (Southern India) * Bucket Name: Your bucket name. * Access Key, and Secret Key: Create.

1.6 Choose appropriate redundancy settings in accordance with your organization’s policies, then click “Next”. **Note:** *For the sake of this example we have chosen "No Redundancy" . Get in touch with your Acronis Representative to determine an appropriate redundancy level and hardware configuration for your Cyber Protect Infrastructure cluster.*

1.7 Enter a Domain Name for the backup server, then click “Next”. ***Note:** This must be a real DNS address that is resolvable to the IP of your Acronis Cyber Infrastructure gateway, also the server must be able to accept inbound connections on port 44445.*

1.8 To register your Cyber Protect Infrastructure, enter your Acronis Partner Credentials, then click `“`Next”.

1.9 Review the “Summary”, then click “Create”.

1.10 You are presented with the “Backup storage Overview" page.

1.11 Confirm Registration by clicking the “Registration” Tab.

1.12 Log in to your Acronis Cyber Protect Cloud Partner account, and confirm that the location is available by clicking “Settings > Locations”.

Now you are ready to attach this storage to your New Customers in Acronis Cyber Protect account and push the backup Verify the backup by checking in you Zata.ai account. # Connect Bucket with CloudBerry CloudBerry is a cloud-based backup and disaster recovery solution that provide a secure and reliable way to protect data across various platforms. CloudBerry offers a range of products and services, cloud backup, Disaster recovery, cloud storage management, Endpoint Backup. **Lets connect buckets with CloudBerry** Download the **CloudBerry** your system to follow these [link.](https://www.msp360.com/explorer/windows/) After download and completion the installation to open your **CloudBerry**

Add the account to **enable backup and data restoration**. Click on the file section and click on **Add New account**.

Select the **S3 Compatible**

New S3 Compatible Storage Account- **Display Name :- Specify name** **Service Point :- idr01.zata.ai** (Central India) or **bom01.zata.ai** (Southern India) Access and secret key to follow these [link.](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key) Enter all the details and click on "Test Connection".

The connection was successful. **Click OK.**

The account has been **successfully** added.

Now, back to the **Cloudberry** dashboard, you can see two sections: left and right. The left section shows my local machine and the right section is configured for the **Zata.a**i account. Go to the right section and click on the source to select the **Zata.ai** account.

After selecting the account **Zata.ai**, we can see our buckets are visible. If you already have buckets, they will be visible. To create a **bucket**, follow these steps [link.](https://docs.zata.ai/manage/bucket/create-bucket)

Now transferring the data to each other. Choose the folder in both section, where you want to backup and restore your data. Here is an example: I selected **`Desktop/New Folder`** my local machine and **Zata.ai** for the bucket.

Now transfer the data by right-clicking the item and selecting **Copy/Move**.

Now we can see data is transferring, here data is transferring depends on your data and internet speed.

Now data have been transferred.

# Connect MSP360 Backup With Zata.ai MSP360 Backup supports multiple platforms including Windows, macOS, and Linux, as well as various databases and virtual environments. With features like file-level and image-based backups, it provides flexibility for different backup strategies. Additionally, it includes tools for monitoring and reporting, which help in maintaining transparency and compliance with data protection standards. Follow this link to log in or create an account on MSP360 and get a free trial: [MSP360 Free Trial](https://www.msp360.com/connect/) **Steps to Create a User and Connect to S3 Storage in MSP360** 1. **Log in**: Access your MSP360 account. 2. **Navigate to Dashboard**: Go to the MSP360 dashboard. 3. **Create User**: Set up a new user for S3 storage. 4. **Create Account**: Establish an account to connect to S3 storage.

Select the S3 Compatible

Give the Specify Credentials Storage Type: Default (S3 Compatible) Display Name: Enter\_your\_display\_name Access and Secret Keys by following this [link](/manage/access-keys). Signature version: **Select default >4** Set HTTPS:- **idr01.zata.ai** (Central India) or **bom01.zata.ai** (Southern India)

Create Backup Destination Give the Display Name:- Enter\_Display\_Name If you already have a bucket, select it. Otherwise, create a new one.

Select the company to assign when creating an account in MSP360 Backup.

Before saving, ensure you verify the details.

There are details about the attached storage with **MSP360**

# Connect Veeam Backup Gateway With Zata.ai Veeam Backup and Replication is a comprehensive data protection and disaster recovery solution designed to protect virtual, physical, and cloud-based workloads. **Adding a Backup Repository in Veeam on Windows** 1. **Download and Install** [**Veeam**](https://www.veeam.com/): * Visit the Veeam website and download the installer. * Follow the on-screen instructions to complete the installation. 2. **Add Backup Repository**: * Open Veeam Backup & Replication. * Go to **Backup Infrastructure**. * Follow the wizard to configure the repository settings.

Right-click on **Backup Repositories** and select **Add Backup Repository,** select the object storage,

Select **S3 Compatible**

Again Select **S3 Compatible**

Fill in the service point and region for adding credentials: **Access Key and Secret Key**. for Access key and secret key follow these [links](/manage/access-keys).

Provide the **bucket name** To create a bucket, follow these [links](/manage/bucket).

Select and create a folder

Update the mount server configuration accordingly.

After applying all the **configurations**, you should see a message indicating success.

You can now see a summary after completing the entire process.

# Connect Ahsay cloud backup suite(ACBS) with Zata.ai ## Connect Ahsay cloud backup suite(ACBS) with Zata.ai **AhsayCBS** stands for Ahsay Cloud Backup Suite, a comprehensive backup software solution designed for managed service providers and IT professionals. It provides data backup and restore capabilities for virtual machines, databases, servers, and desktops, supporting multiple platforms and storage options. Download the ACBS in Windows by following this [link](https://www.ahsay.com/en/download).

After downloading ACBS on Windows, click on AhsayCBS to start the installation.

Choose the language, and then click ok to continue

Click next to continue

Read the license agreement. Select “**I agree on the agreement**” If you agree, then click on \[Next] to continue the installation.

Choose the installation directory, then click next to **continue**.

Click next to **continue**

Enter the ports to be used by **AhsayCBS**. By default, the ports are 80 and 443 (Http and Https respectively). If these ports have been used by other applications, eg. Microsoft IIS, Apache or other applications. Please use alternative ports such as 8080, 8443, then click \[Next] to continue.

Click to start the installation

Click to complete the installation.

After clicking "Finish," the service will automatically open in the browser. Now enter the default credentials -> **Username: system** **Password: system**

Now enter the credentials to change password and press enter

This is a dashboard of **AhsayCBS**

Now click on the system settings > **Basic** > Click the Predefined Destinations

Now select the Predefined Destinations to add some details Name: Specify Name accordingly Type: Single storage destination Destination storage: AWS S3 Compatible Cloud Storage Host: **idr01.zata.ai** (Central India) or **bom01.zata.ai** (Southern India) Port: **443** Access Key and secret key to follow these [links.](https://docs.neevcloud.com/neevcloud-products/access-details/s3-ec2-credentials/create-s3-ec2-credentials) Signature version: **Select SV4** **Instructions** Provide the bucket name. Make sure the [bucket](https://docs.neevcloud.com/neevcloud-products/storage/object-storage/create-bucket) has already been created on **Zata**.**ai**.

Connect with **SSL**:- Click on the connect with **SSL** Click **Test** to verify your details. After clicking, you will see a popup.

Now save the details

Now back to the system settings > **Basic** > Click the Predefined Destinations

Navigate to the **Zata.ai** Dashboard, go to **Object Storage**, and select the desired bucket name.

# Connect Commvault Backup with Zata.ai #### Steps to Connect Zata.ai S3 Storage with Commvault: **1. Create an S3 Bucket in Zata.ai:** * Log in to your Zata.ai Console. * Navigate to the Bucket. * Click on "Create bucket" and follow the prompts to set up your bucket. **3. Generate Access Keys:** * In the Zata.ai Console, go to the [Access key](/manage/access-keys). * Generate access keys, which will be used in Commvault for authentication. **4. Configure Commvault to Use S3 Storage:** * Log in to your Commvault Command Center. * Navigate to the `Storage` tab. * Add a new cloud storage library and select S3-compatible storage as the storage type. * Enter the S3 bucket details, access key, and secret key obtained from Zata.ai. **5. Define Storage Policies:** * In Commvault, create or modify storage policies to use the S3 storage library you just configured. * Define the backup and retention policies according to your requirements. **6. Run Backup Jobs:** * Set up and run backup jobs, ensuring they are directed to the S3 storage. # Connect Vembu Backup with Zata.ai **Vembu Backup** **Vembu Backup** is a comprehensive data protection solution that provides backup, recovery, and disaster recovery for various IT environments including physical, virtual, and cloud infrastructures. It supports all major platforms and helps in safeguarding business-critical data through advanced features like incremental backups, instant restores, and offsite replication. Download the Vembu backup solution in Windows by following this [link](https://www.vembu.com/)

**For the installation Guide follow these** [**link**](https://www.bdrsuite.com/guide/vembu-bdr-suite/7-0/en/bdr-installation-windows.html) After installation, the following screen opens in the browser:

Access the browser and configure **object storage.**

Select "**Create New Object Storage Repository**" Give the Name of Repository - ......... Repository Type:- S3 compatible Set as the default repo:- NO Server Endpoint:- **idr01.zata.ai** (Central India) or **bom01.zata.ai** (Southern India) DC Region:- In this section, the region is selected default. Credential: - click on the Add New Credentials:- Set the name of Display name, Access key, Secret key

After this, select the bucket and cache location.

Create the object storage repository.

# Connect NetDrive 3 with Zata.ai A comprehensive, step-by-step guide to mount your **Zata.ai** object storage as a local drive using **NetDrive 3** on macOS and Windows. ### Overview This guide helps teams using **Zata.ai** (S3-compatible storage) set up NetDrive 3 for seamless drag-and-drop file access through Finder/Explorer and desktop applications. **Tested with:** NetDrive v3.5.251 (macOS & Windows) ### Prerequisites Before you begin, ensure you have: * **Zata S3 credentials:** Access Key ID and Secret Access Key * **Zata endpoint:** `https://idr01.zata.ai` (Central India) or `https://bom01.zata.ai` (Southern India) * **Bucket name** (optional but recommended): e.g., `my-team-backups` * **NetDrive 3 installed:** Version 3.x for macOS or Windows * **Network access:** Outbound HTTPS (TCP 443) to your Zata endpoint * **Correct system time:** Significant time drift can break S3 authentication > **Tip:** If your account has restricted bucket listing permissions, prepare to enter a specific bucket name during setup. ### Step 1: Install NetDrive 3 ### Download NetDrive 3 Visit the [official NetDrive download page](https://www.netdrive.net/download/) to get the latest version. ### Windows Installation 1. Download and run the NetDrive 3 installer 2. Complete the installation process following the setup wizard

1. Launch **NetDrive** 2. If prompted, allow NetDrive through Windows Defender Firewall for private networks ### macOS Installation 1. Download the NetDrive 3 installer for macOS 2. Install the application 3. Open **NetDrive** from Applications folder ### Step 2: Create New S3-Compatible Connection 1. In NetDrive, click the **green + button** (Add New Drive) as shown in the interface

1. You'll see the "Add a Personal Drive" configuration screen 2. **Storage type:** Select **S3** from the dropdown menu 3. **Label:** Enter a descriptive name (e.g., `Zata`)

> **Note:** On macOS, NetDrive mounts drives under **Locations** in Finder sidebar. On Windows, you can assign a specific drive letter. ### Step 3: Configure Connection Details Fill in the S3 account configuration form with these exact values:

### Account Settings * **Server Address:** `idr01.zata.ai` (or `bom01.zata.ai` for Mumbai) * **Access ID:** Enter your Zata Access Key ID (e.g., `DKQLR6NUF7IYG6SFQSU0`) * **Secret Key:** Enter your Zata Secret Access Key * **Save account ID and secret key** (recommended) ### For Limited Bucket Access If you have restricted permissions: * **Bucket name:** Enter your specific bucket name (e.g., `my-team-backups`) ### Network Settings * Click **PROXY SETTINGS** if you need to configure proxy settings for your network > **Important:** Make sure to use the exact server address `idr01.zata.ai` (Central India) or `bom01.zata.ai` (Southern India) without the `https://` prefix. ### Step 4: Advanced Configuration Before connecting, ensure these critical settings are configured: * **Use HTTPS (SSL/TLS):** **ON** * **Force path-style addressing:** **ON** *(prevents SSL certificate issues)* * **Port:** `443` * **Region:** `CentralIndia` or `SouthIndia` (case-sensitive) * **Signature:** **V4** * **Connect at login/Mount at boot:** **ON** (optional) * **Background transfer:** **ON** (recommended) Click **CONNECT** to mount the drive. ### Step 5: Verify the Connection 1. Open the mounted **Zata** drive in Finder (macOS) or Explorer (Windows) 2. Create a test folder (e.g., `netdrive-test`) 3. Copy a small test file into the folder 4. Verify the file appears in your Zata bucket using your preferred S3 tool ### Troubleshooting ### Authentication Issues **Problem:** `SignatureDoesNotMatch` or authentication failures **Solutions:** * Verify **Signature** is set to **V4** * Enable **Force path-style addressing** * Double-check endpoint URL, Access Key, and Secret Key (no trailing spaces) * Ensure system date/time is accurate with automatic sync enabled * Verify bucket name spelling and case if specified ### SSL/Certificate Issues **Problem:** SSL or hostname mismatch errors **Solutions:** * Keep **HTTPS** enabled * Use the exact Zata endpoint: `idr01.zata.ai` or `bom01.zata.ai` * Ensure **Force path-style** is **ON** ### Bucket Access Issues **Problem:** Can't list buckets or see empty bucket list **Solutions:** * Your access key may lack `ListAllMyBuckets` permission * Enter the bucket name explicitly in the connection settings * Reconnect after specifying the bucket **Problem:** `403 AccessDenied` errors **Solutions:** * Check bucket permissions and policies for your access key * Verify you're connecting to the correct bucket and account * Ensure your key has necessary permissions (list/get/put/delete) ### Performance Issues **Problem:** Slow file operations (rename/move/copy) **Solutions:** * Enable background transfer in NetDrive settings * Break large file operations into smaller batches * For bulk uploads, consider using dedicated tools like rclone, then use NetDrive for daily operations ### Security Best Practices * **Principle of least privilege:** Create access keys limited to required buckets and actions * **Regular key rotation:** Update and revoke old access keys periodically * **Always use HTTPS:** Never disable SSL/TLS encryption * **Restrict access:** Limit key usage to authorized machines only ### Configuration Summary Here's a complete example of the settings (replace with your actual values): ``` textStorage type: S3 Server address: idr01.zata.ai (or bom01.zata.ai) Access Key ID: DKQLR6NUF7IYG6SFQSU0 Secret Access Key: ************************ Region: CentralIndia (or SouthIndia) Signature: V4 Bucket: my-team-backups Use HTTPS: ON Force path-style URL: ON Port: 443 Connect at login: ON Background transfer: ON ``` *** > **Success!** You should now have Zata storage mounted as a local drive, accessible through your system's file manager for seamless file operations. # Connect GoodSync with Zata.ai GoodSync is a file synchronization and backup software. It can sync files between: ## Prerequisites To download **GoodSync** and install it, follow these [links](https://www.goodsync.com/download). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3).
[Embedded Link](https://www.youtube.com/watch?feature=youtu.be\&v=u2E1DyTx5iA) ## Set up From Scratch with Zata.ai After downloading and installing GoodSync, open the application and begin the configuration process. Open the GoodSync and click on the New Job

Type Your Folder name and choose 'Backup' or 'Synchronization'.

Select the left folder as the local folder (e.g., `D:\Projects`).

Select the correct folder in Amazon S3, then click *Add New Account*. Set the following values: * **Endpoint:** idr01.zata.ai (Central India) or bom01.zata.ai (Southern India) * **Access Key:** Obtain from Zata.ai * **Secret Key:** Obtain from Zata.ai Now click on the save.

Ensure that **Auto Run** is turned **ON** for Auto Sync. Click on the Auto Button

Select the **Periodically** option, set the desired time interval (e.g., every 5 minutes), and click **Save**.

* Run the job manually once to verify that files are uploaded to the Zata.ai bucket. * Log in to the Zata.ai panel and confirm that the uploaded files are visible in the bucket. * Enable Auto Schedule to automate future uploads without manual intervention. # Connect Forklift with Zata.ai ## ForkLift for macOS ForkLift is a powerful file manager and FTP client for macOS, offering a dual-pane interface, advanced file operations, and integration with various cloud services. ### Prerequisites Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow these: click on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). ### Installation 1. Download ForkLift from the [official website](https://binarynights.com). 2. Open the downloaded `.dmg` file. 3. Drag ForkLift to the Applications folder. 4. Launch ForkLift from the Applications folder. ## Set Up from Scratch with Zata.ai After downloading and installing Forklift, open the application and begin the configuration process. ### Launch Forklift on your Mac. In the top menu bar, click Go → Connect.

### Configure the AWS S3 connection #### In the **Connect** window * Protocol: Select Amazon S3 * Server: Enter idr01.zata.ai (Central India) or bom01.zata.ai (Southern India / Mumbai) * Username: Enter your Zata Access Key ID * Password: Enter your Zata Secret Access Key Now click on the connect.

#### Browse Your Buckets * Once connected, your available buckets on Zata will be displayed. * You can drag and drop files between Finder/Forklift and your Zata storage. * Use Forklift’s dual-pane view to easily transfer files to and from Zata.

# Connect Odrive with Zata.ai **odrive** is a cloud storage management tool that lets you connect and manage multiple cloud storage services from one place. #### Prerequisites Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow these: click on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). Download the odrive by following this [link](https://docs.odrive.com/docs/odrive-usage-guide) ### Launch odrive 1. Open the odrive app on your desktop (Windows or macOS).

After the installation is complete, click Get started to launch odrive.

When you click on *Get Started*, a prompt will automatically open in your browser, allowing you to sign up for an account using your email ID

Now sync your procore documets directly to your desktop.

Now click on Link Storage and select S3 Compatible.

#### Enter Zata.ai Storage Details In the **S3 Compatible Storage** setup window, fill in the required fields as shown below: * **Name:** `Zata` (or any identifier you prefer) * **Host:** idr01.zata.ai (Central India) or bom01.zata.ai (Southern India)\` * **Bucket Name:** Your Zata.ai bucket name * **Access Key ID:** Provided by Zata.ai * **Secret Access Key:** Provided by Zata.ai * **Default Storage Class:** `Standard` * **Directory Structure:** `Simple '/' Delimited` Now click on the link.

### Verify Connection and Browse Buckets After successfully linking your Zata.ai storage, you will see your local files on the left panel and your Zata.ai buckets on the right panel. * The left pane**l** shows your directories. * The right panel lists your Zata.ai buckets.

# Connect Handy Backup with Zata.ai Handy Backup is a backup software solution designed to automate the process of copying and restoring files, folders, databases, and entire system images. ## Prerequisites Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). To download Handy Backup and install it, follow this [link](https://www.handybackup.net/). After downloading the handy backup, follow these steps to integrate with the zata.ai ### **Launch Handy Backup** Open the Handy Backup application and start creating a new backup task. Choose Create a new task, select Backup task, then click Next.

### Select Data to Backup Browse and select the files/folders you want to back up. Click Next to continue.

### Select Storage Destination From the list of storage options, choose S3 Cloud. Then, Click on Create a Connection.

Configure Zata.ai Connection Enter your Zata.ai details: Service Point (Endpoint): (or for Mumbai) Region: CentralIndia (or SouthIndia for Mumbai) Access Key ID: \ Secret Access Key: \ Click Test Connection to validate.

Click Next, adjust schedule/options if needed, then click Finish to save the backup job.

Run Backup You can now run the task manually or wait for the scheduled backup. Your data will be securely uploaded to Zata.ai. # Connect WinSCP with Zata.ai #### WinSCP Overview WinSCP is a free and open-source SFTP, FTP, WebDAV, Amazon S3, and SCP client for Microsoft Windows. Its primary function is to transfer files between a local and a remote computer securely. In addition to its basic file transfer capabilities, WinSCP provides scripting and basic file management functionality. ### Prerequisites To download WinSCP and install it, follow this [link](https://winscp.net/eng/download.php). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). ### Launch WinSCP Open the WinSCP application on your computer. On the login windows, click on the New site. ### Select S3 Protocol From the File protocol dropdown, select Amazon S3. The login screen will now adjust for S3 inputs.

### Enter Zata.ai S3 Details Fill in the following details: * Host name: `idr01.zata.ai` (Central India) or `bom01.zata.ai` (Southern India / Mumbai) Port number: 443 Access key ID: Your Zata.ai Access Key Secret access key: Your Zata.ai Secret Key

### Save the Connection Click Save to store the session for future use. Optionally, check Save password for convenience. #### Connect and Transfer Files Click Login. You will now see your Zata.ai bucket(s) listed. You can drag-and-drop files between your PC and Zata.ai storage, just like an FTP/SFTP server.

# Connect Iperius Backup with Zata.ai This guide explains the process to set up Iperius Backup with Zata.ai’s S3-compatible storage for automated, secure file backups. *** ### Prerequisites To download Iperius Backup and install it, follow this [link](https://www.iperiusbackup.com/). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). *** ### Create a New Backup Job 1. Launch Iperius Backup. 2. Click **Create new backup job**.

* Add files/folders you want to back up.

* Use filters or exclusions for file type/size as needed. *** ### Add Zata.ai as Cloud Destination 1. In the **Destinations** tab, select **Cloud**. 2. Choose **Amazon S3** (compatible with Zata.ai). 3. Click **New Account**, and fill out: * Name: `zata` * Type: `S3` * Access Key ID/Secret Access Key * Service Point (Endpoint): (or for Southern India) * Region: `CentralIndia` (or `SouthIndia` for Mumbai) * Enable **Use SSL** option. * Save the account settings.

*** ### Select Bucket and Further Settings 1. Choose your Zata.ai bucket (e.g., `test`). 2. Optionally, add a subpath for organization. 3. Set backup options: * **Backup type:** Choose between full or incremental. * **Number of copies:** Set retention (e.g., 1 or more). * Enable zip compression and AES-256 encryption if desired. * Set a password for zip files for added security. * Choose how zip files are named and whether to create individual zip files per item. * Select path format inside zip files ("Full path including drive" recommended).

*** ### Step Scheduling Automated Backups 1. Navigate to **Scheduling** tab. 2. Enable **Run backup automatically**. 3. Choose schedule: * Weekly (select days) * Monthly (select calendar days) * Custom intervals (e.g., every X days/hours/minutes) 4. Add execution times as needed (e.g., 20:00).

*** ### Review and Save Job 1. In the **Summary** tab: * Enter Job name (e.g., `Zata`), optional description. * Confirm items, destinations, and schedule. * Optionally, enable RMM console monitoring. * Option to shut down computer after backup completion. 2. Click **OK** to save the job. *** ### Run Backup and Verify 1. Execute the backup job manually for the first time. 2. Confirm backup progress and completion message. 3. Check Zata.ai Console to verify uploaded files.

*** ### Additional Notes * **Immutability:** For immutable backups, enable Object Lock on your Zata.ai bucket before configuration. * **Security:** Use AES-256 encryption and passwords for sensitive files. * **Performance:** Iperius supports multi-threaded, multipart uploads for large files. * Ensure system time is synchronized for S3 signature validation. *** ### Troubleshooting * If backups fail, check log files (from "See log" after backup completion). * Verify credentials and endpoint accuracy in Cloud Account setup. * Make sure your bucket exists and Object Lock is enabled if needed. *** # Connect UpdraftPlus Backups with Zata.ai This guide explains how to configure the UpdraftPlus WordPress Backup Plugin to store backups on Zata.ai’s S3-compatible object storage. Screenshots are included at each step for clarity. *** ### Prerequisites To download UpdraftPlus and install it, follow this [link](https://teamupdraft.com/updraftplus/). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). *** ### Install UpdraftPlus 1. Go to **Plugins → Add New** in WordPress Admin. 2. Search for “UpdraftPlus” and install it. 3. Click **Activate** after installation.

*** ### Open UpdraftPlus Dashboard * In the sidebar, click **UpdraftPlus** under Plugins. * You’ll see the Backup/Restore dashboard, last log message, and scheduling info.

*** ### Access Backup Settings * In the dashboard, open the **Settings** tab. * Choose backup schedules and the number of retained backups. * Select **S3-Compatible (Generic)** under “Choose your remote storage” options.

*** ### Enter Zata.ai Storage Details * Enter your Zata.ai S3 credentials: * **S3 access key**: (Your Zata Access Key) * **S3 secret key**: (Your Secret Key) * **S3 location**: (Your bucket, e.g., `s3generic://wp-backups`) * **S3 end-point**: idr01.zata.ai (Central India) or bom01.zata.ai (Southern India) * **Bucket access style**: Path style (recommended) * **Signature version**: SigV4 * Click **Test S3-Compatible (Generic) Settings** to verify.

*** ### Configure Backup Schedule * Use the dropdown menus to set the frequency for **Files backup** and **Database backup**. * Adjust how many scheduled backups you want to retain.

*** ### Run a Manual Backup * Go to the **Current Status** tab. * Click **Backup Now**. * In the dialog, select what to include: * **Include your database in the backup** * **Include your files in the backup** * **Send this backup to remote storage** * Click **Backup Now** to start. *** ### Confirm Backup and Remote Storage * When the backup finishes, verify that your files are listed in Zata.ai’s S3 bucket (via the dashboard or S3 explorer). * Check the status messages and logs for confirmation. *** ### Best Practices * Always test your restore process with a test backup. * Set retention policies for automatic old backup removal. * Consider encryption for sensitive sites and data. *** ### Troubleshooting * A successful “Test S3-Compatible settings” means your WordPress site can reach Zata.ai. * If errors appear, double-check credentials, endpoint, and bucket name. * Review UpdraftPlus logs in the dashboard for detailed error messages.
# Connect CrossFTP with Zata.ai ### Introduction **CrossFTP** is a versatile FTP and cloud storage client that supports S3-compatible endpoints such as **Zata.ai**. You can use it to upload, download, and manage files in cloud storage just like with FTP servers. ### Prerequisites To download CrossFTP and install it, follow this [link](https://www.crossftp.com/). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). ### Step-by-Step Setup ### Launch CrossFTP Open CrossFTP after installation. ### Open Site Manager * Navigate to **Sites → Site Manager** from the main menu. * Click **New Site** to create a new profile.

### Configure S3 Connection * Set the **Protocol** dropdown to **S3/HTTPS**.

* Fill in these details: * **Host:** `idr01.zata.ai` (Central India) or `bom01.zata.ai` (Mumbai) * **Access ID:** Your Zata Access Key ID * **Secret Key:** Your Zata Secret Access Key * **Port:** `443` (default HTTPS port) * **Region:** `CentralIndia` or `SouthIndia` (as provided by Zata.ai) * Optionally, specify a **Default Bucket name** to connect to automatically. ### Advanced & Security Settings * Ensure **Use SSL** is enabled for secure transfer. * Adjust additional settings as needed (proxy, firewall, etc.). ### Connect and Manage Files * Click **Connect**.

* On successful connection, your **buckets and folders** will appear in the right-hand pane. * Drag and drop files, or use the context menu to upload/download/manage your data.

### Tips & Troubleshooting * Always use the correct **region endpoint** and ensure bucket names are accurate. * Use the Site Manager’s **Quick History** to reconnect to recent connections easily. * Check log messages at the bottom for connection status and errors. * For large files or many objects, use batch upload/download features for efficiency. # Connect Arq Backup with Zata.ai Arq backs up your files to the cloud automatically and safeguards your digital privacy. Zata’s object storage (S3-compatible) can be used as a secure storage backend for Arq. ### Prerequisites To download Arq and install it, follow this [link](https://www.arqbackup.com/download/). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). ### Step-by-Step Configuration ### 1. Launch Arq and Create Backup Plan * Open Arq Backup. * Click **Create a Backup Plan** in the initial dashboard.

*** ### 2. Add Zata as a Storage Location * When asked "Where should Arq store the backup data?", click **Add Storage Location...**

*** ### 3. Select S3-Compatible Server * In the "Add a Storage Location" dialog, select **S3-Compatible Server** and click **Continue**.

*** ### 4. Enter Zata S3 Credentials * Fill in the following details: * **Server URL:** `https://idr01.zata.ai:443` (or `https://bom01.zata.ai:443` for Southern India) * **Region:** `central India` (or `Southern India` for Mumbai) * **Access Key ID** and **Secret Access Key** from your Zata account * **Bucket Name:** (e.g., your chosen bucket like `abhatest`) * Click **Save** to confirm.

### 5. Confirm Zata Endpoint and Bucket * In the "Create Backup Plan" dialog, confirm the Zata endpoint (`https://idr01.zata.ai` or `https://bom01.zata.ai`).

*** ### 6. Set Encryption Password * Choose a strong password for encrypting backups. * Enter and confirm it; this secures your backed up data.

*** ### 7. Select Files to Back Up * Choose one of the options: * Back up all drives, with standard exclusions * Back up user data on the main drive * Manually select folders * Click **Create Backup Plan** to begin.

# Connect ExpanDrive with Zata.ai ExpanDrive can be configured to connect with **Zata.ai Object Storage**, allowing you to mount Zata buckets as network drives and access them seamlessly from **Finder (macOS)** or **Explorer (Windows)**. This guide provides step-by-step instructions to set up ExpanDrive with Zata.ai. [Embedded Link](https://youtu.be/63QTHThuyuY) *** ### Prerequisites To download ExpanDrive and install it, follow this [link](https://www.expandrive.com/download). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). *** ### 1: Launch ExpanDrive 1. Open the **ExpanDrive** application. 2. Click **New Connection**.

*** ### 2: Select Connection Type * For versions **v7 and later** → choose **Amazon S3**. * If you are using a version prior to v7 → also choose **Amazon S3**.

*** ### 3: Enter Zata.ai Details Fill in the following fields: * **Server / Endpoint:** `https://idr01.zata.ai` (or `https://bom01.zata.ai` for Southern India)\ \&#xNAN;*(replace with your assigned region endpoint if different)* * **Access Key ID:** enter your Zata.ai access key * **Secret Access Key:** enter your Zata.ai secret key * **Bucket (optional):** enter the bucket name if you want to connect directly to a specific bucket. * Leave blank if you want to browse all buckets.

*** ### 4: Save and Connect 1. Click **Save**. 2. ExpanDrive will mount your Zata.ai storage as a network drive. 3. You can now access your Zata.ai bucket directly from Finder (macOS) or Explorer (Windows).

*** ### Notes * For **ExpanDrive Server Edition**, always select the **Amazon S3** connection type. * Use the correct **Zata.ai endpoint** for your region. * Works seamlessly across both **Windows** and **macOS**. * Once connected, you can **drag, drop, upload, and manage files on Zata.ai just like a local drive**.
# Connect qBackup with Zata.ai qBackup is validated for use with **Zata.ai Object Storage**. This guide explains how to configure qBackup to back up your files to Zata.ai. *** ### Prerequisites To download qBackup and install it, follow this [link](https://www.qualeed.com/en/qbackup/). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). *** ### Create a New Project in qBackup * Launch qBackup. * Go to **File > New Project**. * Enter a project name (e.g., `ZataBackup`).

*** ### Add Backup Sources * In the **Include** tab, add the files and folders you want to back up. * In the **Exclude** tab, define any files or folders you do not want to back up.

*** ### Configure Storage (Zata.ai) * Go to the **Storage** tab. * Select **S3 Compatible Storage**. * Choose **Use Access Key ID and Secret Access Key**. * Enter your credentials: * Access Key ID: `` * Secret Access Key: `` * Endpoint: (or for Southern India) * Bucket name: `` *Recommendation: Create a fresh bucket or dedicated folder for qBackup jobs to avoid "Storage is not empty" errors.*

*** ### Schedule (Optional) * Navigate to the **Maintenance** tab. * Configure a schedule for automated backups: * Daily * Weekly * Custom frequency *** ### Run the Backup * Save the project. * From the main screen, select your project. * Click **Backup** to start the process.

# Connect SmartFTP with Zata.ai A practical walkthrough to connect **SmartFTP** to your **Zata.ai Object Storage** (S3‑compatible) for simple drag‑and‑drop transfers, folder sync, retries, and bookmarks — all from a classic Windows FTP client UI. *** ### Who This is For Teams using **Zata.ai** who prefer SmartFTP’s familiar interface for uploads, downloads, and sync operations. *** ### Prerequisites To download SmartFTP and install it, follow this [link](https://www.smartftp.com/en-us/). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). *** ### Quick Connect (First Time) 1. Open **SmartFTP**. 2. Go to **File ▸ Connection** (or press `Ctrl+N`). 3. Fill in the fields: * Protocol: **S3 (Amazon)** * Host: `idr01.zata.ai` (or `bom01.zata.ai` for Mumbai) *(replaces `s3.amazonaws.com`)* * Port: **443** * Encryption: **TLS/SSL (default)** * Username: *Access Key ID* * Password: *Secret Access Key* 4. Click **OK / Connect**.

You should now see your account and accessible buckets in the Remote Browser.

*** ### Open a Specific Bucket (Faster, Cleaner) To connect directly to a bucket: * In the **Connection** window, set **Path** = `/your-bucket-name` * Example: `/my-team-backups` *Note: If you don’t have List permissions on the account root, always set the Path to avoid errors.* *** ### Save as a Favorite 1. When connected, click **Favorites ▸ Add to Favorites…** 2. Name it, e.g. `Zata – Backups (idr01)` or `(bom01)` 3. In **Favorite Properties ▸ Connection**: * Confirm Host = `idr01.zata.ai` (or `bom01.zata.ai`) * Path = `/your-bucket-name` * Enable **Reconnect** and **Keep Alive** to avoid idle timeouts. *** ### Upload / Download Basics * Drag‑and‑drop files/folders between **Local (left pane)** and **Remote (right pane)** * Transfers appear in the **Transfer Queue**; you can pause, resume, or reorder * Right‑click a folder → **Transfer ▸ Synchronize** to mirror local ↔ bucket *** ### Recommended Transfer Settings * Retries: **5** (with backoff) * Concurrent transfers: **3–5** (based on your uplink speed) * Integrity: enable **Verify / Compare after transfer** for critical data * Preserve timestamps: **On** *** ### Verify Your Connection Perform these sanity checks: * Create a test folder (e.g. `test-smartftp`) * Upload a small file (e.g. `readme.txt`) * Rename / delete the file to confirm write permissions * Cross‑check the object in another tool (Zata Panel / Rclone) *** ### Appendix — Zata Endpoints * **Central India**: `https://idr01.zata.ai` * **Southern India (Mumbai)**: `https://bom01.zata.ai` * Use other regional endpoints provided by Zata if applicable. # Connect Plesk with Zata.ai Zata.ai provides S3-compatible object storage that can be integrated with Plesk to back up websites, databases, and configurations directly to the cloud. This guide will walk you through setting up Zata.ai as a backup destination in Plesk. ## **Prerequisites** To download Plesk and install it, follow this [link](https://docs.plesk.com/en-US/obsidian/deployment-guide/plesk-installation-and-upgrade-on-single-server/1click-plesk-installation/installing-plesk-for-windows-in-one-click.76448/). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). ### Log in to Plesk Open your Plesk panel (`https://yourdomain:8443`). Log in with your admin credentials. #### Install the Amazon S3 Backup Extension From the left menu, go to Extensions. Search for Amazon S3 Backup. Click Install. *The Amazon S3 extension works with any S3-compatible storage, including Zata.ai.*

### Configure Zata.ai as Backup Storage Go to Tools & Settings → Backup Manager.

Click Remote Storage Settings → Amazon S3 Backup.

Fill in the following details: * **Service Provider:** Custom. * **Bucket Name:** `plesk-backups` (replace with your bucket name) * **Access Key ID:** *Your Zata Access Key* * **Secret Access Key:** *Your Zata Secret Key* * **Endpoint:** (or for Southern India) Click ok to save.

### Test the Connection * Once saved, Plesk will attempt to connect to Zata.ai. * If successful, you will see Zata.ai (via Amazon S3 extension) listed as a remote backup option. ### Run a Backup Navigate to Backup Manager. Select Back Up.

Choose Store in remote storage only (or both local + remote).

Click on ok and start the backup. Verify the backup files in your Zata.ai bucket. # Connect Syncovery with zata.ai Syncovery is a powerful backup and synchronization software for Windows, macOS, Linux, and others. It can be used to back up and sync files to **Zata.ai Object Storage (S3-compatible)** for secure and scalable cloud storage. This guide provides step-by-step instructions to configure Syncovery with **Zata.ai**. ## Prerequisites To download Syncovery and install it, follow this [link](https://www.syncovery.com/). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). ## Launch Syncovery and Create a New Profile Open **Syncovery**. From the top menu, click on Perform a Synchronization or Backup now,

### Select Source Choose the **local folder** on your system that you want to back up or sync.

### Select Destination (Zata.ai Storage) Choose **S3** as the storage type. In the S3 settings window: * **Access Key ID**: Enter your Zata.ai Access Key. * **Secret Access Key**: Enter your Zata.ai Secret Key. * **S3 Endpoint**: (or for Southern India) * **Bucket** : (or ) Click **OK.**

### Configure Profile Settings * Set your preferred options for: * **Scheduling** (daily, weekly, real-time sync). * Click **Save**.

### Run the Backup/Sync 1. Select your newly created profile. 2. Click **Run Profile** to start uploading files to Zata.ai. 3. Monitor the job log to ensure files are transferred successfully.

# Connect Cloud Mounter with Zata.ai ## **Prerequisites** To download **CloudMounter** and install it, follow this [link](https://mac.eltima.com/mount-cloud-drive.html). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). ### Connect CloudMounter (macOS) Open **CloudMounter** → choose **Amazon S3**.

1. In the connection panel: * **Connection name:** `zata` * **Access Key ID** / **Secret Access Key:** paste from Step 2 * **Server endpoint:** `https://idr01.zata.ai` (Central India) or `https://bom01.zata.ai` (Southern India) * **Bucket:** suharclone1 *(You have type your bucket name)* 2. Click **Mount**. The drive appears in **Finder** under *Locations*.

#### Verify & Use * Drag & drop files in Finder / File Explorer — they upload directly to Zata. * Right‑click the connection → **Open in Browser** to confirm objects are visible in the Zata Console. * Check the **status icon** in CloudMounter for sync/transfer progress.

# Connect S3fs With Zata.ai Zata.ai provides S3-compatible object storage that can be mounted as a local drive on your Linux system using s3fs-fuse. [Embedded Link](https://youtu.be/iVdumfMFw4s) ### Prerequisites Before you start, ensure you have: * A Zata.ai account * Access Key and Secret Key (available in Zata Console → Access Keys) * Your Bucket Name * Your Zata.ai S3 Endpoint (e.g., `https://idr01.zata.ai` or `https://bom01.zata.ai`) * A Linux server (Ubuntu/Debian/CentOS supported) * Root or sudo privileges ### Install s3fs ### Ubuntu/Debian ``` sudo apt update sudo apt install s3fs -y ```

### CentOS/RHEL ``` sudo yum install s3fs-fuse -y ``` ### Create Credential File Create a password file to store your access keys: ``` echo ACCESS_KEY_ID:SECRET_ACCESS_KEY > ~/.passwd-s3fs chmod 600 ~/.passwd-s3fs ```

Replace `ACCESS_KEY_ID` and `SECRET_ACCESS_KEY` with your actual credentials. ### Create Mount Directory ``` sudo mkdir /mnt/s3bucket ```

### Mount the Zata.ai Bucket Run the following command (replace placeholders): ``` s3fs BUCKET_NAME /mnt/s3bucket -o passwd_file=~/.passwd-s3fs,url=https://YOUR_S3_ENDPOINT,allow_other,use_cache=/tmp,sigv4,use_path_request_style ```

### Example ``` s3fs neevapp /mnt/s3bucket -o passwd_file=~/.passwd-s3fs,url=https://idr01.zata.ai,allow_other,use_cache=/tmp,sigv4,use_path_request_style # For Mumbai, use url=https://bom01.zata.ai ``` ### Verify Mount ``` df -h | grep zata ls /mnt/zata ```

### Auto-mount on Boot To automatically mount the bucket on system boot, edit `/etc/fstab` and add the following line: ``` s3fs#BUCKET_NAME /mnt/zata fuse _netdev,passwd_file=/root/data/passwd.txt,url=https://idr01.zata.ai,allow_other,use_cache=/tmp,sigv4,use_path_request_style 0 0 # For Mumbai, use url=https://bom01.zata.ai ``` Then test the configuration: ``` sudo mount -a ``` ### Conclusion Your Zata.ai Object Storage is now mounted as a local drive. You can read and write files directly to `/mnt/zata` just like a local directory. ### Example Use Cases * Backup local folders directly to Zata.ai * Mount in a Docker host for shared media files * Use as a network drive in hybrid cloud setups # Mount S3 bucket to Linux operating system To mount an S3 bucket to a Linux machine, you can use a tool like **s3fs** Step 1: Install dependencies ``` sudo apt-get update -y sudo apt-get install s3fs -y ``` Step 2: Store your credentials Create a credentials file to store your access and secret keys securely ``` echo ACCESS_KEY_ID:SECRET_ACCESS_KEY > ~/.passwd-s3fs chmod 600 ~/.passwd-s3fs ``` Replace `ACCESS_KEY_ID` and `SECRET_ACCESS_KEY` with your actual credentials.

Step 3: Create a mount point Create a directory where the S3 bucket will be mounted: ``` sudo mkdir /mnt/s3bucket ```

Step 4: Mount S3-Compatible Storage with Path-Style Addressing ``` s3fs BUCKET_NAME /mnt/s3bucket -o passwd_file=~/.passwd-s3fs,url=https://YOUR_S3_ENDPOINT,allow_other,use_cache=/tmp,sigv4,use_path_request_style ``` #### Breakdown of the Options: * `BUCKET_NAME`: Replace this with your actual bucket name. * `/mnt/s3bucket`: The mount point where the bucket will be mounted. * `-o passwd_file=~/.passwd-s3fs`: Specifies the path to the file where your credentials are stored (replace with your own credentials file path if necessary). * url=[https://idr01.zata.ai ](https://idr01.zata.ai)(or for Southern India) with your S3-compatible service's endpoint. * `allow_other`: Allows other users to access the mounted directory. * `use_cache=/tmp`: Caches files locally `/tmp` to improve performance. * `sigv4`: Forces Signature Version 4 signing (needed for most S3-compatible services). * `use_path_request_style`: Forces path-style addressing, which is required for some S3-compatible service Step 5: Verify the mount ``` sudo df -h ```

Now check to mount to navigate to the directory and create a new file on your system.

Now back to the Zata.ai dashboard click on the bucket section, select the bucket, and check the content

**Lets see file has been created.**

**To mount an S3-compatible bucket with path-style addressing** **permanently** (so that it is automatically mounted at boot), you can add an entry to your **/etc/fstab** file. Here’s how to configure that: Open **/etc/fstab** in an editor ``` sudo vi /etc/fstab ``` Add an entry to mount your S3 bucket. The format should look like this: ``` s3fs#Bucket_Name /mnt/s3bucket fuse _netdev,nonempty,allow_other,url=https://idr01.zata.ai,use_path_request_style,passwd_file=/root/.passwd-s3fs 0 0 # For Mumbai, use url=https://bom01.zata.ai ``` Replace **`BUCKET_NAME`** with your S3 bucket name.

Now, check if the mount entry in /etc/fstab works properly by running the following command ``` sudo mount -a ``` Now, reload the daemon service ``` sudo systemctl daemon-reload ``` Now, reboot the system and check the mount directory. ``` df -h ```

Verify the Mount:- To confirm that the bucket is mounted, list the contents of your mount point.

sudo ls /mnt/s3bucket

# Connect Bucket with S3 Browser Object storage configuration with Buckets Navigate to Zata.ai and click on the bucket section to [create the bucket](https://docs.zata.ai/manage/bucket/create-bucket). Now click on the Access key section to create the [access and secret key](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). [Embedded Link](https://youtu.be/snJqhHzkvGo) After completing this step, proceed to the[ **browser**](https://s3browser.com/)**.**

To add a new account, click **Add New Account**.

* Fill in the Information:- **Display name** - Set a display name of your choice. * **Account type**- Select S3 Compatible Storage * **REST Endpoint**- Set it to - **** (Central India) or **** (Southern India) * **Access\_Key** -[ Access key](/manage/access-keys) that you created above. * **Secret\_key** - The secret key that you created above. Click on the advanced settings.

* After filling in the details, continue the process. * Click the **Advanced Settings ->** * Select the Signature Version:- **Signature V2** * Addressing model:- **Path style/ Virtual Hosted Style**

` After this click the`` `` `**`Add new account` ->**

* Now go to the **S3 Browser** ->

* Now you can see details of **Buckets and uploaded files ->** * Click any Bucket and see details about the uploaded files ->

* To upload new files, first click on the **bucket,** and then click on the upload button.

We can see uploading and status are running

Now back to your Zata account the check the bucket->

You can now download the object from the bucket to your local machine. Select bucket and choose object, and click on the download section.

Now Processing are running

Do you know more details about the S3 credentials follow these [**link**](/manage/access-keys) -> # Access Specific Bucket through Subuser in S3 Browser ## Step 1: Download and Install S3 Browser * Go to the official S3 Browser website and download the application. * Install S3 Browser on your system (Windows). * Open S3 Browser after installation is complete.

## Step 2: Get Subuser Credentials from Zata.ai * Log in to the Zata.ai dashboard. * Go to **Subusers → Subusers** from the left sidebar. * Locate the Subuser you want to connect and open the downloaded credentials file (Access Key and Secret Key).

> **Note:** If the credentials file is lost, a new key must be generated and the old key deleted, as the Secret Key cannot be retrieved again. * On the same Subuser Management page, look under the **ASSIGNED BUCKETS** column. Make sure to note down the exact name of the bucket assigned to this subuser, as you will need it later.

## Step 3: Add a New Account in S3 Browser * Open S3 Browser. * Click on **Accounts → Add New Account**. * A popup will open: Add New Account.

## Step 4: Configure Account Settings **Required Fields** * **Account Name:** Enter any recognizable name for this connection. * **Account Type:** Select “S3 Compatible Storage”. * **REST Endpoint:** Enter the Zata.ai S3-compatible endpoint URL (region: Indore). * **Access Key ID:** Enter the Access Key from the Subuser credentials file. * **Secret Access Key:** Enter the Secret Key from the Subuser credentials file.

## Step 5: Test and Save the Connection * Click on **Test Connection** to verify the credentials and endpoint are correct. * Once the connection is successful, click **Save/OK** to add the account. ## Step 6: Add the Bucket as an External Bucket > **Note:** A Subuser does not have permission to list all buckets. The bucket list will appear empty, so the specific bucket must be added manually as an External Bucket. * In S3 Browser, right-click on the buckets (or go to Buckets menu) and select **Add External Bucket**. * A popup will open asking for the bucket name. * Enter the exact bucket name that was assigned to the Subuser in Zata.ai. * Click **Add/OK**.

## Step 7: Select the Bucket to Access * Click on the bucket name from the list to open it. * The bucket contents (folders/files) will be displayed based on the permission assigned to the Subuser.

## Step 8: Perform Actions Based on Assigned Permission The available actions depend on the permission set for the Subuser on this bucket: | Permission | Allowed Action in S3 Browser | | ------------- | -------------------------------------------------- | | View Only | Browse and download files only | | Upload Only | Upload files to the bucket only | | View & Upload | Browse, download, and upload files | | Full Access | Upload, download, rename, and delete files/folders | ## Step 9: Troubleshooting Common Connection Issues * **Access Denied error:** Verify the correct bucket is assigned to the Subuser in Zata.ai. * **Connection failed:** Re-check the REST Endpoint URL and region (Indore). * **Invalid credentials:** Re-confirm Access Key and Secret Key are copied correctly with no extra spaces. ## Step 10: Final Verification * Confirm the bucket is visible and accessible in S3 Browser. * Confirm actions (view/upload/full access) work as per the assigned permission. * Subuser access through S3 Browser is now successfully configured. *Bucket access via Subuser using S3 Browser (integrated with Zata.ai, S3-compatible) is now successfully completed.* # Connect Bucket with Cyberduck Cyberduck is a free and open-source application designed for file transfer and cloud storage management. it simplifies the process of connecting your local computer to remote servers or cloud storage services. [Embedded Link](https://youtu.be/GgBAAkjVFWI) ## Prerequisites To download the **Cyberduck** and installation follow these [links](https://cyberduck.io/download/). Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow these click on [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). Now open the Cyberduck. Click on the Open connection to add the new account.

Click on the option, select the S3-compatible storage, and click on the more option.

After these, search the S3-Compatible storage and choose the option.

Choose the S3(Deprecated path style requests)

After these now back to the main console the add some details about the S3 account. Set the Server :- [REST the Endpoint](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3) Access\_key: Access key that you created above. Secret\_key:- The secret key that you created above. Click on the connect.

Let's see the bucket is visible that we created in the Zata.ai bucket section.

Now click on the upload option and upload the file. Alternatively, you can simply drag and drop it.

Lets see the data has been transferred from the local system to the bucket.

Navigate to the Zata.ai dashboard, select the Object storage section, choose the bucket, and check the data.

# Integration of Zata.ai with Rclone GUI **1. Introduction** Zata.ai provides **S3-compatible object storage** that allows users to store and manage unstructured data such as files, images, backups, and logs. Rclone is an open-source command-line program used to manage files on cloud storage systems. In this setup, we connect **Zata Object Storage with Rclone GUI** to manage buckets and objects through a graphical interface. *** **2. Prerequisites** Before starting the configuration, ensure the following resources are available: | Requirement | Description | | --------------- | -------------------------------------------- | | Zata.ai Account | Active account with access to object storage | | Bucket | At least one bucket created | | Access Keys | Access Key ID and Secret Access Key | | S3 Endpoint | Zata S3 service URL | *** **3. Create Zata Object Storage Bucket** Login to **Zata.ai dashboard** and create a new bucket. Steps: 1. Open Zata Storage Dashboard 2. Navigate to **Buckets** 3. Click **Create Bucket** 4. Enter bucket name 5. Select region 6. Create bucket Example bucket name: ``` testing-bucket-001 ``` *** **4. Generate Access Keys** To allow external tools like Rclone to connect, access keys must be generated. Steps: 1. Go to **Access Keys** 2. Click **Create Access Key** 3. Copy the following credentials: ``` Access Key ID Secret Access Key ``` These credentials are used for **authentication with the S3 API**. *** **5. Identify Zata S3 Service Endpoint** Zata provides region-specific S3 endpoints. For this setup the endpoint used is: ``` https://idr01.zata.ai (Central India) or https://bom01.zata.ai (Southern India) ``` Region: ``` us-east-1 ``` This endpoint is required to connect S3-compatible clients like **Rclone**. *** **6. Install Rclone** Download and install the latest version of Rclone from the official website: #### Step 1: Verify the Installation Open **Windows PowerShell** or any **Terminal** and run: ``` rclone version ``` If Rclone is installed successfully, the installed version will be displayed. #### Step 2: Launch the Rclone Web GUI Run the following command in **Windows PowerShell** or **Terminal**: ``` rclone gui ```

This starts the Rclone Web GUI locally and automatically opens it in your default web browser. #### Step 3: Create a New Remote 1. Open the **Remotes** tab.

2. Click **Add New Remote**.

#### Step 4: Configure the Remote Fill in the following fields: | Field | Value | | -------- | ------------ | | **Name** | `Zata Cloud` | | **Type** | `s3` | When you choose **Type = s3**, a list of S3-compatible providers will appear. Select Amazon S3 Compliant Storage Providers from the list.

#### Step 5: Enter Your Credentials Provide your Zata Cloud credentials. | Field | Value | | --------------------- | ------------------------------------ | | **Provider** | Select Other | | **Access Key ID** | Your Zata Access Key | | **Secret Access Key** | Your Zata Secret Key | | **Region** | `us-east-1` | | **Endpoint** | `idr01.zata.ai` (or `bom01.zata.ai`) |

#### Step 6: Configure Advanced Options Scroll down and expand **More Options**. Enable the following options: * ✅ **force\_path\_style** * ✅ **v2\_auth** > **Important** > > These two options **must be enabled** for successful integration with Zata Cloud.

#### Step 7: Create the Remote Scroll to the bottom of the page and click **Create Remote**.

#### Step 8: Verify the Connection If the configuration is correct, the new remote named **Zata Cloud** will appear in the **Remotes** list. Your Rclone integration with Zata Cloud is now complete and ready to use.

#### Configuration Summary

Setting	Value
Name	Zata Cloud
Type	s3
Provider	Other
Access Key	Your Access Key
Secret Key	Your Secret Key
Region	us-east-1
Endpoint	idr01.zata.ai (or bom01.zata.ai)
force_path_style	Enabled ✅
v2_auth	Enabled ✅

*** **7.** Create a Bucket and Upload Files After successfully configuring the **Zata Cloud** remote, you can create buckets and upload files directly from the Rclone Web GUI. #### Step 1: Open the Zata Cloud Remote Under **Remotes**, click **Zata Cloud**.

The existing buckets in your Zata Object Storage will be displayed.

#### Step 2: Create a New Bucket * Click **New Folder**.

* Enter a unique bucket name (for example, `testing-bucket-002`). * Click **OK**.

#### Step 3: Verify Bucket Creation After the bucket is created successfully, it will appear in the Explorer.

#### Step 4: Open the Bucket Click the newly created bucket to open it. Since it is a new bucket, it will initially be empty.

#### Step 5: Upload Files * Inside the bucket, click **Upload**.

* Select the file(s) you want to upload from your local system. * Click **Open** to begin the upload.

#### Step 6: Verify the Uploaded File After the upload completes successfully, the uploaded file will appear inside the bucket.

*** **8. Verify in Zata Dashboard** Now go to your **Zata dashboard** Open: Buckets → testing-bucket-002 You should see the uploaded file. This confirms: Rclone, Zata Object Storage working

*** **9. Conclusion** In this setup, **Zata Object Storage was successfully integrated with Rclone GUI**. This integration enables: * Easy file uploads * Bucket management * Backup storage Using Rclone with Zata provides a flexible and efficient way to interact with S3-compatible storage systems. # How to Transfer Data to Zata.ai Bucket Using Rclone # For Linux Server Rclone is an open-source command-line program that helps you manage, sync, and transfer files and directories across different cloud storage services and local systems. [Embedded Link](https://youtu.be/UojhD_jVZX8) ## **Prerequisites:** Select any Linux Operating system to perform these processes. We have chosen the operating system Ubuntu 22.04 Click on the link to Launch [instance](https://docs.neevcloud.com/neevcloud-products/computes/getting-started-launch-vms). For Zata.ai configuration: * Click on the Zata [login page](https://auth.zata.ai/realms/zata/protocol/openid-connect/auth?client_id=zatacloud_client\&redirect_uri=https%3A%2F%2Fmy.zata.ai%2F\&state=dd2b5305-f7f5-4922-8639-4b0c62060c2f\&response_mode=fragment\&response_type=code\&scope=openid\&nonce=646d8811-0870-469c-9045-9e13d0fdd1b3\&code_challenge=wRG6I1qb9wdmY4unvHhPYaYq5WWM-801w72AYyLi8xY\&code_challenge_method=S256). * Zata Bucket - See our [Bucket Creation Guide](https://docs.zata.ai/manage/bucket/create-bucket) * Zata Access & Secret Key Pair - See our [Access Keys Guid](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key)e * For more information about the [zata.ai](https://zata.ai/) After successfully launching the instance, follow these steps: ### Update && Upgrade the system. ``` sudo apt-get update -y sudo apt-get upgrade -y ``` Transfer Data to Zaat.ai Bucket Using Rclone on Ubuntu. ## Install and configure the rclone. Install the rclone. ``` sudo apt-get install rclone -y ``` ### To configure rclone for Zata.ai. Run the following command to configure ' **rclone** ' When you run the command above, follow these steps: Choose 'n' to create a new remote Name: Zata (Give the name of the remote)

Type of storage to configure: '4'; these values vary depending on the rclone version.

Choose your S3 Provider to choose '13' for Zata object storage(if there is no zata then you can select other), these numbers are very dependent on the rclone versions.

Get credentials from runtime (environment variables or metadata if no env vars). This only applies if access\_key\_id and secret\_access\_key are blank. Enter a boolean value (true or false). Press Enter for the default ("false"). Choose a number from below, or type in your value **env\_auth: true**

**Access & Secret key** - We have created the above in the zata.ai section.

Region to connect to. Leave blank if you are using an S3 clone and you don't have an area. Enter a string value. Press Enter for the default. Choose a number from below, or type in your value

Endpoint for S3 API. Required when using an S3 clone. Enter a string value. Press Enter for the default. Choose a number from below, or type in your value

Note that this ACL is applied when server-side copying objects as S3

Note that this ACL is applied only when creating buckets. After completing these processes, simply press Enter at each step

After this, all processes use the default configuration, so press Enter to continue. This is the remote configuration completed after following these steps:

Now complete the configuration to run these commands. ### To copy and move your data You can run it accordingly. ``` rclone copy zata:(bucket-name) --progress ``` ``` rclone move zata:(bucket-name) --progress ```

Zaat. Now, navigate to the zata.ai bucket section, open the bucket, and check if the data has been transferred.

Download or restore your server files from Zata to your local system. ``` rclone copy zata:(bucket_name) /path/to/local/directory ``` * `zata` Your rclone remote * `your-bucket-name`The name of the bucket in Zata.ai. * `/path/to/local/directory`Where do you want to restore the files

# For Windows Server [Embedded Link](https://youtu.be/SJLgph5giME) ### **Prerequisites:** Select any Window Operating system to perform these processes. We have chosen the operating system Windows Server 2022 Click on the link to launch the [instance](https://docs.neevcloud.com/neevcloud-products/computes/getting-started-launch-vms). Download rclone from the following [link](https://rclone.org/downloads/)

For Zata.ai configuration: * Click on the Zata [login page](https://auth.zata.ai/realms/zata/protocol/openid-connect/auth?client_id=zatacloud_client\&redirect_uri=https%3A%2F%2Fmy.zata.ai%2F\&state=dd2b5305-f7f5-4922-8639-4b0c62060c2f\&response_mode=fragment\&response_type=code\&scope=openid\&nonce=646d8811-0870-469c-9045-9e13d0fdd1b3\&code_challenge=wRG6I1qb9wdmY4unvHhPYaYq5WWM-801w72AYyLi8xY\&code_challenge_method=S256). * Zata Bucket - See our [Bucket Creation Guide](https://docs.zata.ai/manage/bucket/create-bucket) * Zata Access & Secret Key Pair - See our [Access Keys Guid](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key)e * For more information about the [zata.ai](https://zata.ai/) After successfully launching the instance, follow these steps: After successfully downloading rclone, extract the file.

Now navigate to the `C:\Let's` directory and create an `rclone` folder.

Now, move the downloaded content to the rclone directory.

Let's see if the content has been moved to the rclone directory.

**Add Rclone to the System PATH** Open Environment Variables Settings * Right-click This PC or My Computer → Click Properties * Click Advanced system settings * In the System Properties window, click Environment Variables Edit the PATH Variable * Under System variables, scroll and find Path, then click Edit * Click New and paste the folder path (not the `.exe`, just the folder). ``` C:\rclone ``` Click OK to close all windows Restart Command Prompt Close and reopen the Command Prompt, then test: Open your command prompt, navigate to the rclone directory, and run the command.

``` rclone version ``` Now, configure the rclone for Zata.ai Run the following command to configure ' **rclone** ' When you run the command above, follow these steps: Choose 'n' to create a new remote Name: Zata (Give the name of the remote)

Type of storage to configure: '4'; these values vary depending on the rclone version.

Choose your S3 compatible version to choose '34' for object storage, these numbers are very dependent on the rclone versions.

**Access & Secret key** - We have created the above in the zata.ai section.

Region to connect to. Leave blank if you are using an S3 clone and you don't have an area. Enter a string value. Press Enter for the default. Choose a number from below, or type in your value

Endpoint for S3 API. Required when using an S3 clone. Enter a string value. Press Enter for the default. Choose a number from below, or type in your value

Note that this ACL is applied when server-side copying objects in S3

Note that this ACL is applied only when creating buckets. After completing these processes, **simply press Enter at each step...**

After this, all processes use the default configuration, so press Enter to continue. This is the remote configuration completed after following these steps:

Now, complete the configuration to run these commands. #### To copy and move your data You can run it accordingly. ``` rclone copy zata:(bucket-name) --progress ``` ``` rclone move zata:(bucket-name) --progress ```

Now, navigate to the Zata.ai bucket section and check the bucket.

Download or restore your server files from Zata to your local system. * `zata` Your rclone remote * `your-bucket-name`The name of the bucket in Zata.ai. * `/path/to/local/directory`Where do you want to restore the files?

Now, check the restore folder on your local system.

# Connect S3 storage to CPanel ## Connect s3 storage to CPanel 1. Click to install cPanel on the VM. 2. Configure cPanel after installation. For access and secret access key Navigate to the Zata.ai panel and click on the Access section Create the [Access and secret keys](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). #### Creating a Bucket in Zata.ai Navigate to the dashboard to click the bucket and create the bucket.

Navigate to WHM portal > Backup configuration > Additional Destinations

After to set the key, Click Save Destination

# Backup your WordPress Site to Zata.ai S3 storage with using Updraft plugin. After installing and configuring your **WordPress**. To connect install and activate the **Updraft backup** follow these steps. Navigate to the WordPress dashboard, click on "**Plugins**," and then click on "**Add New**."

Search for Updraft and click "**Install Now**".

After installing to activate the **Updraft .**

Click the button and open the settings.

Next, click on the settings and select the **S3 compatible option.**

Now fill in the **S3/EC2 credentials** for accessing the storage bucket For **access and secret keys** follow this [**link**](/manage/access-keys)**.** S3 Location: Give the name of the bucket to create a bucket to follow below these [**steps**](/manage/bucket/create-bucket)**.** 1. Navigate to the **Object Storage section.** 2. Select "**Create Bucket**" and enter your desired bucket name. 3. Confirm to create the bucket. S3 End point: - **idr01.zata.ai** (Central India) or **bom01.zata.ai** (Southern India) Bucket access style: Default - **path style** Signature version: default- **SigV4** After fill all the details click on the **save changes.**

Now, go back to **Updraft Backup/Restore** and click on "**Backup Now"**.

The backup has been successfully created.

# Connect S3 Drive to Zata.ai S3 Drive allows users to transform compatible storage backends, such as S3 and WebDAV, into personal encrypted file storage solutions. It offers drive mounting, syncing, backup, file versioning, and search capabilities. Install and configuration To Install the S3 drive follow these links Now we are performing on the Windows operating system After installation of the S3 drive to mount on the zata.ai Create an account using mail and password

After login the S3 drive click on the manage account

In the account section, we have two options the first is s3 (remote basic) and the second is Rclone, where we define the cloud provider details

Now configure the Rclone and set the cloud storage details

Rclone config and click on the add/ ``` "s3": { "access_key_id": "", "secret_access_key": "", "endpoint": "https://idr01.zata.ai", "provider": "Other", "region": "CentralIndia", "type": "s3" }, ``` > **Note:** For Mumbai region, use `"endpoint": "https://bom01.zata.ai"` and `"region": "SouthIndia"`. Now that the account has been added, click on the account and see the cloud buckets.

Now click on the sync to connect the zata.ai

Now click on the ( + ) to add the account

Now configure the sync remote host to the destination host Now click on the source remote

Now select the source path and local folders

After selecting the remote and local you will get the source path

Now, the destination configuration path for selecting the 'TO'

Choose S3 and select the bucket.

After selecting the destination path, you will get the destination path with the s3 bucket name

In this section, you have to configure the mode and sync timing and click on the save

Now completed the configuration to check the sync process

Let's see all the data copied into the s3 storage bucket Now bucket the local folder

Now check the destination host

# Mount Bucket to Local system using the TntDrive TntDrive is a software tool that allows you to mount S3 Buckets as a network or removable drive on Windows. This means you can access your S3 files as if they were stored on your local computer. It's designed to simplify working with S3 buckets, making managing and accessing your cloud storage easier. ## **Prerequisite** Zata.ai Cloud storgae account * Zata.ai Bucket - See our [Bucket Creation Guide](https://docs.zata.ai/manage/bucket/create-bucket) * Access & Secret Kye Pair - [See our Access Keys Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key) Setup the TntDrive on the Windows server Download the TntDrive following the [link.](https://tntdrive.com/download/tntdrive-6-0-9.exe) Now follow the Download the instructions Navigate to the download folder and Install the TntDrive

Click for Accept the agreement to click on the next

Select the destination location and click on the next

Select the additional task you would like to perform while installing Tntdrive and click on the next

To complete the installation to set TntDrive Open the TntDrive and set the configuration Click on the Account section to add a new account

Enter the new account details and click on the Add new account Account Name: zata.ai Account Type: Amazon S3 Compatible Storage REST Endpoint: (Central India) or (Southern India) Access & Secret Key:- Follow these [link](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key) Click on the Use Secure transfer (SSL/TLS)

Now process to click on the Advances S3-Compatible storage settings Select the signature version: Signature V2 Addressing model: Path style Now click on the close And now click on the Add new account Now check the account has been created

Now next process is to Add a new Drive

Specify the drive properties and click the Create Account Zata.ai. Select the bucket and give the folder a name similar to the map

When you click on the bucket area, you will see lists of buckets you have created within the zata.ai

After selecting the Account, Bucket Name, and Mapped driver and click on the Add New Drive

Now you can see that the driver has been mapped correctly

Check that the driver has been connected by navigating to Windows on this computer.

Navigate to the Zata.ai storage panel to check the bucket is empty

Now transfer data locally to Zata.ai bucket I have stored the data on the locally attached drive. Please check the Zata.ai bucket now

Now navigate to the Zata.ai storage and check the bucket

# How to Integrate QNAP NAS storage and Backup to Zata.ai A QNAP NAS (Network Attached Storage) is a specialized device made by QNAP Systems. It's designed to store, manage, and share data over a network. Prerequisites Zata.ai Bucket - [Bucket Create Guide](https://docs.zata.ai/manage/bucket/create-bucket). Access and Secret Key Pair - [Access Key Guide](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key). REST Endpoint to follow these, click on the [links](https://docs.zata.ai/manage/service-urls-for-zata.ai-s3). After successfully setting up the QNAP system, log in with your username and password.

You may now proceed with the following steps to configure the backup and restoration process. Navigate to the App Center and install **HBS 3 Hybrid Backup Sync** to proceed with backup configuration.

Open the App Center, search for **HBS 3 Hybrid Backup Sync**, and proceed with the installation.

Now, back to the **Backup/Sync** section and launch **HBS 3 Hybrid Backup Sync** to begin configuration.

Navigate to **Storage Spaces**, then select and create a new storage space as needed.

Select **S3-compatible storage** from the available storage options.

Complete the process of creating a storage space as shown in the interface: **Fill in the Required Details:** * **Name:** Enter a descriptive name for your storage space (e.g., "Amazon S3 & S3 Compatible 1"). * **Service Provider:** Select "S3 Compatible" from the dropdown menu. * **Server Address:** Input the server address (e.g., `idr01.zata.ai` or `bom01.zata.ai`) * **Signature Version:** Choose the appropriate signature version (e.g., `v2`). * **Access Key:** Enter your access key. * **Secret Key:** Enter your secret key.

Now back to the **Backup & Restore** or **Backup/Sync** section in your application interface. Click on **Create** and then select **New Backup Job**. This will open the backup job creation wizard

Choose the folders or files you wish to back up. When selecting a folder, all files and subfolders within it will be included automatically.

Select the storage space you previously configured (e.g., your S3-compatible storage). Click **Select** to confirm your choice.

While setting up a bucket on the Zata.ai dashboard, specify and select the bucket name accordingly.

Now select the destination folder

Verify the details, and then proceed to the next step by clicking Next.

Set up your preferred schedule in the schedule section, and click 'Next' to continue.

Configure the rules, such as enabling filters.

Carefully review the settings, and then click Create.

Backup is now successful.

# Proxmox Backup Server Integration with Zata.ai S3 Storage **Overview** This document describes the procedure to configure **Proxmox Backup Server (PBS)** to store backups on **Zata.ai S3-compatible Object Storage**. The integration allows virtual machine and container backups from Proxmox environments to be securely stored in scalable object storage. **Prerequisites** Before starting the setup, ensure the following requirements are met: * Proxmox VE installed and running * Proxmox Backup Server installed * Internet connectivity * Zata.ai object storage account * S3 bucket created * Access Key and Secret Key generated 1. **Create Object Storage Bucket** **Step 1:** Login to the Zata.ai dashboard. **Step 2:** Navigate to: ``` Object Storage → Buckets ``` **Step 3:** Click **Create Bucket** **Step 4:** Enter bucket name Example: ``` proxmox-backups ``` **Step 5:** Click **Create** **5. Generate Access Credentials** **Step 1:** Navigate to: ``` Object Storage → Access Keys ``` **Step 2:** Click **Create Key** **Step 3:** Copy the generated credentials: ``` Access Key ID Secret Access Key ``` These credentials will be used to authenticate PBS with S3 storage. 2. **Access Proxmox Backup Server** Open the PBS web interface in a browser: ``` https://:8007 ``` Login using: ``` Username: root@ Password: server password ```

3. **Configure S3 Endpoint** **Step 1:** Navigate to: ``` Configuration → S3 Endpoints ``` **Step 2:** Click **Add** **Step 3:** Enter the following configuration: ``` S3 Endpoint ID : zata-reg Endpoint : idr01.zata.ai (or bom01.zata.ai for Southern India) Port : 443 Region : us-east-1 Access Key : Secret Key : Path Style : Enabled ``` **Step 4:** Click **OK**

4. **Create Local Cache Directory**\ PBS requires a local cache directory when using S3 storage. **Step 1** Open: ``` Administration → Shell ``` **Step 2:** Run the following command: ``` mkdir -p /mnt/pbs-cache ``` **Step 3:** Verify directory creation: ``` ls /mnt ``` Expected output: ``` pbs-cache ```

*** 5. **Create Datastore** **Step 1** Navigate to: ``` Datastore → Add ``` **Step 2** Configure datastore settings: ``` Name : zata-backups Datastore Type : S3 (tech preview) Local Cache : /mnt/pbs-cache S3 Endpoint ID : zata-reg Bucket : proxmox-backups GC Schedule : daily Prune Schedule : daily ```

6\. **Verify Datastore Configuration** After successful configuration, the datastore will appear under: ``` Datastore → zata-backups ``` The PBS dashboard will display storage usage.

*** **11. Conclusion** The Proxmox Backup Server has been successfully integrated with Zata.ai S3-compatible object storage. This setup enables secure, scalable, and centralized backup storage for Proxmox environments. Backups can now be scheduled and stored in object storage for disaster recovery and long-term retention. # FAQ # What are the regions of Zata.ai? | Zone Description | State | Status | Country | | ------------------- | -------------- | ----------- | ------- | | Central India Zone | Madhya Pradesh | Active | India | | Southern India Zone | Maharashtra | Active | India | | Northern India Zone | Uttar Pradesh | Coming Soon | India | # What is the billing process for Zata.ai ? Our billing cycle is based on a date-to-date system, where storage upgrades are processed within the same billing cycle. However, to ensure a seamless transition and avoid any transaction gaps, we adhere to the following guidelines: Upgrade storage: Storage upgrades are allowed during the billing cycle, and the changes will be reflected in the next billing cycle. Transaction Gap: To prevent any discrepancies, a 48-hour transaction gap will be maintained between the storage upgrade and the new billing cycle. This ensures that all transactions are accurately accounted for and billed accordingly. No Downgrade During Billing Cycle: Once the storage upgrade is processed, it is not possible to downgrade during the same billing cycle. Upgrade Process: When upgrading your storage plan, we understand that you shouldn't be charged for the entire upgraded plan for the remaining days of the billing cycle. To ensure a fair and transparent process, we prorate the upgraded storage plan charges based on the remaining days of the billing cycle # What happens if I miss a Payment ? Service Suspension:- If the payment is not received within the specific deadline, your account may be temporarily suspended, and access to our services may be restricted Account Re-Activation: Once the payment is received, you account will be re-activated, and access to our services will be restored. # How do I request access to use storage endpoints in a browser or SDK? ### Using Our Storage Endpoints From SDKs or Browsers We support customers who want to connect directly to our S3-compatible storage endpoints from their own applications or SDKs. Because this involves CORS and security considerations, we don’t allow all external domains by default. How to request access If you need your application or SDK to call our storage endpoints directly (for example, from a browser or mobile app): #### Open a support ticket with the following details: The domain(s) or subdomain(s) your application will use (e.g., ). Whether you require read-only access (GET/HEAD) or read/write access (PUT/POST/DELETE). Any specific headers your SDK or app sends in requests (if different from standard AWS SDK headers). Our team will review your request and configure the necessary CORS rules and access controls for your tenant. #### Security notes We do not recommend embedding long-lived access keys in browser or mobile apps. Please use temporary credentials or presigned URLs whenever possible. CORS rules will only be opened for the exact origins you request (wildcards such as \* are not permitted without review). Each customer must use their own isolated credentials/policies — shared keys are not supported. # How can I get support for billing-related issue? Having any issues? Reach out to us by email at ** .** # What are the terms and conditions for using Zata.ai services? For information regarding the usage of Zata.ai services, please refer to the [Legal ](https://zata.ai/zataprivacypolicies.pdf)section on their website. # Where can I find additional information on pricing and billing? You can check the information related to pricing and billing on the Zata.ai dashboard # Support The Support section helps users get assistance with technical, billing, and account-related issues. It allows users to search for solutions, submit new support requests, and track existing tickets. If you have any inquiries or need technical assistance, please contact us at [**solutions@zata.ai**](https://mail.google.com/mail/?view=cm\&fs=1\&to=solutions@zata.ai\&su=Custom%20Plan%20Request\&body=Hi%20there). Our dedicated support team is always available to help you. # Raise a Support Ticket The **Submit a Ticket** page is used to raise a new support request. Users can: * Enter their email in the **Requester** field. * Add a clear **Subject** describing the issue. * Select the **Type** of issue (Technical, Billing, Account, etc.). * Choose the **Priority** based on urgency. * Select the **Product** (e.g., Zata AI). * Describe the issue in detail in the **Description** box. After submitting, the ticket is sent to the support team for review and resolution. # View and Track Tickets The **Tickets** page allows users to manage and track all their submitted support tickets. Users can: * View all existing tickets. * Check ticket status such as *Open*, *Pending*, or *Closed*. * Search tickets using keywords. * Filter tickets based on status. * Sort tickets by creation date. * Export tickets for record keeping or reporting. This page helps users stay updated on the progress of their issues and communicate effectively with the support team. # Announcements and Updates The Announcements and Updates section keeps you informed about changes to the Zata.ai platform. It is the official place to find pricing revisions, new feature releases, service notices, and other updates that may affect your account. This section includes: * Pricing and plan changes * New feature and region announcements * Planned maintenance and service notices * Policy updates Announcements are listed with their effective dates so you can review what is changing and when it takes effect. # Zata Pricing Update — October 2026 Revised pricing for Zata Object Storage, effective 1 October 2026 This announcement outlines the upcoming pricing changes for Zata Object Storage, effective October 1, 2026. The revised pricing reflects the evolving costs of infrastructure and operations while allowing us to continue investing in the reliability, performance, security, and scalability of our storage services. A summary of the current and new pricing is provided below. Customers can review the current and revised pricing below. ## Updated Storage Pricing | Plan | Storage Capacity | Current Price / Month | New price (w\.e.f. Oct 1st) | | --------------- | ---------------- | --------------------- | --------------------------- | | **Basic** | 1 TB | ₹599 | **₹699** | | **Standard** | 5 TB | ₹2,970 | **₹3,470** | | **Pro** | 10 TB | ₹5,880 | **₹6,880** | | **Business** | 25 TB | ₹14,550 | **₹17,050** | | **Enterprise** | 50 TB | ₹28,800 | **₹33,800** | | **Enterprise+** | 100 TB | ₹57,000 | **₹67,000** | | **Custom** | 100 TB+ | Custom | Custom | > **Note** All prices are exclusive of GST. An 18% GST will be applicable separately. ## When Does the New Pricing Take Effect? The revised pricing will be **effective from October 1, 2026**. The current pricing will remain applicable until **September 30, 2026**. ## Frequently Asked Questions ### 1. When will the new pricing become effective? The revised Zata storage pricing will be effective **October 1, 2026**. ### 2. Which plans are affected? The pricing update applies to the **Basic**, **Standard**, **Pro**, **Business**, **Enterprise** and **Enterprise+** storage plans. Custom plans for 100 TB+ continue to be quoted separately. ### 3. Are the prices inclusive of GST? No. All prices listed above are **exclusive of GST**. An 18% GST will be applicable separately. ### 4. What if I require more than 100 TB? For storage requirements above 100 TB, Zata offers custom plans. Please contact us at for more details. ## Need Help? For pricing enquiries or storage requirements: * **Email:** * **Phone:** 1800-309-1433