S3 bill is dominated by egress
Cloudflare R2 and Backblaze B2 are S3-compatible with much lower egress.
Try this first
- 1R2: zero egress cost, storage slightly higher, great for public assets
- 2B2: low storage plus low egress (especially via Cloudflare partner)
- 3Migrate via rclone or aws-cli with endpoint override
- 4Keep backups dual: one primary plus one secondary provider
When to bring us in
For compliance data or strict SLA, AWS S3 stays the safe default. Not all workloads fit.
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.