Overview

GitProtect supports the majority of the most popular cloud service providers compatible with S3:

Sending backup tasks to S3 cloud storage has a limit (buffer). The default buffer value is 128 MB, which limits both the maximum data size and the minimum internet speed. If your network environment or S3 endpoint has no additional restrictions, the minimum required upload speed is ~0.64 Mbit/s.

GitProtect supports S3-type immutable storage as a backup location. This feature is available for selected storages supported by GitProtect, such as AWS, Wasabi, and Backblaze B2. Datastores of this type allow you to freely save and read data, but modification and deletion are only possible after meeting the bucket's retention policies.

Advantages:

Protection against ransomware and other threats (cyber attacks) — files in immutable storage are read-only and immune to loss, accidental deletion, corruption, and other issues that could compromise your data.
Prevention of accidental file deletion — when access to important or critical data is shared, the risk of deletion or modification increases, which immutable storage feature prevents.
Preservation of file authenticity — ensures data accuracy by preventing modification or manipulation of uploaded files.
Compliance with legal regulations — meets requirements for storing confidential data (e.g., payment or medical records).

Adding new storage

This article describes the process of setting up an S3-compatible bucket as storage in GitProtect.

Open the Storages section and click Add storage button.

The Add storage sidebar will appear—use it to enter the name of your new storage in the Add storage name field (step 1), then click the arrow next to the Storage type section (step 2) to expand the list of available storage types.

Scroll down the list and select the S3 storage option.

After selecting storage option, the system will display additional sections, including: Authentication data, Service URL, Bucket name, and Optional description.

Copy the access key ID and secret access key from your S3-compliant storage provider, paste the access key ID to the corresponding field, and click Select or add secret access key to open the Password Manager menu and add your copied secret key to your bucket.

In the Service URL field, enter the URL provided by your S3-compliant storage provider.

Enter the bucket name in the Bucket name field and proceed to the next step.

Ensure that the browsing machine—a device with an active license and the GitProtect worker installed—can access your S3 bucket. To use a different device, click Change next to the Browsing machine at the bottom.

Review your settings and click the Save button to add the storage to GitProtect. Refresh the page to see the newly added storage on your storages list.

Adding new storage

This article describes the process of setting up an S3-compatible bucket as storage in GitProtect.

Open the Storages section and click Add storage button.

Scroll down the list and select the S3 storage option.

After selecting storage option, the system will display additional sections, including: Authentication data, Service URL, Bucket name, and Optional description.

In the Service URL field, enter the URL provided by your S3-compliant storage provider.

Enter the bucket name in the Bucket name field and proceed to the next step.

Review your settings and click the Save button to add the storage to GitProtect. Refresh the page to see the newly added storage on your storages list.

To get the access key ID and secret access key, visit your S3-compatible platform and create a new access key.

Overview

For cloud storage backup to S3-compliant systems, GitProtect suggests a minimum upload speed of 2.5 Mbit/s.

This feature is not enabled by default.

S3 compliant

Overview

Adding new storage

Adding new storage

Overview

Configuration and limitation

Immutable storage

S3 compliant