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

Production WordPress on AWS

WordPress on AWS built so it can survive an instance dying, not just a traffic spike.

Price and scope

From $399

Typically $399–$999, 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

  • WooCommerce, where the cart and the sessions cannot be cached the way pages can
  • Multisite, which changes how media, domains and the database are laid out
  • A live site with real traffic, so the build happens in parallel and cuts over

Some of this you can check yourself, right now, for free: WordPress Security Check →

Why a WordPress instance cannot be duplicatedOne EC2 instance running the web server, MySQL and the uploads directory together. A second instance cannot be added, because half the media library lives on the first instance's local disk.ONE EC2 INSTANCEnginx + PHPMySQLsame box, every page viewwp-content/uploadson the local diskTHE SECOND INSTANCEcannot be added:half the media libraryis on the other disk
Production WordPress on AWS

What actually goes wrong

WordPress on AWS usually means one EC2 instance running the same LAMP stack the shared host was running — the identical single point of failure, except now you own the patching and pay more for it. The thing that quietly prevents ever fixing it is the media library: uploads land on the instance's own disk, so a second instance would serve half the images, and a rebuild would lose them. Underneath that, every uncached page view goes to a MySQL on the same box, which is why the site falls over at exactly the moment it starts doing well.

How I find it

  • wp option get home && wp option get siteurl — what the database thinks the site is
  • du -sh wp-content/uploads on the instance, against what is in S3, which is usually nothing
  • SHOW GLOBAL STATUS LIKE 'Threads_connected' under real traffic, not at rest
  • curl -sI against a cold URL, reading the cache headers a logged-out visitor actually receives

What you get

  • Media moved to S3 and served through CloudFront, so the instance holds no state worth losing
  • A page cache and an object cache, with the invalidation rules WooCommerce needs if it is present
  • Database on RDS with automated backups, separate from the instance serving PHP
  • Automatic security updates for core and plugins, with a staging path for anything larger
  • A restore tested end to end — the site rebuilt from backup, timed, before you rely on it

Questions

Is AWS actually better than managed WordPress hosting?

Often not, and I will say so. If you run one marketing site with no unusual requirements, a good managed host is cheaper and better than anything I would build you. AWS earns its keep when you need it inside your own network, alongside other infrastructure, or under compliance rules a shared platform cannot meet.

Will my plugins still work after this?

Almost all of them. The two that occasionally object are ones writing directly to the uploads directory and ones caching in a way that conflicts with the object cache — both are found during the build, on a copy, not after you have gone live.

Can you do this without taking the site down?

Yes. The new environment is built alongside the existing one and verified against a hosts-file override before any DNS changes, so the only interruption is the cutover you plan for.

What does it cost to run on AWS afterwards?

For a typical business site, a small instance, a small RDS and CloudFront transfer — usually comparable to mid-tier managed hosting rather than dramatically cheaper. I will give you the estimate from your actual traffic before you commit, because "cheaper" is the claim this work most often fails to deliver.

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.