👋 Introduction

What is Lighthouse S3?

Lighthouse S3 is an S3-compatible API for Lighthouse storage (IPFS + Filecoin). Point the AWS CLI, boto3, rclone, or any tool that speaks Amazon S3 at the Lighthouse S3 endpoint, and your files land on Lighthouse — content-addressed by CID, backed by Filecoin deals — with the bucket-and-key workflow your tools already understand.

No SDK migration, no new upload API to learn: if it works with S3, it works with Lighthouse S3.

Your existing S3 tools ──▶ s3.lighthouse.storage ──▶ Lighthouse (IPFS + Filecoin)
   aws cli / boto3 /            S3 API                 files stored by CID,
   rclone / SDKs            (SigV4, buckets, keys)     billed to your account

---

What You Can Do

• Use any S3 client – AWS CLI, boto3, aws-sdk-js, rclone, and other SigV4 S3 tools work out of the box.
• Keep your workflow – buckets, keys, multipart uploads, presigned URLs, pagination: standard S3 semantics.
• Get CIDs for free – every object response carries its IPFS CID in the x-amz-meta-cid header, so content addressing comes built in.
• Bill through your Lighthouse account – uploads count against your existing Lighthouse plan; no separate billing.
• Self-serve credentials – trade your Lighthouse API key for S3 credentials with a single API call. See Create S3 Keys.
• Share with presigned URLs – hand out time-limited download links without sharing credentials.

---

Endpoint at a Glance

Endpoint	https://s3.lighthouse.storage
Region	us-east-1
Addressing	Path-style (https://s3.lighthouse.storage/bucket/key)
Auth	AWS Signature Version 4 (standard S3 credentials)

---

Where to Go Next

• 🚀 Quick Start — upload your first file in five minutes
• 🔑 Create S3 Keys — get your access key and secret
• 📖 Supported Operations — the full compatibility list
• 🌐 S3 and IPFS Semantics — how mutable S3 maps onto immutable content addressing (read this before storing sensitive data)