Getting Started with Zero-Egress S3 Storage

Nyota Drive provides enterprise S3-compatible cloud object storage built on high-availability edge infrastructure. Unlike AWS S3—which penalizes growing businesses with $0.08 to $0.12/GB bandwidth transfer fees every time users download files—Nyota Drive guarantees KES 0.00 egress bandwidth fees forever.

This guide explains how Nyota Drive works under the hood, provides code samples for popular SDKs (Node.js @aws-sdk/client-s3, Python boto3, and MinIO), and walks you through creating your first storage bucket.

1. How It Works Under the Hood

Nyota Drive implements the standard AWS S3 REST API specification. You can use your existing AWS SDKs, backup tools (Rclone, Cyberduck), and CI/CD deployment pipelines simply by updating your endpoint URL and credentials:

┌────────────────────────────────────────────────────────────────────────┐
 │                      YOUR APPLICATION / BACKEND                        │
 │           (Node.js / Python / Go / Next.js / AWS SDK / Boto3)          │
 └───────────────────────────────────┬────────────────────────────────────┘
                                     │
                 S3 API Endpoint: https://drive.nyotaimara.com
                 Credentials: S3 Access Key & Secret Key
                                     │
                                     ▼
 ┌────────────────────────────────────────────────────────────────────────┐
 │                      NYOTA DRIVE OBJECT STORAGE                        │
 │  - Zero Egress Bandwidth Fees ($0.00 download transfer costs)         │
 │  - 100,000 Class A (writes/commits) free monthly                       │
 │  - 1,000,000 Class B (reads/downloads) free monthly                    │
 │  - 99.999999999% (11 9's) Data Durability & AES-256 Encryption         │
 └────────────────────────────────────────────────────────────────────────┘

2. S3 Connection Parameters Matrix

Use these global S3 connection parameters when initializing any storage client:

3. Developer SDK Integration Examples

Read our developer docs at https://docs.nyotaimara.com/docs/2-nyota-drive

4. Step-by-Step: Creating Your First Storage Bucket

1. Log in to the Nyota Drive Web Console.
2. Click "Create Bucket" in the top-right corner.
3. Enter a bucket name (must be lowercase alphanumeric characters and hyphens, e.g., company-media-archive).
4. Select your Bucket Visibility:
5. • Private (Default): Objects are locked behind authentication and short-lived pre-signed URLs.
   • Public: Assets are routed globally via Cloudflare CDN edge nodes (assets.drive.nyotaimara.com).
5. Click "Initialize Bucket".

5. Common Pitfalls & How to Troubleshoot

Pitfall A: "My S3 Client returns SignatureDoesNotMatch or 403 Forbidden."

• The Cause: Your SDK is attempting to use legacy S3 V2 signatures or has forcePathStyle disabled.
• The Resolution: Ensure your client configuration sets forcePathStyle: true and uses AWS Signature Version 4.

Pitfall B: "I deleted files, but my available storage quota hasn't freed up."

• The Cause: Deleted files are moved to the Trash Bin and retained for 30 days for accidental recovery.
• The Resolution:
• 1. Navigate to drive.nyotaimara.com/trash.
  2. Click "Empty Trash" to physically purge objects and immediately release storage quota.

Related Support Guides & Links

• Public vs. Private Buckets & CDN Edge Caching
• Fixing S3 SignatureDoesNotMatch & Presigned Expirations
• Creating Password-Protected Share Links
• Direct Nyota Drive Web Console