Nami Cloud’s S3-compatible API allows you to migrate from AWS S3 or other cloud providers with zero code changes, bringing Web2 familiarity to Web3 infrastructure.

​
Why S3 Compatibility Matters

One of the biggest hurdles for organizations moving from Web2 to Web3 has been compatibility. Nami Cloud eliminates this barrier with a fully S3-compatible API, allowing you to plug into decentralized storage using the same tools and workflows you use with traditional cloud providers.

​
Benefits of S3 Compatibility

  • Zero Learning Curve: Use familiar AWS SDKs, CLI commands, and third-party tools
  • Instant Migration: Move from AWS S3 with just endpoint configuration changes
  • No Code Rewrites: Existing applications work without modification
  • Industry Standard: Leverage the most widely adopted object storage API

​
Supported S3 Operations

Nami Storage supports all standard S3 operations out-of-the-box:

​
Bucket Operations

Create Bucket

PUT /{bucket}

Delete Bucket

DELETE /{bucket}

List Buckets

GET /

Bucket Location

GET /{bucket}?location

​
Object Operations

Put Object

PUT /{bucket}/{key}

Get Object

GET /{bucket}/{key}

Delete Object

DELETE /{bucket}/{key}

List Objects

GET /{bucket}

Head Object

HEAD /{bucket}/{key}

Copy Object

PUT /{bucket}/{key} with copy headers

​
Migration Guide

​
From AWS S3

Migrating from AWS S3 is as simple as changing your endpoint configuration: 
import { S3Client } from "@aws-sdk/client-s3";

const s3Client = new S3Client({
  region: "us-east-1",
  endpoint: "https://your-bucket.storage.nami.cloud",
  credentials: {
    accessKeyId: "your-access-key",
    secretAccessKey: "your-secret-key"
  },
  forcePathStyle: false
});

​
Migration Checklist

1

Update Endpoint

Change your S3 endpoint to https://{bucket}.storage.nami.cloud
2

Update Credentials

Replace AWS credentials with your Nami Cloud access keys
3

Test Operations

Verify basic operations like list, upload, and download work
4

Update Production

Deploy the endpoint changes to your production environment

​
Key Differences from AWS S3

While Nami Storage is fully S3-compatible, there are some enhancements specific to decentralized storage:

​
Enhanced Features

FeatureAWS S3Nami Storage
DecentralizationNoData distributed across Walrus network
Censorship ResistanceNoNo single point of control
Auto EncryptionManual setupBuilt-in AES-256 encryption
Auto RenewalN/AAutomated storage epoch management
AccelerationCloudFront requiredBuilt-in Railgun acceleration (Beta)

​
Performance Optimizations

  • Sub-100ms Latency: Railgun acceleration (Beta) provides faster access than traditional CDNs
  • Global Edge Network: Automatically cached at edge locations worldwide
  • Smart Routing: Optimized data paths reduce transfer times
  • Compression: Automatic compression for supported file types

​
Authentication & Security

​
Access Control

Nami Storage supports standard S3 authentication methods:
  • Access Key & Secret Key: Standard AWS-style credentials
  • Signature Version 4: Industry-standard request signing
  • Bucket Policies: Fine-grained access control (coming soon)
  • ACLs: Object-level access control lists (coming soon)

​
Enhanced Security

Beyond standard S3 security, Nami Storage provides:
  • End-to-End Encryption: AES-256 encryption by default
  • Decentralized Verification: Cryptographic proof of data integrity
  • No Vendor Lock-in: Your data remains accessible even if Nami goes offline

​
Common Use Cases

Static Website Hosting

Host websites with decentralized reliability

Backup & Archive

Long-term storage with automated renewal

Media Storage

Fast delivery of images and videos

Data Lakes

Analytics data with Web3 guarantees

API Data Storage

Application data with global availability

Content Distribution

Global content delivery with Railgun (Beta)

​
Best Practices

​
Naming Conventions

  • Use DNS-compatible bucket names
  • Avoid periods in bucket names for SSL compatibility
  • Follow S3 naming guidelines for objects

​
Performance Optimization

  • Enable compression for text-based files
  • Use multipart uploads for large files (>100MB)
  • Leverage Railgun (Beta) caching for frequently accessed content
  • Structure object keys to avoid hotspotting

​
Cost Optimization

  • Bundle small files when possible (auto-bundling coming soon)
  • Use lifecycle policies for data archival
  • Monitor usage through Nami Cloud dashboard

​
Getting Started

Ready to migrate? Here’s how to get started:
  1. Create Account - Sign up for Nami Cloud
  2. Generate Credentials - Create your S3-compatible access keys
  3. Test Migration - Try the migration with a test bucket first
  4. Full Migration - Update all applications to use Nami Storage

​
Need Help?

Experience the power of decentralized storage with the simplicity of S3. Your data will be more secure, more available, and truly yours.