FEATURES / CORS Editor
/// CORS Editor
Fix CORS errors without editing JSON.
View and edit S3 CORS configuration through a visual form. Add allowed origins, toggle HTTP methods, set headers. Applied to AWS instantly — no JSON policy required.
Start for freeYour CORS rules. Readable. Editable. Applied in seconds.
/// How it works
Select a bucket
Pick any bucket from your connected accounts. Storafleet loads the current CORS configuration immediately — you see what's active before making any change.
Edit the rules
Add or remove allowed origins, toggle HTTP methods (GET, PUT, POST, DELETE, HEAD), set allowed and exposed headers, and configure max age.
Save — applied immediately
Hit save and Storafleet pushes the new CORS config to AWS S3. Your browser-based applications pick up the new rules on their next preflight request.
Visual CORS form
Add allowed origins, select HTTP methods, set headers and max age — all through form inputs. No XML or JSON policy writing required.
Origin management
Add multiple allowed origins line by line. Storafleet warns you when a wildcard (*) is present — unintentional wildcards are a common misconfiguration.
Applied instantly
CORS changes are pushed to the S3 API the moment you save. No deploy step, no CloudFormation, no waiting for propagation beyond normal AWS consistency.
View current config at a glance
See exactly what CORS rules are active on any bucket right now. The current configuration is shown before you make any changes — no surprises.
Wildcard warnings
Storafleet flags wildcard origins and methods. Accidental * in Production origins is a security misconfiguration — we surface it before it becomes a problem.
Raw JSON fallback
Need to paste a CORS config directly? Switch to raw mode, paste the JSON, validate and apply. Both modes supported — pick what works for you.
/// Without Storafleet
Fixing a CORS error in S3 means writing XML or JSON policy by hand and hoping the syntax is right.
- S3 CORS config is XML in the console — easy to get wrong and hard to read
- No way to see current CORS config without CLI or Console navigation
- Wildcard origins are visually identical to specific origins in raw JSON
- Apply CORS changes require re-uploading the entire policy document
- No validation — a typo in an origin silently breaks your app
/// With Storafleet
A visual CORS editor. Origins, methods, headers — form fields. Applied immediately.
- Current CORS config shown immediately when you select a bucket
- Form-based editor — origins list, method toggles, header inputs
- Wildcard (*) origins flagged with a visible warning
- Changes applied to S3 API instantly on save
- Raw JSON mode available for power users who prefer it
/// When you'll use this
Debugging a CORS error in production
Your React app throws a CORS error on S3 object fetch — but only in production. You open Storafleet, check the CORS config on the prod bucket, and see the allowed origin list is missing your new domain. Add the origin, save. Error gone. Total time: 90 seconds.
Key featureVisual CORS origin editor with instant apply
Locking down CORS before go-live
Staging had a wildcard origin (*) for convenience during development. Before launch, you need to tighten it to the actual production domain. Storafleet surfaces the wildcard with a warning — you replace it with the specific origin and apply. No JSON, no CLI.
Key featureWildcard warning + origin replacement
Enabling direct S3 uploads from the browser
You want users to upload files directly from your frontend to S3 — bypassing your servers entirely. This requires CORS to allow PUT from your app's domain. You configure it in Storafleet in 2 minutes, test it, done. Your server costs drop immediately.
Key featurePUT method CORS config for direct browser upload
Your storage estate deserves a control plane.
Join the DevOps teams and founders who run every cloud's buckets from one control plane.
Free plan · No credit card · 50+ cloud providers · Cancel any time