Companies Using Amazon Web Services (AWS)

Amazon Web Services is the largest single technology footprint in our index, and it is also the one most likely to be misread. Before any of the tables on this page are useful, you need to know what a detection here actually asserts. Everything below depends on it.

Why our number and Amazon's number disagree

AWS booked $42.2 billion in the quarter to June 2026, up 37%, across 124 Availability Zones in 39 regions. This page publishes 936,363 domains. Those two figures get set side by side in analyst decks and they should not be, because neither is a version of the other.

Revenue counts accounts. We count hostnames that answer to a browser. The overlap is thin. The largest AWS bills in the world are compute, storage, data pipelines and internal services, and none of that resolves to a public domain anyone can crawl. Meanwhile a freelancer with one Route 53 hosted zone at 50 cents a month produces a detection identical to a bank's. The population on this page is therefore skewed toward the cheapest thing AWS sells, and it is silent about the expensive ones.

That limit is worth stating plainly rather than working around. To size AWS as a business, read Amazon's filings. To find out which specific domains touch AWS this month and what else is installed alongside them, the filings are no help at all, and that is what this page is for.

What the detection proves

Three separate signals can put a domain on this list, and they carry very different weight. The first is DNS: the domain's nameservers are delegated to Route 53. The second is the HTTP response for the page itself, which arrives carrying AWS service headers such as x-amz-request-id or x-amz-id-2. The third is a reference to an amazonaws.com address inside the page's JavaScript.

TechnologyChecker.io took a random sample of 260 detected domains and resolved each one by hand. 60.8% matched on nameservers, 10.0% on their own response headers (3.1% on both), and 32.3% matched on neither, which leaves the JavaScript reference as the only explanation. The first two mean somebody is paying Amazon. A hosted zone has an owner and an invoice. The third does not, and here is why it matters: we pulled every recorded fetch to an amazonaws.com host across our index, and 71.85% of the domains making them fetch only from buckets that appear on 50 or more unrelated sites. Those are Shopify apps, form builders, real-estate CRMs and school website vendors serving their own files from their own S3 buckets. The site loads a file from AWS. The AWS customer is the vendor.

Which is why the company list on this page is not simply the top of the ranking. We tested the 160 largest candidates individually and kept the 72 that confirmed. On this technology, publishing the unfiltered list would have put dozens of businesses in front of you whose only connection to Amazon is a plugin their web agency installed.

Sales Signal: Treat the headline count as a market size and the confirmed list as a target list. If you sell cloud cost management, migration services or DevOps tooling, the qualifying question is whether the prospect owns the AWS account, and the fastest proxy is whether their nameservers or their own response headers carry the signal.

Growth trajectory

We can show three months: 683,467 domains in June 2026, 869,267 in July, 936,363 in August. Resist the obvious reading. AWS launched S3 in 2006 and has been the largest cloud provider since roughly 2012, so nothing about this platform grew 37% over one summer. What grew is our coverage. The honest version is that AWS touches at least 936,363 live domains and the true number is higher, because a site running on EC2 behind another company's CDN with third-party DNS produces none of our three signals.

The determinism figure is the useful one instead. Across active detections the ratio of confirmed sightings to scans is 0.997, about as close to 1.00 as anything we measure. DNS records and response headers do not flicker the way a JavaScript tag does, so when we say a domain is on AWS this month, it will almost certainly still say so next month.

"A 0.997 determinism score is a measure of how reproducible the reading is, not how much it means. AWS is the clearest example we have of a signal that is perfectly stable and still easy to over-interpret." - David Thomson, CTO at TechnologyChecker.io

Sales Signal: Do not build a trigger on month-over-month movement in this count while coverage is still expanding. Build it on the migration table instead, where the direction of travel for an individual domain is a genuine event.

Customer profile

80.4% of the 446,064 companies we sized have fewer than 50 staff, and 2.56% have more than 1,000. Every instinct says that skew is wrong for an enterprise cloud, and every instinct is reading the wrong thing. Route 53 costs 50 cents per hosted zone per month. It is the cheapest line item in cloud computing and the default for anyone who registers a domain through AWS, which makes the small end of this table a census of domain owners.

The 8.14% with 200 or more staff is where the procurement cycles live, and that is 36,298 companies. Age tells a similar story: 39.76% were founded in the 2010s and 23.27% in the 2020s, so 63% of the matched base is younger than AWS's own enterprise business.

Sales Signal: Segment on headcount before anything else on this page. The sub-50 band is a self-serve motion at best. The 36,298 companies above 200 staff, cross-referenced against the second-service test below, is the list worth a human.

Industry and geographic concentration

Software Development leads the industry table at 8.07% and nothing else reaches 6%. We publish profiles where one vertical takes 30% of the base; here the top ten industries together account for less than 40%. That flatness is the point. AWS has no vertical, and this table is closer to a description of the commercial web than a description of an AWS buyer.

Geography is more concentrated: the United States takes 41.76%, and adding the United Kingdom, Australia and Canada brings the English-speaking share to 60.5%. Brazil at 4.52% outranks both Canada and Germany, which happens on almost no other profile we publish.

One caveat on Real Estate, which looks large at 17,217 companies. A meaningful share of those are individual agent sites hosted by a handful of brokerage platforms, so the industry count runs well ahead of the count of decision makers.

Sales Signal: Brazil is the geography worth a look, because it ranks above markets with far more mature cloud tooling ecosystems and far more competition for the same accounts.

Migration patterns

The largest corridor in our data is 26,591 domains that dropped AWS and now run Cloudflare, against 4,532 in the reverse direction. Before that becomes a story about Cloudflare taking share, apply the mechanism test. Onboarding a domain to Cloudflare replaces its nameservers, and nameserver delegation is what 6 in 10 of our AWS detections rest on. So a company can move DNS and CDN to Cloudflare, keep every server it has on EC2, and disappear from this count entirely.

We measured how often that happens. 12.13% of the domains in that corridor still run another Amazon service, which is a floor rather than an estimate, because it only catches the ones running a second AWS product we detect separately. The corridors we would defend as real are the smaller ones: AWS is net positive against Google Cloud CDN at 2,143 in versus 1,089 out, and against Firebase at 1,141 in versus 418 out. Against Azure it is level, 311 in and 329 out.

"The Cloudflare number is the biggest in the table and the least trustworthy in it. When your signal is DNS, anything that changes DNS looks like churn." - David Thomson, CTO at TechnologyChecker.io

Sales Signal: The 26,591 are a strong list for edge and DNS tooling and a weak list for anything sold on the premise that they left AWS. The 11,041 that moved in the last 30 days are still inside the window where an infrastructure decision is being revisited.

Technology ecosystem

52.76% of AWS domains carry at least one other Amazon service, led by S3 at 33.64% and CloudFront at 27.27%. We would use that as the qualification line on this whole page. A domain with AWS plus S3 plus CloudFront is built on the platform. A domain with the AWS signal alone and nothing else is most often a hosted zone.

Then there is the overlap nobody expects: 34.26% of these domains also run Cloudflare, and 18.0% run Cloudflare without a second Amazon service. Multi-vendor is the normal state of the infrastructure layer, not the exception, and any pitch built on "you are an AWS shop" will be wrong about a third of the time. Google Analytics appears on 65.27%, which tells you nothing about AWS and everything about the web.

Sales Signal: The 18.0% running Cloudflare in front of AWS are the clearest opening for anyone selling observability, cost attribution or WAF consolidation, because they are already paying two vendors for the delivery path and can see both bills.