☁️
Zus Docs
  • About Züs
  • System
    • Providers and Services
      • Miner
      • Sharder
      • Blobber
      • Validator
      • Authorizer
      • Node Locator (0DNS)
    • Storage
      • Architecture and Data Management
      • Protocol
        • Allocations
        • Reference Objects
        • Challenges
        • Write Markers
          • Chain Hashing
          • Two Commit
        • Blobber Repair Protocol
      • ZS3 Server
        • Backup, Recovery and Replication
        • Encryption and Compression
        • S3FS Setup and Usage
        • Backup & Recovery with Restic on Blimp + ZS3 Server
        • Backup & Recovery with Veeam on Blimp + ZS3 Server
      • File Operations
        • Upload
        • Download
        • File Sharing
        • Partial Error Recovery
        • Streaming
        • Rent a Blobber
    • Smart Contracts
      • Storage S.C.
      • Miner S.C.
      • ZCN S.C.
      • ERC-20 S.C.s
      • Bridge Protocol
    • Blockchain & Consensus
      • Entities
    • User Authentication and Wallet Management System
      • OKTA Integration
      • Key Management System (KMS)
  • APIs
    • 0DNS API
    • JS API
    • Mobile API
  • CLIs
    • Storage CLI
      • Quickstart
      • Configuring the tool
    • Wallet CLI
      • Wallet Configuration
      • Quickstart
      • Configuring the tool
  • SDKs
    • Go SDK
      • GO SDK Microservices
    • JS SDK
  • Tokenomics
    • Staking
    • Reward & Penalty
  • ✨Züs Apps
    • 🗝️Vult
      • Getting Started
        • Web
        • Mobile
      • Vult AI
        • Batch Processing
        • Memory Retention
        • Technical Implementation
        • Architecture Overview
      • Login / Register
      • File Management Pages
      • File Sharing
      • Storage Management Dashboard
      • Storage Maintenance and Troubleshooting
      • Züs Subscription
      • Wallet Management
      • Refer a friend
      • Settings
    • 🏗️Blimp
      • Getting Started
      • Login / Register
      • Configure Storage
        • Create Standard Storage Allocation
        • Create Enterprise Allocation
        • Create S3 Server Allocation
        • Create Cloud Migration Allocation
        • Allocation Maintenance and Troubleshooting
      • File Management Pages
      • File Sharing
      • Manage Allocations
      • Upgrade Storage
      • Blimp Vault
      • Refer a friend
      • Settings
      • Launching ZS3 Server
      • Using CLI to backup files into Blimp + ZS3 Server
    • 🏠Chimney
      • Getting Started
      • Login / Register
      • Create New Deployment
      • Manage Your Deployments
      • Homepage
      • Staking Dashboard
      • Rank Dashboard
      • Monitor Dashboard
      • Stats Dashboard
      • Logs Dashboard
      • Wallet Dashboard
      • Operations on your Deployments
      • Restricted Blobbers
      • Settings
        • Manage Profile
        • Wallet Settings
        • Update Blobber Settings
        • Update Blobber Version
        • Refer a friend
        • Help
    • 🌐Atlus
      • Getting Started
      • Home page
      • Service Providers Page
      • Charts Page
        • Market Charts
        • Network Charts
        • Storage Charts
      • Blockchain Page
      • Server Map Page
      • Storage Explainer Page
      • Details Pages
        • Block Details Page
        • Transaction Details Page
        • Wallet Details Page
        • Miner Details Page
        • Sharder Details Page
        • Blobber Details Page
        • Validator Details Page
        • Authorizer Details Page
        • Allocation Details Page
      • Appendix: Common Components
    • ⚡Bolt
      • Getting Started
        • Web
        • Mobile
      • Login / Register
      • Sign In with external wallet
      • Staking Dashboard
      • Staking/Unstaking a provider
      • Claiming Rewards
      • Send/Receive ZCN tokens
      • Buy ZCN
      • Deposit/Withdraw ZCN tokens
      • Activity Dashboard
      • Refer a friend
      • Settings
  • Releases
    • Hardfork
