How to Mount Scaleway Object Storage on macOS: Treat Your Cloud Storage Like a Local Folder

Why Mounting Scaleway Object Storage on macOS Is a Smart Move

Working directly on Scaleway Object Storage through Finder beats fighting with the Scaleway CLI or third-party S3 browsers. A mounted drive streams files on demand, so you can browse a multi-terabyte bucket in Paris or Amsterdam without filling your Mac's SSD. And because the mount is just a folder, every macOS app — Preview, Pages, VS Code, Photoshop — sees Scaleway as a native location.

🧩 Native Finder Integration — Your Scaleway bucket shows up as a regular folder and a mounted Finder volume, so any macOS app can open and save into it without the Scaleway CLI or an S3 browser.
💾 No SSD Hostage Situation — Scaleway buckets can hold terabytes of media or backups. Mounting streams files on demand, so even a multi-TB bucket only spends Mac disk space on the files you actually open.
⚡ Real-Time Access to Cloud Files — Objects uploaded from an Instance, a Kubernetes job, or a teammate appear in your mounted folder after the next poll cycle.
🛡️ Read-Only Mode for Safety — Scaleway often hosts EU-sovereign data — exactly the data you don't want to mutate by accident. Mount read-only and Finder will block any writes outright.
🇪🇺 EU Regions + Free 75 GB Tier — Scaleway Object Storage offers Standard, One Zone-IA, and Glacier classes across Paris (fr-par), Amsterdam (nl-ams), and Warsaw (pl-waw), with 75 GB of Standard storage and 75 GB of egress free per month — great if you need EU data sovereignty.

