Companies using Amazon Web Services (AWS)
28,700 companies in the market · 670+ named decision-makers ready in 24-48 hours · Sized November 2026
- Built to your filters, never reused
- Compiled fresh for your order
- Every company checked on its own website
- Decision-makers confirmed current
- Emails verified at build time
- Bounced emails replaced or refunded for 30 days
Signals you can ask for
Name the one that fits your offer when you reply to your order receipt; we confirm it can be sourced for this market before we build. Each row then shows the signal, its date where it has one, and where it came from.
- Exhibiting at a trade show in the next 6 months
- New certification or registration in the last 12 months, from the registry this list is built on
- Bought, merged or recapitalized in the last 12 months
- New products or a new facility announced on its own site in the last 6 months
- Hiring now: open roles on its own site
About 46,500 US companies show their own Amazon Web Services setup, estimated from a random sample of 3,122 company domains scanned on November 16, 2026; the cautious figure is 28,700. That means the site or email is hosted or sent on AWS, not that the whole stack runs on it; a site on a hosting platform that runs on AWS does not count alone. Use rises with size, from 1.8% of companies with 1-10 staff to about 10% of those with 51 or more.
A national order delivers 2,400+ companies with a company phone within 24-48 hours, each confirmed by a fresh scan on the order day; a state, industry or size-band order covers every company we can confirm there. The Researched file names a technology lead or founder at 670+ of them, each with a verified email.
Companies
$500
2,400+ companies with a phone
- Nationwide, or narrowed to your states or metros
- Company phone; website and general email where published
- Location and the fields on this page
- CSV emailed within 24-48 hours
Named decision-makers
$800
670+ named decision-makers
- The CTO or VP engineering, head of IT or DevOps, founder at small companies at each company, by name
- 670+ with a verified email; company phone for the rest
- Each person checked as current in the role
- Companies we cannot confirm are left out, never guessed
One-time purchase. Card payment with bank authentication. Built to order and emailed as a CSV within 24-48 hours. If a list comes in under the floor we state, we tell you before delivery and refund the difference or widen the scope. Any email that bounces within 30 days is replaced or refunded.
Check the quality first: free sample of 25 rows
The sample is the real thing: 25 rows with a named decision-maker, verified email and phone, checked by hand. It downloads as a CSV.
The market, sized in November 2026
1,626,000
US companies in the scanned directory pool
28,700
In scope after exclusions (estimate)
2,400+
In a 24-48-hour national file
670+
Named decision-makers in that file
670+
Verified emails in that file
Estimated from a random sample of 3,122 US company domains drawn from business directory records (companies with an owner or executive on file, every industry and size) and scanned on November 16, 2026. A company counts when its public DNS shows its own AWS setup: mail sent through Amazon SES or received on AWS, or a company subdomain served by an AWS service. The in-scope figure is the cautious end, allowing for the sample being drawn in batches.
- Who is in it
- US companies whose own website code or public DNS records show they use Amazon Web Services (AWS) (sites and email hosted or sent on AWS); each row carries the evidence and the scan date; with the person who owns the tool identified
- Left out on purpose
- companies outside the US, Amazon Web Services (AWS)'s own offices and partners listed only as resellers, domains with no operating business (parked or redirected), evidence older than the scan (records we cannot see on the scan date)
- The person on each row
- CTO or VP engineering, head of IT or DevOps, founder at small companies
- Can be narrowed by
- state, region or city, industry, employee band, other tools in use
Companies on the list
10 of about 28,700, as examples. People and contact details are in the file, not on this page.
| Company | City | State | Type |
|---|---|---|---|
| Quince | San Francisco | CA | Direct-to-consumer retailer, 1,001+ staff; mail via Amazon SES, site on CloudFront |
| SAIC | Reston | VA | Government technology contractor, 1,001+ staff; site on EC2 |
| Slalom | Seattle | WA | Consulting firm, 1,001+ staff; help site on CloudFront |
| Sol de Janeiro | New York | NY | Beauty brand, 201-1,000 staff; mail via Amazon SES |
| Belmont Behavioral Health System | Philadelphia | PA | Behavioral health hospital, 201-1,000 staff; site on CloudFront, mail via Amazon SES |
| SXSW | Austin | TX | Conference and festival organizer, 201-1,000 staff; mail via Amazon SES |
| Belmont Village Senior Living | Houston | TX | Senior living operator, 1,001+ staff; site and mail on AWS |
| Snickfish | Maryville | TN | Title management services, 1-10 staff; mail received on AWS |
| J. Blanton Plumbing | Northbrook | IL | Plumbing contractor, 51-200 staff; mail via Amazon SES |
| Arise | Miramar | FL | Customer service platform, 1,001+ staff; support site on CloudFront |
How this list is built
Built from each company's own public records, read again on the day of your order.
- Universe: US companies with an owner or executive in business directory records, every industry and size, matched to their own web domains.
- Scan: public DNS plus one plain read of the homepage. AWS counts on an amazonses.com include in SPF (mail sent through Amazon SES), mail received on AWS, or a company subdomain pointed at CloudFront, Elastic Load Balancing, S3, Elastic Beanstalk, Amplify or an EC2 host.
- Exclusions: parked or redirected domains, Amazon's own domains and companies outside the US. Not counted alone: a website address in AWS ranges, usually a hosting platform (54,600 more companies), or Route 53 name servers (21,800 more).
- Decision-makers: CTO, VP or head of engineering, head of IT or DevOps, IT director; the founder or owner at companies under 51 staff, from verified business contact records.
- What the 48-hour file contains: about 100,000 company domains scanned on the order day; the 2,400+ with AWS evidence and a company phone from the site or the directory record are kept. No phone, no row.
- Company websites (homepage code): One plain read of each company's homepage: links to vendor-hosted portals, the published phone and the contact page
- Public DNS records (mail and verification records): Mail (MX), sending (SPF) and domain-verification (TXT) records and subdomain aliases, read on the scan date
- Amazon Web Services published IP address ranges: Every address block AWS uses (EC2, CloudFront, Global Accelerator and more), to read which subdomains and mail hosts sit on AWS and to flag website addresses on AWS as an extra column
- Business directory records: US companies with an owner or executive on file, with employee band and state, matched to each company's own web domain, and a company phone where the website shows none
- Verified business contact records: Named IT, engineering and owner-level decision-makers with verified business email where available
Who buys this list, and how to use it
AWS consulting partners, cost-optimization and FinOps vendors, cloud security and backup vendors, DevOps tool makers, competing clouds and technical recruiters buy this list. Target the CTO or head of engineering at software and larger firms, the IT director at traditional businesses, and the founder below 50 staff.
- Timing: cloud budgets are set from October to December and bills reviewed after a surprise invoice; migration and security projects are often planned in the first quarter.
- Response: engineering leaders ignore generic cloud pitches; lead with what you saw, such as a help site behind CloudFront or mail sent through SES, and one specific saving or risk.
- Tip: rows with a CloudFront, load-balancer or EC2 subdomain run customer-facing infrastructure on AWS, the first segment for partner and FinOps offers. Rows with SES sending only (64% of companies) suit email and security offers better.
How every order is compiled
This is not an export from a stored contact database. Your file is compiled from scratch in the 24-48 hours after you order, for the whole country or just your territory, using the same method that built the free sample.
Built for your order, never reused
Reply to your order receipt with the cut you want: your states or metros, which companies to keep or leave out (any of the filters under “Can be narrowed by”), the titles to name. We build the file to that brief, at the same price. There is no master file on a shelf: each file is compiled for one buyer, and no buyer's file is ever reused for another order.
- 1Rebuilt from the original sources on the day of your order. We don't keep this list on a shelf. When you order, we go back to these sources and run the search again across every state, or only your territory:
- Company websites (homepage code)
- Public DNS records (mail and verification records)
- Amazon Web Services published IP address ranges
- Business directory records
- Verified business contact records
- Each company's own website
- 2Every company read on its own website. We open each company's website and read its home, services and about pages. A company stays in the file only if those pages show it fits this page's definition; a matching industry code or a keyword in its name is never enough on its own. Everything under "Left out on purpose" is removed.
- 3Ownership and status checked. We search each company's name with terms like "acquired", "joins", "part of" and "portfolio company", because a website often still reads independent months after a sale. That keeps each row's owner current, removes companies of a kind this page leaves out (such as hospital-owned practices) and catches any that have closed.
- 4Duplicates merged. Rows are matched on phone number, website domain, street address and name, so branches, trade names and duplicate registry records collapse into one company.
- 5The right person, confirmed current. For the researched file we look for the CTO or VP engineering, head of IT or DevOps, founder at small companies on the company's own team or about page, in public filings (such as the official named on a registry or license record) and in verified business contact records. Each person must be shown with the company today, on its own site or a second current source. A match to someone with the same name at a different company is thrown out.
- 6Emails verified at build time. Each named email must come back verified when your file is built, sit on the company's own domain, and that domain must have a working mail server (we check its MX record). We never guess an address from a name pattern. Shared inboxes like info@ or office@ go in a separate general-email column, never next to a person's name.
- 7Phones that reach the company. Every phone number is compared with the one on the company's own website or business listing. Registry and license numbers are often years old, so when they disagree, the company's current number wins.
- 8Checked row by row before delivery. An automated check rejects the file if it has duplicate companies, rows without a phone, or cells a spreadsheet would turn into dates. Then we open 20 random rows (100 on large files) and check each one against its source. The CSV comes with a note listing what we checked and what we removed. If the file comes in under the numbers on this page, we tell you before delivery and refund the difference.
Read the full method: your ideal customer, plus the signal that says why now →
Frequently asked questions
Does this mean the company runs on AWS?
No. It means the company's own email or a company site is hosted or sent on AWS on the scan date. Many of these companies also run applications there, but the records we read cannot show the rest of the stack, how much they spend, or whether a second cloud is in use.
Why doesn't a website on an AWS address count by itself?
Most such sites sit on a hosting or site-building platform that runs on AWS, so the company itself may have no AWS account; in our hand check, 3 of 4 such sites were platforms. About 54,600 more US companies show only that. They can be added to an order on request, flagged as website address only.
Why don't Route 53 name servers count on their own?
Route 53 shows that the domain's DNS is managed in AWS, not that the site or email runs there, and agencies often manage it for clients. About 21,800 more US companies show only that. They can be added on request, flagged as DNS only.
Will you show which companies moved to or from AWS?
Every scan is dated and kept. A monthly rescan of the same domains shows which companies added or dropped AWS evidence in the last month; that change list is available on request after our next monthly scan.
How many AWS users will my file have?
A national order delivers at least 2,400 companies with a company phone (website and general email where published), and the researched file names a CTO or VP engineering, head of IT or DevOps, founder at small companies at 670 or more of them (670+ with a verified email), within 24-48 hours. The market itself is about 28,700 companies, sized November 2026; a narrowed order covers every one we can verify in that area. If a file comes in under these numbers, we tell you before delivery and refund the difference.
Is this an export from a contact database?
No. Each file is compiled after you order, in 24-48 hours: we pull the sources behind this page again, check every company on its own website, merge duplicates, confirm each named person is in the role today, verify every email at build time and hand-check random rows before delivery. A stored database goes stale as companies open, close and change hands; building at order time avoids that.
Is my file reused or sold to anyone else?
No. Every file is built from scratch for one order, to that buyer's filters: their territory, which companies to keep or leave out, the titles to name. We don't keep a master file to resell, and no buyer's file is ever reused for another order. Two buyers who order the same market each get their own fresh build, so some companies will overlap, but nobody receives someone else's file.
What if some emails bounce?
Every email is verified when the list is built. If any address hard-bounces within 30 days of delivery, reply to your delivery email with the bounced addresses. We re-check each one and replace it with a working address at the same company, or refund that share of your order if we can't. If more than 10% of a file's emails bounce, you can have your money back instead.
How fast is it delivered?
Within 24-48 hours of payment, as a CSV emailed to you, with a permanent download link.
Can it be narrowed to my territory?
Yes. Every list can be narrowed by state, region or city, and this one also by industry, employee band, other tools in use. Reply to your order receipt with the cut you want; the price stays the same.
Where does the data come from?
Public sources: Company websites (homepage code); Public DNS records (mail and verification records); Amazon Web Services published IP address ranges; Business directory records; Verified business contact records. Every row is checked against the company's own website before delivery, emails are verified, and anything we cannot confirm is left out rather than guessed.
Related lists
- Companies using Atlassian (Jira and Confluence) · about 26,600 companies
- Companies using Microsoft 365 · about 479,200 companies
Trade shows where these companies exhibit
- AWS re:Invent 2026 exhibitor list · 441 exhibitors
- ChannelCon 2026 exhibitor list · 159 exhibitors