About Expertise Work Managed Apps
Business Website Online Store Sales CRM Team Drive Online Academy Newsletter System Booking System Shared Inbox Knowledge Base Short Links Business Manager Photo Gallery Survey Platform Community Forum Project Boards Estate Agency Car Workshop Restaurant Clinic Photography Studio
AWS
Assess & advise Build & migrate Automate & operate Secure & comply Urgent & go-live
Projects
Hosted Monitoring & Dashboards Self-Hosted Observability Stack Bulk Document Data Extraction Email Deliverability Diagnosis & Repair SEO Migration Recovery AWS Security Review VPS Hardening & ModSecurity Cloud Architecture & Resilience Review SSL & Server Configuration Container Security Review DNS & Email Troubleshooting DevOps Deployment & Rollback Review WordPress Hardening Retainer Data Pipeline Rerun Review Metric Reconciliation
Free Tools
Website Health Check Email Domain Health Check DNS Health Check SSL Certificate Checker Redirect Chain Checker Robots.txt Checker XML Sitemap Validator Docker Compose Checker WordPress Security Check AWS IAM / S3 Policy Checker Domain Registration Lookup Uptime Monitoring Trial Downtime Cost Calculator AWS Cost Estimator Cloud Architecture Self-Assessment DevOps Engagement Builder Self-Managed VPS vs Managed AWS
Blog Certifications Hire Me

AWS WAF & Edge Protection

Rules tuned against your real traffic, in count mode first, so nothing legitimate gets blocked.

Price and scope

From $349

Typically $349–$749, fixed in writing before anything starts.

2–4 days
Working days, counted from the moment I have access — not from the day you agree.

What moves it up

  • Tuning against live traffic rather than deploying a default rule set and hoping
  • An API as well as a website, where the two need genuinely different rules
  • A login or checkout path that needs its own rate limit separate from everything else

Some of this you can check yourself, right now, for free: Website Health Check →

A WAF that is mostly countingTraffic reaching a web ACL where one rule group blocks and three are set to count after false positives, plus a path that reaches the load balancer directly, bypassing the web ACL entirely.trafficWEB ACLrate limitblockingcommon rule setcount since MarchSQL injection setcount, false positivebad inputs setcount, never revisitedload balancerits DNS name still answers directly
AWS WAF & Edge Protection

What actually goes wrong

WAF gets deployed the way a smoke alarm gets installed by someone who then takes the battery out. The managed rule groups go on in block mode straight away, something legitimate trips a rule within a fortnight — an admin pasting SQL into a form, a webhook with an unusual user agent — and rather than tune it, the rule group goes to count mode "temporarily" and stays there. What is left is a WAF that costs money every month and blocks nothing. The other half is scope: the rules sit on CloudFront while the load balancer behind it is still reachable directly.

How I find it

  • aws wafv2 list-web-acls, then get-web-acl — how many rules are actually in block mode
  • aws wafv2 get-sampled-requests — real requests a rule matched, before deciding to enforce it
  • The ALB's DNS name requested directly, to see whether the edge can be bypassed entirely
  • aws wafv2 get-web-acl-for-resource for every public resource, not just the one you remember

What you get

  • Managed rule groups deployed in count mode first and tuned against your own traffic before enforcing
  • Rate limiting on the paths that need it — login, checkout, expensive endpoints — not one global limit
  • The origin locked so the load balancer cannot be reached around the edge
  • Logging to a place you can query, so a block can be explained to whoever it blocked
  • A written list of what is enforced, what is counting, and what would have to happen to enforce the rest

Questions

Will a WAF block real customers?

It will if you deploy it in block mode on day one, which is why nothing here is enforced until it has spent time counting against your real traffic. False positives get found in the log, not in a support ticket.

Does this stop a DDoS attack?

Shield Standard is already protecting you at layer three and four, at no cost. WAF handles the application layer — request floods, bad bots, credential stuffing. A genuinely large volumetric attack is Shield Advanced territory, which is a serious monthly commitment and I will tell you if you are nowhere near needing it.

How much does AWS WAF cost to run?

A few dollars a month for the web ACL and rules, plus a charge per million requests. For most sites this size it is a small line — the cost that surprises people is the logging, which is why retention gets set with everything else.

Can you tell me what it has actually blocked?

Yes, and that is part of the point. Logging goes somewhere queryable so any block can be traced to a rule and a request, which is what makes tuning possible rather than guesswork.

S3 + CloudFront Website / CDN

Static hosting where the bucket is private, the certificate is right, and deploys invalidate the cache.

From $249 1–3 days

Want this done?

Tell me what you are running and I will come back with a fixed price and a date. If it turns out you do not need this, I will say that instead.

Prefer to talk? Book a free call ↗  ·  Or hire me on Upwork ↗  ·  Typical reply within one business day.

When I answer

Sunday to Thursday, 09:00–18:00 EET. Outside that I will still look, but I will not promise a time.

No 24/7 desk, and I will not pretend otherwise

One person, one time zone. If round-the-clock cover is what you need, you need a team, and I will say so rather than sell you a plan that cannot deliver it.

Your AWS bill stays yours

You pay Amazon directly and you keep control of the account. Nothing here resells your infrastructure or sits between you and your own billing.

A price that starts with "from" is a starting price

Every service page lists exactly what pushes a quote above it, before you ask. You get a fixed number in writing before any work begins.