Skip to main content Scroll Top

Cloudflare vs AWS: CDN, WAF, Hosting, Storage and Serverless Compared (and When to Use Both)

Updated September 2026 · Written and maintained by the Progression Agency strategy team

Cloudflare and AWS overlap more every year: both offer a CDN, a web application firewall, DNS, serverless compute, object storage and databases. This guide compares Cloudflare with the matching AWS services (CloudFront, AWS WAF and Shield, Route 53, Lambda, S3, RDS and DynamoDB), explains where each is stronger, how pricing differs, and why most businesses end up using Cloudflare in front of AWS rather than choosing one.

On this page · 9 sections
  1. Cloudflare vs AWS: what each is
  2. Cloudflare vs AWS CloudFront
  3. Cloudflare WAF vs AWS WAF
  4. Cloudflare R2 vs Amazon S3
  5. Cloudflare Workers vs AWS Lambda
  6. Pricing differences
  7. Using Cloudflare and AWS together
  8. Which should you choose?
  9. How Progression Agency uses them

The short answerUse Cloudflare for what sits in front of an application: DNS, CDN, DDoS protection, WAF, bot management, and small full-stack apps on Workers, Pages, R2 and D1. Use AWS for what sits behind it: virtual machines, containers, managed relational databases, queues, machine learning and the long tail of enterprise services. Cloudflare is simpler and usually cheaper for edge and bandwidth; AWS is broader and deeper for compute and data. Most production sites we build run both: Cloudflare at the edge, AWS (or Vercel) for the origin.

Comparisons are based on each project’s official documentation as linked in the text. Progression Agency builds with all of the technologies compared and has no affiliate relationship with any of them.

Cloudflare vs AWS: what each is

Cloudflare began as a reverse proxy and CDN that protects and accelerates websites, and has grown into a developer platform (Workers, Pages, R2, D1, KV, Durable Objects) that runs code and stores data on its global network. AWS is the largest cloud provider, with more than two hundred services covering compute, storage, databases, networking, analytics and AI. They compete at the edge and in serverless; they do not compete for the core of a large application’s infrastructure. Documentation: developers.cloudflare.com and docs.aws.amazon.com.

Cloudflare vs AWS: service by service
NeedCloudflareAWSUsual pick
CDNCloudflare CDN (global network)Amazon CloudFrontCloudflare for simplicity; CloudFront when deep in AWS
DDoS protectionIncluded on all plansAWS Shield Standard (free), Shield Advanced (paid)Cloudflare
Web application firewallCloudflare WAF (managed rules, free tier rules)AWS WAF (pay per rule and request)Cloudflare for most sites; AWS WAF for AWS-native apps
DNSCloudflare DNS (free, fast)Route 53Cloudflare
Bot managementBot Fight Mode, Bot ManagementAWS WAF Bot ControlCloudflare
Static hostingPagesS3 + CloudFront, AmplifyCloudflare Pages
Serverless computeWorkers (V8 isolates, edge)Lambda (regional), Lambda@EdgeWorkers for edge logic; Lambda for backend
Object storageR2 (no egress fees)S3 (egress billed)R2 for public assets; S3 for AWS-integrated data
SQL databaseD1 (SQLite at the edge)RDS, Aurora (PostgreSQL, MySQL)AWS for production relational data
Key-value / NoSQLKV, Durable ObjectsDynamoDBDepends on access pattern
Virtual machines and containersNone (Workers only)EC2, ECS, EKS, FargateAWS
Email sendingEmail Routing (inbound)Amazon SESAWS
Machine learningWorkers AI (inference)SageMaker, BedrockAWS for training; either for inference
Edge and origin: where each provider fits
Cloudflare protects and accelerates; AWS (or another origin) computes and stores.

Cloudflare vs AWS CloudFront

Both are global CDNs. Cloudflare bundles the CDN with DNS, DDoS protection and a WAF in one proxy that takes minutes to enable and includes unmetered bandwidth on its plans; CloudFront bills per gigabyte and per request and integrates natively with S3, Lambda@Edge and AWS WAF. For a marketing site or a store, Cloudflare is the quicker win. For an application whose assets and functions already live in AWS, CloudFront keeps everything in one account and one bill.

Cloudflare WAF vs AWS WAF

Cloudflare’s WAF ships managed rulesets (including OWASP core rules), rate limiting and bot detection with little tuning, and the free plan includes a small set of rules. AWS WAF is pay-per-web-ACL, per-rule and per-million-requests, with managed rule groups from AWS and marketplace vendors; it protects CloudFront, load balancers and API Gateway directly. Teams without a security engineer usually get better protection faster from Cloudflare; AWS-native teams prefer WAF for its integration with their other controls. See website security services.

Cloudflare R2 vs Amazon S3