How Mounting a Cloud Drive Works (and Why It's Different from Sync)

Traditional sync tools copy every object in your Scaleway bucket down to your hard disk and keep both sides matched. That's fine for small buckets, but it's a non-starter when you're storing the kinds of large media or backup archives Scaleway is good at.

Mounting flips the model. OurClone presents your Scaleway bucket as a virtual filesystem — the object key hierarchy is visible right away, but file contents are only fetched when you actually open something. Frequently used objects are cached locally for instant repeat access, and writes are pushed back to Scaleway in the background using standard S3-compatible PUTs.

OurClone makes both the polling interval (how often it checks Scaleway for remote changes) and the maximum cache size configurable, plus a read-only switch for extra safety on production buckets.

🚀 Stream files on demand — no need to download the whole drive
💾 Saves Mac disk space by caching only what you actually open
🔁 Two-way sync — edits in the mounted folder push back to Scaleway
🛡️ Read-only mode prevents accidental writes when you only need to browse

What to Know Before You Mount Scaleway Object Storage

A little planning before you click Mount will save you from cleaning up a messy mount point later.

📁 Pick the Right Mount Source — You can mount a specific Scaleway prefix (say /backups/2026) for focused access, or mount the entire bucket for full Finder browsing. A narrower prefix usually feels snappier.
🖥️ Choose a Sensible Local Mount Point — Use a dedicated, empty folder like ~/CloudMounts/Scaleway. Don't aim it at your Desktop or any folder that already has files — the mount will hide whatever was there.
🔒 Read-Only vs Read-Write — Read-only is the safer pick when your Scaleway bucket holds production data or archives. Pick read-write only if you need to upload or edit. Remember: read-only mode literally cannot upload — Save dialogs will fail.
⏱️ Set a Reasonable Polling Interval — Lower intervals catch remote changes faster but generate more LIST traffic. For Scaleway, a 30–60 second interval is usually a good balance.
💽 Plan Your Cache Size — A bigger cache makes repeat opens snappy and reduces egress from your Scaleway bucket. A few GB is plenty for documents; bump it up if you regularly reopen large media files.

How to Mount Scaleway Object Storage on macOS with OurClone

OurClone makes mounting Scaleway Object Storage on macOS refreshingly painless. Step 1 uses Scaleway API keys plus a regional endpoint — and from there you're four clicks away from a Finder-ready volume.

🔐 Connect to Scaleway Object Storage via Access Keys — Open OurClone and go to Add Storage. Choose the Scaleway provider from the S3 list, then fill in your Remote Name, Access Key ID and Secret Access Key (create these in the Scaleway console under Identity and Access Management → API Keys). Pick the Endpoint and Region that match your bucket — for example, s3.fr-par.scw.cloud + fr-par for Paris, s3.nl-ams.scw.cloud + nl-ams for Amsterdam, or s3.pl-waw.scw.cloud + pl-waw for Warsaw. Once entered, OurClone will verify your credentials and Scaleway will appear as a connected storage backend.

📂 Open the Mount Tab and Click New Mount — Once Scaleway is connected, go to the Mount tab in OurClone. Click the New Mount button in the top-right corner to open the mount configuration dialog.

⚙️ Configure the Mount Settings — In the dialog, pick Scaleway as the authorized source. Choose what to mount — a specific bucket prefix (e.g., /backups/2026) or the entire bucket. Then pick a local folder as the mount point (something like ~/CloudMounts/Scaleway). Choose Read-only if you just want to browse, or Read-write if you need to upload and edit. Optionally tweak the polling interval (how often OurClone checks Scaleway for changes) and max cache size. Click Mount to finish.
🗂️ Use Your Scaleway Mount Like a Local Folder — Open the local folder you picked as the mount point. macOS now treats it as a mounted volume — you can browse, open, create folders, drag in files, and delete items just like any local folder. For example, create a new backup folder inside and drop in a few photos. OurClone uploads them to your Scaleway bucket in the background.

✅ Confirm the Sync on Scaleway Object Storage — Switch back to OurClone and open your Scaleway storage from the file browser — your new backup folder and uploaded photos should already be listed. For extra peace of mind, log in to the Scaleway Object Storage console and confirm the files appeared in your bucket too.

The combination of Scaleway API keys and OurClone's mount engine gives you a Scaleway bucket that genuinely feels like a local volume on macOS — EU-sovereign, S3-compatible, and ready to use right from Finder.

Getting the Most Out of Your Scaleway Mount

A live mount is convenient. Keep these in mind once your Scaleway mount is up and running.

🔁 Edits Sync Both Ways — Anything you add, rename, or delete in the mounted folder propagates to Scaleway. Changes uploaded from other clients appear after the next poll cycle.
🛑 Read-Only Means Read-Only — If you mounted with read-only permissions, drag-and-drop uploads and Save dialogs will fail silently or with a permissions error. Remount as read-write to enable uploads.
💽 Cache Lives on Your Mac — Recently opened files are cached locally to reduce egress from your Scaleway bucket. If your Mac is low on disk space, reduce the max cache size in the mount settings.
⏱️ Polling Interval Affects Freshness — A short polling interval picks up remote changes faster but generates more LIST traffic. For Scaleway, a 30–60 second interval is usually a good balance.
🔌 Unmount Cleanly Before Sleep — If you put your Mac to sleep with the mount active, OurClone will reconnect automatically on wake. For long absences, click Unmount in the Mount tab to release the volume.

When Your Mount Stops Working

Most mount failures trace back to one of a few causes: a deleted or rotated Scaleway API key, the wrong region or endpoint (Scaleway tightly pairs the endpoint and region — using fr-par with the Amsterdam endpoint will fail), a bucket that's been deleted or renamed, or a mount point that's no longer empty. If your Scaleway mount returns auth or signature errors, regenerate the key in the Scaleway IAM console, double-check both the endpoint and region under Add Storage, and remount.

Verify the Sync Anytime

Any time you're unsure whether a file made it up, you have two easy checks: open the Scaleway storage view inside OurClone's file browser, or log straight into the Scaleway Object Storage console. Whatever Finder shows in your mount point should match — and if it doesn't, give it a poll cycle and check again.