When the AWS bill needs a closer look
Your AWS bill covers compute, storage, and data transfer. We review those costs alongside what the application needs to run.
We estimate the cost of running suitable workloads on Cloudflare and the work needed to move them.
Start with the bill and the workload
Before moving anything, we review your AWS services, traffic, storage, dependencies, and deployment process. We compare the current cost with a proposed Cloudflare setup, including migration work and any services that stay on AWS.
You get a recommendation: what to move, what to keep, the expected running cost, and a scoped first migration. Savings have to justify the work.
What can move?
Websites, web applications, APIs, and file storage are useful places to start. Each service needs its own compatibility check.
| On AWS today | A possible Cloudflare setup |
|---|---|
| Website hosting | Workers static assets for the site, with Workers for dynamic requests. |
| Lambda or a web API | Workers, after checking runtime support, dependencies, and execution limits. |
| S3 file storage | R2, after checking the S3 operations your application uses. |
| Relational database | D1 where its SQLite model fits, or keep Postgres/MySQL and connect through Hyperdrive. |
R2 has no direct egress charges. Storage and operations are still billed. See R2 pricing and S3 API compatibility.
Workers has a different runtime from a server. We check Node.js compatibility, execution limits, and storage options before recommending a move.
Migrate in stages
1. Choose the first workload
Pick a contained part of the product. Agree on cost, response time, error rate, and the customer journeys that must keep working.
2. Build and test alongside AWS
Adapt the code, move or connect the data, and test real workflows. Set up logs, alerts, backups, and a rollback plan before switching traffic.
3. Switch, measure, and hand over
Move traffic in controlled stages. Compare results with the agreed baseline, then retire the AWS resources that are no longer needed. Your team gets the code, deployment setup, and operating notes.
When keeping AWS makes sense
Heavy compute, specialized AWS services, database requirements, or compliance constraints can change the decision. Moving a website or file storage first may be worthwhile while the core system stays where it is.
The plan may cover one workload or the whole application.
Is your AWS setup worth moving?
Bring an overview of your product, the AWS services it uses, and your approximate monthly spend. We will talk through whether a move makes sense.