R2 is S3-compatible object storage with no egress fees, which is the point: serving images, video and downloads from S3 costs per gigabyte leaving AWS, and R2 removes that line. S3 remains the default for data that other AWS services process (analytics, machine learning, backups) and offers more storage classes and lifecycle tooling.

Cloudflare Workers vs AWS Lambda

Workers run at every Cloudflare location with very fast cold starts and a limited runtime (V8 isolates, not full Node.js), ideal for middleware, personalization, redirects, API gateways and small apps. Lambda runs full runtimes in a region with access to the whole AWS ecosystem, better for heavy backend work, long tasks and anything that talks to RDS or S3 constantly. Many stacks use both.

Pricing differences

Cloudflare prices are mostly flat per plan (Free, Pro, Business, Enterprise) plus usage on Workers, R2 and add-ons, with no bandwidth charges; AWS is usage-based on almost every dimension, including data transfer out. Cloudflare bills are easier to predict; AWS bills need budgets and alerts. Check cloudflare.com/plans and aws.amazon.com/pricing.

Edge — Cloudflare edge. DNS, CDN, WAF, DDoS..
Core — AWS core. Compute, databases, queues..
R2 — No-egress storage. Public assets without transfer fees..
Work — Workers vs Lambda. Edge logic vs backend work..
Bill — Predictability. Flat plans vs usage billing..
Both — Use both. Edge in front, origin behind..

Using Cloudflare and AWS together

The most common production layout for a business web app: Cloudflare handles DNS, TLS, CDN caching, DDoS and WAF; the origin runs on AWS (EC2, ECS, Lambda) or on Vercel; the database lives in RDS or a managed Postgres service; public media sits in R2 or S3 behind Cloudflare. This gets Cloudflare’s edge protection and AWS’s depth without paying twice. See hosting types compared and backend hosting options.

Which should you choose?

Cloudflare or AWS?
SituationRecommendation
Marketing site or store needing speed and protectionCloudflare in front of any host
Static site or small full-stack appCloudflare Pages + Workers
Web application with relational data and background jobsAWS origin, Cloudflare edge
Enterprise already standardized on AWSAWS, with CloudFront and WAF; Cloudflare optional
Media-heavy site with large downloadsCloudflare R2 + CDN
Machine learning training, big dataAWS

How Progression Agency uses them

Every site we launch goes behind Cloudflare unless a client’s policy forbids it; applications run on Vercel or AWS depending on scale and compliance; heavy assets go to R2. Accounts belong to the client and the setup is documented. See cloud migration services and DevOps services.

Setting up or securing hosting?

We will design the edge and origin layout for your site or app, set it up in your accounts and document it.

Get a hosting plan

Frequently asked questions

Is Cloudflare better than AWS?
For edge services (CDN, DNS, WAF, DDoS) Cloudflare is simpler and usually cheaper; for compute, databases and the breadth of services AWS is far larger. They are complementary.
Can Cloudflare replace AWS?
For static sites and small full-stack apps on Workers, yes. For applications needing virtual machines, containers or managed relational databases, no.
Is Cloudflare cheaper than AWS?
For bandwidth and edge protection, yes: Cloudflare does not bill bandwidth on its plans and R2 has no egress fees. Compute and database costs depend on usage.
Can I use Cloudflare with AWS?
Yes, and most production sites do: Cloudflare at the edge, AWS as the origin.
What is the difference between Cloudflare and CloudFront?
Both are CDNs; Cloudflare bundles DNS, WAF and DDoS in one proxy, while CloudFront is AWS’s CDN integrated with S3, Lambda@Edge and AWS WAF.
Cloudflare WAF vs AWS WAF: which is better?
Cloudflare for fast, low-tuning protection of any site; AWS WAF for AWS-native applications and fine-grained control.
What is Cloudflare R2?
S3-compatible object storage with no data-egress charges.
What are Cloudflare Workers?
Serverless functions that run on Cloudflare’s edge network with very fast cold starts.
Does Cloudflare host websites?
Yes, through Cloudflare Pages for static and Workers-based sites.
Is Cloudflare free?
Cloudflare has a free plan with DNS, CDN, DDoS protection and basic WAF rules; paid plans add features.
Is AWS free?
AWS has a free tier for many services for a limited time or usage; production use is billed on usage.
Which is better for a WordPress site?
Cloudflare in front of a managed WordPress host is the common setup; AWS is used when the business runs everything on it.
Which is more secure?
Both are secure platforms; Cloudflare makes edge protection easier to get right, AWS gives more control over the origin.
Which does Progression Agency use?
Cloudflare for every site’s edge, AWS or Vercel for origins, R2 for heavy assets.
Can Cloudflare reduce my AWS bill?
Often, by caching at the edge and moving public assets to R2 to cut data-transfer charges.

Need help choosing or moving hosting?We recommend, set up, migrate and manage hosting for the sites and apps we build, and for sites built elsewhere.

Get a hosting recommendation

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Contact Us
0