S3 TEST SPACE FOR DEVELOPERS

Test your S3 integration before it reaches production.

Get a private-by-default S3-compatible bucket, scoped credentials and 10 GB to exercise real upload, download, listing and deletion flows from your app.

No credit cardOne isolated bucketUp to 2 active keys
storage-client.ts S3 READY
// Use credentials supplied through your environment
import { S3Client, PutObjectCommand }
  from "@aws-sdk/client-s3";
import { fromEnv }
  from "@aws-sdk/credential-providers";

const s3 = new S3Client({
  endpoint: "https://storage.frees3.backends.co.uk",
  region: "gb-east-1",
  forcePathStyle: true,
  credentials: fromEnv(),
});

await s3.send(new PutObjectCommand({
  Bucket: process.env.S3_BUCKET,
  Key: "integration/hello.txt",
  Body: "hello from the test suite",
}));
Endpoint configuredCredentials stay in your environment
USE THE TOOLS ALREADY IN YOUR STACK
  • AWS SDK
  • AWS CLI
  • rclone
  • JavaScript
  • Python
  • PHP
  • Go
A REAL ENDPOINT, SMALL BLAST RADIUS

Build against S3 behaviour—not a storage mock.

Point a local build, integration suite or preview environment at your endpoint. The portal handles the bucket and key lifecycle while object traffic goes directly between your client and the S3 service.

01
</>

Your application

Configure its SDK or CLI with the endpoint, region and environment-held key.

02
API

S3-compatible endpoint

https://storage.frees3.backends.co.uk

03
S3

Your isolated bucket

One stable, randomly named bucket with bucket-scoped permissions.

Objects move through the S3-compatible endpoint. The portal manages your account, credentials and requested visibility while your client sends object requests to the endpoint shown in your dashboard.

DEVELOPER WORKFLOWS

Enough surface area to test the flows that usually break.

01

Wire up an SDK

Verify endpoint overrides, path-style addressing, regions, environment credentials and application error handling.

PUTGETLISTDELETE
02

Exercise key rotation

Create a second key for overlap, test it from the portal, then revoke the old one without changing the bucket name.

CREATETESTREVOKE
03

Check private and public reads

Keep objects private by default, or deliberately test anonymous read-only object URLs. Public mode never enables anonymous listing or writes.

PRIVATEPUBLIC GET
04

Inspect test objects

Use the browser for bounded uploads, downloads and deletion, then check storage, object-count and available transfer observations.

BROWSERUSAGE
PURPOSEFULLY SCOPED

Your test key is limited to one assigned bucket.

That gives application code the object operations it needs while excluding bucket lifecycle, identity, policy and service-wide discovery controls.

✓

Object workflowsList, locate, upload, download and delete

✓

Multipart workflowsList and abort uploads; list uploaded parts

—

No storage administrationNo bucket, IAM or policy management

FREE DEVELOPER SPACE

A practical target for integration tests.

No automatic paid conversion and no overage billing. Keep independent copies of anything important.

10GBdecimal storage quota
1bucketprivate by default
2keysrotation overlap
50GBmonthly download allowance
Use it as a test platform, not your only copy.No uptime SLA, managed backup, undelete, version history or guaranteed recovery point is included.
READY WHEN YOUR CODE IS

Give your S3 integration somewhere real to run.

Create your test account Email verification required. Service use is subject to the published limits and acceptable-use rules.