WordPress hosting AWS setups look cheap on a pricing calculator, but for most business sites they cost more than managed hosting once you count engineer time, patching, backups, security and bandwidth billing. Running WordPress on EC2, Lightsail or Google Compute Engine makes sense when you need control or custom scale, and you have someone to run the server.
This guide is for business owners, agencies and developers weighing a do-it-yourself cloud build against a managed plan. It covers what you actually own on AWS and Google Cloud, where the billing surprises hide, what you gain in return, and a short decision guide. Cloud facts come from official AWS and Google Cloud documentation, checked in October 2026.
What WordPress hosting AWS really means
When people say WordPress hosting AWS, they usually mean one of two things. The first is Amazon Lightsail, which sells a virtual server bundle with a WordPress image. The second is Amazon EC2, where you rent a virtual machine and build the stack yourself: web server, PHP, database, caching, TLS and backups.
WordPress on AWS is not a WordPress product. It is general-purpose cloud infrastructure that can run WordPress. The same is true of WordPress hosting Google Cloud setups built on Compute Engine. In both cases you get a machine and a network, and the rest is yours to assemble.
Teams that choose WordPress hosting Google Cloud or AWS accept the same deal. That is what people mean by self managed WordPress hosting: you install the WordPress.org software on a server you control and you are responsible for keeping it healthy. Managed WordPress hosting is the same software with the maintenance handled by the provider.
Who owns what: the shared responsibility model
AWS publishes a shared responsibility model that draws the line clearly. AWS is responsible for protecting the infrastructure that runs its services. For EC2, the customer is responsible for managing the guest operating system, including updates and security patches, any application software installed on the instance, and configuring the security group firewall (AWS, as of October 2026).
Google Cloud works the same way for virtual machines. Its VM Manager documentation says the OS Config agent runs patching on each VM using the tools of the Linux distribution, which means you set up and schedule the patching.
WordPress sits on top of all that, so a WordPress hosting AWS build adds your application layer to the list. Core, plugins, themes, PHP versions and the database are yours too. The table below shows how the work divides.
| Task | DIY on AWS or Google Cloud | Managed WordPress hosting |
|---|---|---|
| Server OS patches | You | Host |
| PHP and database upgrades | You | Host |
| Firewall and malware scanning | You choose and configure | Host |
| Backups and restore tests | You build and verify | Host, self-service restore |
| Caching and performance tuning | You | Host |
| TLS certificates | You (renewal included) | Host |
| Staging site | You build it | Included |
| WordPress-specific support | Not covered by the provider | Included |
| Bandwidth and storage billing | You monitor it | Plan limits stated up front |
Why WordPress hosting AWS costs more than the calculator says
The instance price is the smallest part of the bill. A WordPress hosting AWS build costs money in four other places, and each one is easy to overlook.
- Engineer time. Initial setup, hardening and tuning take hours. Every month brings patches, plugin updates and the occasional incident.
- Backups. Snapshots are billed by the gigabyte. On Lightsail, AWS lists snapshots at a flat monthly rate per GB (as of October 2026), so a long retention history grows the bill every month.
- Security tooling. A web application firewall, malware scanning and vulnerability monitoring are separate products you must choose, install and watch.
- Data transfer. Traffic leaving the cloud is billed, as covered below.
Add those up and the comparison changes. A managed plan that looks pricier on paper may be the cheaper way to run the same site. Our own WordPress hosting plans start at $29 per month on annual billing, with backups, security and support included.
Billing surprises on AWS and Google Cloud
Cloud bills are usage bills. That is a strength when you want to scale, and a risk when a plugin, a bot or a viral post drives usage up. Three line items cause most of the surprises.
The first is egress. AWS gives customers 100 GB of free data transfer out to the internet per month, aggregated across services (EC2 pricing page, October 2026), and charges tiered rates beyond that. On Lightsail, both inbound and outbound traffic count against your bundle allowance, and outbound traffic above it is billed per GB at rates that vary by Region.
Google Cloud bills the same way. Its network pricing page says inbound transfer is free, but responses to requests count as data transfer out and are charged (as of October 2026). A site that serves large images and video from the server itself will notice.
The second is storage that keeps growing. Snapshots, old volumes and detached disks continue to bill after you stop using them. The third is the supporting cast: load balancers, static IP addresses, NAT and monitoring each add their own line.
Put plainly, WordPress hosting AWS is billed by usage, and managed hosting is billed by plan. None of this is hidden, since it is all documented. It does mean you need budgets, alerts and a person who reads the bill. A managed plan with fixed visit limits and no per-gigabyte overage shifts that risk to the host. We do not bill overages on our plans.
Support on WordPress hosting AWS: what you get and what you do not
AWS Basic Support does not include technical support. Its documentation says it offers assistance for account and billing questions and service quota increases (as of October 2026). Help with EC2 operating systems and the performance of popular third-party software is part of the Business Support+ plan and higher, which carries its own monthly charge.
Even then, support for WordPress on AWS covers the cloud and the operating system. Nobody on the provider side owns your WordPress site. If a plugin conflict takes your checkout down at 9 p.m., the ticket is yours to solve.
Managed hosting inverts that. Staff who work with WordPress every day answer when something breaks. For a business site, that is often the real product. Our guide to managed WordPress hosting lists what a good plan should cover.
Security work you inherit with self managed WordPress hosting
Security is where a WordPress hosting AWS build most often goes wrong. Self managed WordPress hosting hands you the whole security stack. That starts with the operating system and the security group rules, and extends to PHP, the database, file permissions, SSH keys and every plugin you install.
WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.0 or greater, and HTTPS on every install (as of October 2026). Keeping to that baseline means scheduling upgrades, testing them on a copy of the site and rolling back when they fail.
Good secure WordPress hosting layers a firewall, malware scanning, account isolation, vulnerability monitoring and tested backups. On a DIY server you pick each layer, pay for it and respond to its alerts. Our plans include Imunify360 and Patchstack vulnerability protection at the server, so that work is done before you open the dashboard.
What you gain with WordPress cloud hosting you run yourself
None of this means a DIY build is a mistake. WordPress cloud hosting on AWS or Google Cloud gives you real advantages that managed plans rarely match.
- Full control. Root access, custom PHP extensions, your own web server configuration and any software you want alongside WordPress.
- Elastic scale. Load balancers, autoscaling groups, separate database servers and object storage let you design for very large or spiky traffic.
- Ecosystem. If the rest of your product already lives on AWS or Google Cloud, keeping WordPress next to it simplifies networking and compliance reviews.
- Custom architecture. Headless builds, multi-region setups and unusual integrations are easier on raw infrastructure. Our headless WordPress guide covers one such case.
The catch with WordPress hosting AWS is that these benefits require skill. A team that can design, monitor and rebuild the stack gets value from the freedom. A team that wanted a website gets a part-time infrastructure job.
AWS vs managed WordPress hosting: a decision guide
Use this short guide to settle the AWS vs managed WordPress hosting question for your own site. It applies equally to a Google Cloud build.
- Do you have an engineer who will own the server? If not, choose managed. A server without an owner is the most common cause of a hacked cloud site.
- Is your traffic ordinary? Sites under a few hundred thousand visits a month rarely need autoscaling. A managed plan is cheaper and simpler.
- Do you need software or configuration a managed host will not allow? If yes, a VPS or cloud server is justified. Our VPS web hosting is a middle path with root access and a simpler bill than a hyperscaler.
- Is WordPress one part of a larger AWS or Google Cloud system? If yes, DIY may fit, with a clear owner and budget alerts.
- Does an outage cost real money? Then price in monitoring, tested restores and on-call time before you compare monthly totals.
For stores, the stakes are higher still. See WooCommerce hosting requirements before you decide where a checkout will run.
Moving from a DIY cloud server to managed hosting
Many teams start with WordPress on AWS or Google Cloud and move once the maintenance burden outgrows the savings. The move is routine. Take a full backup, copy files and database to the new host, test on a temporary URL, check forms and logins, lower DNS time-to-live a day ahead, then switch DNS.
Our team does the migration by hand and does not charge for it. You can request one on the website transfer page, and we back plans with a 30-day money-back guarantee. If you want to talk through whether WordPress hosting AWS or managed hosting suits your site, contact us.
Frequently asked questions
Is WordPress hosting AWS cheaper than managed hosting?
For WordPress hosting AWS builds, sometimes the monthly server charge is lower, but the total usually is not. Patching, backups, security tools, monitoring and your own time are all costs you carry on AWS. Managed hosting bundles them into a fixed price.
Can I run WordPress on Google Cloud?
Yes. WordPress hosting Google Cloud setups use Compute Engine, which runs WordPress like any Linux server, and you install and secure the stack yourself. Google documents VM patching through its OS Config agent, but the setup and the schedule are yours.
Does AWS provide WordPress support?
AWS Basic Support covers account, billing and quota questions, not technical issues (as of October 2026). Higher paid plans add help with EC2 operating systems and the performance of common third-party software, but they do not manage your WordPress site for you.
What is the biggest billing surprise with WordPress hosting AWS?
Data transfer out is the usual one. AWS includes 100 GB per month free, and traffic beyond that is charged by tier. Snapshots and unused volumes also keep billing until you delete them.
When does self managed WordPress hosting make sense?
A WordPress hosting AWS or Google Cloud build makes sense when you have a technical owner, need custom software or architecture, or run WordPress inside a larger cloud system. For a business site without an engineer, managed hosting is the safer choice.
Sources
- AWS, shared responsibility model
- AWS, Amazon EC2 on-demand pricing and data transfer
- AWS, Amazon Lightsail pricing
- AWS, Support plans
- Google Cloud, network pricing
- Google Cloud, VM Manager OS patch management
- WordPress.org, recommended requirements
Related reading: WordPress hosting cost, what is WordPress hosting and shared vs dedicated WordPress hosting.