Powered by GitBook
On this page
  • Step 1: Install MinIO Client
  • Step 2: Set Up mc Alias
  • Step 3: Create a Bucket
  • Step 4: Upload Files with Compression
  • Step 5: Test Encryption
  • Notes
  1. System
  2. Storage
  3. ZS3 Server

Encryption and Compression

PreviousBackup, Recovery and ReplicationNextS3FS Setup and Usage

Last updated 3 months ago

This section guides you through configuring encryption and compression for S3-compatible storage using the MinIO Client (mc).

Encryption ensures data security, while compression optimizes storage usage.

Step 1: Install MinIO Client

The MinIO Client allows you to interact with your MinIO server. The MinIO Server provides an S3-compatible API and supports core S3 features.

The MinIO Server provides an S3-compatible API and supports core S3 features. Choose one of the following installation methods for Linux:

RPM (RHEL-based Systems)

  • Download the latest stable MinIO RPM package. Install the package using dnf:

wget https://dl.min.io/server/minio/release/linux-amd64/archive/minio-20241218131544.0.0-1.x86_64.rpm -O minio.rpm
sudo dnf install minio.rpm

DEB (Debian/Ubuntu Systems)

  • Download the appropriate .deb package from the MinIO Downloads Page. Install the package using dpkg:

wget https://dl.min.io/server/minio/release/linux-amd64/archive/minio_20241218131544.0.0_amd64.deb -O minio.deb
sudo dpkg -i minio.deb

Binary Installation (Universal Method)

  • Download the MinIO Server binary. Make the binary executable and move the binary to a directory in your system PATH:

wget https://dl.min.io/server/minio/release/linux-amd64/minio
chmod +x minio
sudo mv minio /usr/local/bin/

Installing MinIO Client (mc)

The MinIO Client allows command-line interaction with your MinIO server.

  1. Download the MinIO Client binary:

    wget https://dl.min.io/client/mc/release/linux-amd64/mc
  2. Make the binary executable:

    chmod +x mc
  3. Move the binary to a directory in your system PATH:

    sudo mv mc /usr/local/bin/mc
  4. Verify the installation:

    mc --version

Step 2: Set Up mc Alias

  1. Set an alias for your server:

    mc alias set zcn https://<BLIMP_DOMAIN> <ACCESS_KEY> <SECRET_KEY> --api S3v2
    • Replace <BLIMP_DOMAIN> with the domain link from the Blimp output.

    • Replace <ACCESS_KEY> and <SECRET_KEY> with your credentials.

    Example:

    mc alias set zcn https://blimpibh5l.zus.network shahnawaz rootroot --api S3v2
  2. Verify the alias setup by listing buckets:

    mc ls zcn

Step 3: Create a Bucket

  1. Create a bucket for storing encrypted and compressed data:

    mc mb zcn/encryption-compression
  2. Confirm the bucket creation by listing the contents:

    mc ls zcn

Step 4: Upload Files with Compression

  1. Copy files or directories recursively to the bucket, applying compression:

    mc cp --recursive ../mc/docs zcn/encryption-compression/

    Example commands:

    mc cp --recursive ../mc/docs zcn/encryption-compression/
    mc cp --recursive ../mc/buildscripts zcn/encryption-compression/
    mc cp --recursive ../mc/primary zcn/encryption-compression/
  2. List the contents of the bucket to verify the upload:

    mc ls zcn/encryption-compression/

Step 5: Test Encryption

  1. Ensure that the uploaded files are encrypted on the server by verifying through:

    mc stat zcn/encryption-compression/<FILE_NAME>
    • Replace <FILE_NAME> with the name of any uploaded file.

    • Check the metadata to confirm encryption.

  2. To download and decrypt, use:

    mc cp zcn/encryption-compression/<FILE_NAME> /local/path/

Notes

  • Recursive Upload: Use the --recursive flag to upload entire directories.

  • Bucket Verification: Always verify the presence of the bucket and its contents after each operation.

  • Compression: Compression is applied automatically during file transfer. Ensure that the server supports compression for optimal results.

  • Encryption: Encryption is configured at the server level. Confirm the settings in your ZS3Server configuration to enable encryption.

For other operating systems, refer to this .

resource
Video Tutorial