Managing Object Storage Buckets & Objects

LYNIO Object Storage (lynio-s3) provides an industry-standard, S3-compatible object storage platform designed for high throughput, petabyte-scale capacity, and high-performance direct streaming. Whether you are storing large virtual machine images, database dumps, application assets, or static media, Object Storage delivers durable and cost-effective cloud persistence.

Core Concepts & Namespaces

Unlike traditional hierarchical file systems, Object Storage organizes data into flat namespaces called Buckets.

• Isolated Tenant Namespaces: Bucket names are strictly isolated per tenant namespace. Two distinct tenants can both create a bucket named backups without collision.
• S3 Protocol Compatibility: The platform natively supports the Signature v4 (SigV4) authentication standard, allowing you to use standard S3 SDKs, the AWS CLI, rclone, or Cyberduck without modification.
• Storage Classes: Every bucket is backed by two operational tiers:
  • STANDARD (Hot Pool): Active, high-performance storage pool designed for frequent access and maximum throughput.
  • ARCHIVE (Cold Pool): Cost-effective compressed and deduplicated storage for long-term retention.

Creating an Object Storage Bucket

To create a new bucket in the LYNIO Console:

1. Navigate to Storage > Object Storage in the sidebar.
2. Click Create Bucket in the top right corner.
3. Configure the bucket options:
   • Bucket Name: Enter a unique name within your tenant. Bucket names must be between 3 and 63 characters long and contain only lowercase letters, numbers, and hyphens (-).
   • Region: Select your desired deployment region.
   • Default Storage Tier: Select STANDARD for active workloads or ARCHIVE for immediate cold storage.
   • Auto-Tiering: Enable automatic transition to move unaccessed objects to the ARCHIVE tier after a defined period (default is 30 days).
   • Versioning: Toggle object versioning to preserve previous revisions of updated or deleted files.
   • Retention Policy: Set the number of days to retain non-current historical versions before automatic pruning.
   • Access Control: Select private (default) or public-read for public media hosting.
4. Click Create Bucket.

Navigating the Object Explorer

Clicking on any bucket in the table opens the Object Explorer, providing interactive file management:

• Prefix & Folder Browsing: Click into folders to navigate object keys hierarchically. Use the breadcrumb bar at the top to navigate back to parent directories.
• Creating Folders: Click New Folder, enter a folder name, and confirm. LYNIO creates a zero-byte prefix marker ending with /.
• Drag-and-Drop Uploads: Drag files directly from your desktop onto the explorer area, or click Upload Objects. The upload manager supports multi-file queues and displays real-time progress bars.
• Large File & Multipart Streaming: Files up to 50+ GB are automatically streamed to the node via chunked multipart uploads without consuming memory on the management server.

Managing Object Versions

When versioning is enabled on a bucket:

1. Modifying or re-uploading an existing file key creates a new version while keeping previous revisions intact.
2. In the Object Explorer, click the Options menu (...) next to an object and select Version History.
3. The drawer displays all historical versions, their unique Version ID, file size, creation timestamp, and storage tier (STANDARD or ARCHIVE).
4. You can directly download, rehydrate, or permanently delete specific versions from this view.

Generating Temporary Presigned URLs

Presigned URLs allow you to share read access to private objects with third parties or web clients without exposing your IAM credentials or bucket keys.

To generate a presigned download link:

1. In the Object Explorer, click the Options menu (...) next to the target object.
2. Select Presigned URL.
3. Choose the URL expiration duration (e.g., 15 minutes, 1 hour, 24 hours, or 7 days).
4. If versioning is enabled, optionally select a specific historical version ID.
5. Click Generate Link and copy the resulting signed HTTPS URL.

The generated URL carries an encrypted cryptographic signature and will automatically expire once the specified lifetime passes.

Bucket Access Permissions

For programmatic access via tools like AWS CLI, Python boto3, or Go, see the Connecting AWS CLI and S3 Clients guide.