S3-compatible

Name: Nexoxa Bridge
Author: Nexoxa

AWS S3, MinIO, Cloudflare R2, and DigitalOcean Spaces via s3:// URLs.

S3s3://ACCESS_KEY:[email protected]/my-bucket?region=us-east-1

The story

These pages use illustrative scenarios (sample names and timelines) to explain real Nexoxa Bridge features. Connection URLs, sidebar panels, and vault behavior match the product; story details are teaching examples, not customer case studies.

Alex runs uploads on Cloudflare R2, customer backups on AWS S3, and CI artifacts on a MinIO bucket in the office closet. Three vendors, three consoles, three sets of access keys in env files — until every bucket became a saved s3:// card in Bridge.

Monday morning: list staging prefixes like folders, preview a PDF invoice without downloading, upload a batch of resized images, delete a bad prefix — all before opening the AWS console in a browser that demands MFA again. forcePathStyle=true on MinIO just works when documented in the URL.

Object storage should feel like a file manager, not a cloud portal scavenger hunt.

Connection URL

Scheme: s3://

Parameters

DigitalOcean Spacesstringvaultrequired

s3://ACCESS_KEY:[email protected]/my-bucket?region=us-east-1

AWS S3stringvaultrequired

s3://ACCESS_KEY:[email protected]/my-bucket?region=us-east-1

MinIO (path-style)stringvaultrequired

s3://minioadmin:minioadmin@localhost:9000/my-bucket?region=us-east-1&forcePathStyle=true

Cloudflare R2stringvaultrequired

s3://ACCESS_KEY:SECRET@ACCOUNT_ID.r2.cloudflarestorage.com/my-bucket?region=auto

Paste the URL in Nexoxa Bridge → New connection. Save a human-readable name — MCP references that name, not the raw URL with embedded passwords.

Step 1

Bucket browser

Alex navigates s3://backups/2026/07/, multi-selects old tarballs, and moves them to glacier-prefix without a script. Inline preview confirms the PDF is the right contract before generating a presigned link.
ACCESS_KEY:SECRET encrypt on save — never echoed in logs.

Prefix navigation, upload, move, delete, and media preview. Supports AWS, R2, MinIO, DigitalOcean Spaces via s3:// URL variants. Region and forcePathStyle query params for vendor quirks.

Step 2

Multi-vendor

Staging MinIO and production R2 sit as MinIO Local and R2 Prod in Connections. Same mental model, different endpoints — Alex picks the card, not the SDK code path.
Vendor-specific URL examples live in the right panel for copy-paste.

One URL format across vendors. forcePathStyle=true for path-style endpoints. Separate saved names per bucket/account for MCP and automation.

Step 3

Batch uploads

A 4 GB folder upload queues with per-object ETA. One object fails with 503; Bridge retries while Alex grabs coffee — no custom aws s3 sync one-liner.

Parallel uploads with retry on 5xx. Shared queue UX with SFTP transfers. Progress per object in the transfer studio.

Explore the full feature guide: S3 object browser