"S3" gets used to mean two different things, and the confusion trips people up. It's worth untangling, because understanding it is the key to not getting locked into one vendor. This is what S3 object storage actually is — and why it matters that so many providers "speak S3."

S3 the service vs S3 the standard

Amazon S3 (Simple Storage Service) is the object storage service AWS launched in 2006. It stores data as objects in buckets, reached over an HTTP API.

But S3 is also, effectively, a standard. Because S3 came first and became dominant, its API turned into the common language of object storage. Today dozens of providers and open-source projects implement that same API — so tools written for Amazon S3 work against any of them. When people say a provider is "S3-compatible," they mean it speaks that API, so your existing tools and code work with only a config change.

How S3 object storage works

The core concepts are simple:

• Bucket — a container for objects, with a globally identifiable name.
• Object — a file plus its metadata, stored under a unique key (its name/path within the bucket).
• API — you interact over HTTP: PUT to upload, GET to download, DELETE to remove, plus operations for listing, multipart uploads, presigned URLs, versioning and lifecycle rules.

There's no filesystem and no folders — just keys in a flat namespace, though prefixes (like photos/2026/) can imitate folder structure.

Why the S3 API winning matters to you

Because the S3 API is a de-facto standard, your data isn't trapped. Nearly every backup tool, SDK, CLI (aws-cli, rclone), and application framework can talk to any S3-compatible provider. That gives you portability — you can switch providers, run multi-cloud, or move for price or compliance reasons, without rewriting your integration. (The one thing to check is that a provider doesn't charge a punishing egress fee to get your data out.)

What to check in an S3-compatible provider

"S3-compatible" is a spectrum. Confirm the operations you rely on — multipart uploads, presigned URLs, lifecycle policies, versioning — actually work by testing with your real tools. And check the things the API doesn't tell you: egress cost, data residency, and support.

Getting S3 object storage that fits Europe

If you want the S3 API with data kept in the EU and no egress surprises, an EU-hosted S3-compatible provider is the clean choice. Internetport's object storage implements the S3 API, is GDPR-compliant, charges no egress fees, and offers a free 10 GB tier — so you can point aws-cli or rclone at it and confirm compatibility in minutes. To shortlist across the market, see our object storage providers comparison.