Home / Cost to scrape / Bot protections / Site behind AWS WAF
Cost to scrape a site behind AWS WAF at 10K, 100K, and 1M
Scraping 100,000 pages behind AWS WAF costs from $142.50 a month on Bright Data Web Unlocker and Web Scraper API (Web Unlocker Pay as you go plan), which charges $0.0015 a page.
Check Bright Data Web Unlocker and Web Scraper API's pricing
Bright Data Web Unlocker and Web Scraper API checked Oct 12, 2026; each vendor's own page is linked with its rate.
- 10,000 a month
- $7.50Bright Data Web Unlocker and Web Scraper API, Web Unlocker Pay as you go
- 100,000 a month
- $142.50Bright Data Web Unlocker and Web Scraper API, Web Unlocker Pay as you go
- 1,000,000 a month
- $1,100.20Bright Data Web Unlocker and Web Scraper API, Web Unlocker Scale $999
How hard to scrape: Very hard, with rate limits, CAPTCHAs, bot fingerprinting, IP reputation checks, pages built by JavaScript and TLS fingerprinting in the way; JavaScript rendering needed.
Target access and billing context
Access
Easy means no protection is recorded; moderate, rate limits or fingerprinting without CAPTCHAs; hard, CAPTCHAs and IP checks that usually call for residential proxies; very hard, all of that plus measures such as TLS fingerprinting, a login wall in front of most data or honeypot links.
Protections in the way
Terms
No terms URL is recorded for this target.
What you scrape moves the bill more than who you buy from. A target that forces JavaScript rendering or a residential exit multiplies the meter before any plan is chosen.
What each API charges for a site behind AWS WAF
1 API publishes a rate for a site behind AWS WAF. Each figure is the cheapest of that API's current plans for the volume, from its own page.
| API | 10,000 a month | 100,000 a month | 1,000,000 a month | Costs | What you get | Choose a location | Source |
|---|---|---|---|---|---|---|---|
| Bright Data Web Unlocker and Web Scraper APIchecked Oct 12, 2026 | $7.50Web Unlocker Pay as you go | $142.50Web Unlocker Pay as you go | $1,100.20Web Unlocker Scale $999 | $0.0015 a page | HTML or parsed fields | Country | source |
How to tell a site uses AWS WAF
AWS WAF Bot Control lets a site on AWS monitor, block, rate-limit or challenge bots such as scrapers and crawlers, and can now charge AI bots for access. AWS WAF's own page, read Oct 11, 2026.
| Look for | What it is | Source |
|---|---|---|
aws-waf-token cookie | The encrypted token AWS WAF's challenges and SDKs store, which fingerprints the browser session. | source |
What a blocked request gets back: With the Monetize action, a request gets an HTTP 402 Payment Required challenge with payment instructions instead of the page.source
Whether a blocked request still costs credits depends on the API: most bill only successful requests, and each one's own rule for a 403, a 429 and a 5xx is quoted in the answer linked below.
Every way to get the data from a site behind AWS WAF
No API documents an endpoint built for a site behind AWS WAF; each one reaches it through its general scraping endpoint, at the rates above.
Official API: AWS WAF is a protection a site switches on, not a content platform; any official API belongs to the protected site.
Terms: There is no single terms document for sites behind AWS WAF; each protected site's operator sets its own content terms and access policy.
What the bill depends on
Getting past AWS WAF is bought as a mode, not as a separate product: a stealth or premium proxy, JavaScript rendering, or a named bypass, each with its own credits per request. The table prices the mode each API’s own pages name for AWS WAF. Most of these APIs bill only requests that come back with the page, so a failed attempt costs time rather than credits, but check the vendor’s rule before a large run.
Not in the table
Scrapfly sells a bypass for this protection, but its price is a floor rather than a rate: “The Unblocker starts at 30+ credits per request, scaling with target complexity” (Scrapfly, read Oct 11, 2026). ZenRows shows its adaptive mode getting through AWS WAF but bills whichever configuration succeeds, so it has no fixed price for it (ZenRows, read Oct 11, 2026).
Evidence to check before buying
- A mode that gets past AWS WAF on one site can fail on another, because each site sets its own rules; run a few hundred requests against your own target before you choose a plan.
- A price for getting past a protection is not permission to scrape the site behind it; the site’s own terms still apply.