- Moving to AWS pays off when a site has outgrown shared hosting limits and someone will look after the server.
- Amazon Lightsail offers WordPress instances, managed databases, snapshots, static IPs and load balancers at predictable prices, which suits most business sites.
- EC2 with separate database and storage services gives more control but needs more DevOps skill and ongoing work.
- A safe move uses a staging copy, a tested backup, a short DNS cutover and HTTPS from day one.
- If nobody will patch, back up and monitor the server, managed WordPress hosting is usually the better choice.
Is it worth moving a WordPress site from shared hosting to AWS?
It is worth it when your site has outgrown shared hosting, through traffic, resource limits, slow admin screens or a need for staging and automated deployments, and when someone will manage the server properly. For most business sites, Amazon Lightsail is the simplest AWS route; EC2 with separate database and storage services suits larger or more complex sites. If nobody will patch, back up and monitor the server, a managed WordPress host is usually the safer and cheaper choice.
Our cloud and DevOps team moves WordPress sites to AWS regularly. Here is how we decide whether a move makes sense.
Which signs show you have outgrown shared hosting?
- The site slows down or shows errors at busy times, and the host points to resource limits.
- The WordPress admin is slow even when the public site seems fine.
- You need a proper staging copy and deployments from a code repository.
- Your host restricts server settings, PHP versions or background jobs you need.
- Other sites on the same server have caused outages or security warnings.
If none of these apply, a move may cost more effort than it saves. Often the better first step is to fix the site itself: remove unused plugins, optimise images and add page caching, then measure again. Plenty of slow sites become fast without changing host at all.
What does Amazon Lightsail offer?
AWS describes Lightsail as a simpler way to run projects, bundling instances (virtual private servers), managed databases, SSD storage, snapshots for backups, data transfer, DNS management, static IPs and load balancers at a low, predictable price. Its WordPress guide walks through launching a WordPress instance, connecting a domain, enabling HTTPS and signing in, and notes that the guided setup can take up to 15 minutes to configure the instance. For most business sites, a Lightsail instance with snapshots, a static IP and HTTPS is enough.
When is EC2 the better choice?
| Need | Lightsail | EC2 and related services |
|---|---|---|
| Simple setup and predictable bills | Strong fit | More setup, usage-based billing |
| Separate managed database | Available | Wide choice of database options |
| Auto scaling for traffic spikes | Limited | Strong fit |
| Fine-grained networking and permissions | Basic | Full control |
| Skills needed to run it | Moderate | Higher |
Busy stores, membership sites with many logged-in users and sites with strict compliance needs are more likely to justify EC2 and its related services.
What does a safe migration look like?
- Audit the current site: WordPress, PHP and plugin versions, cron jobs, email settings and any custom server rules.
- Take a full backup of files and database, and confirm it restores.
- Build the new server with the right PHP version, caching, a firewall and HTTPS.
- Copy the site to a staging address on the new server and test forms, checkout, logins and search.
- Lower the DNS time-to-live a day before the switch so changes spread quickly.
- Freeze content changes briefly, copy the final database, and point DNS to the new server.
- Check everything again on the live domain, and keep the old hosting until the new server has proved itself.
Moving a site that is also being redesigned? Plan the SEO side carefully with our website redesign SEO checklist.
What usually breaks during a move?
- Email from the site: contact forms and order emails often relied on the old host's mail server. Send them through a proper email service with authentication instead.
- Scheduled tasks: WordPress cron jobs, backups and imports that ran on the old server need to be set up again.
- Hard-coded URLs and paths in themes, plugins or the database.
- File permissions that stop uploads or updates on the new server.
- Caching and security plugins that were tuned for the old host and now conflict with server-level caching.
What should you check after the switch?
Submit a test enquiry through every form, place a test order if you sell online, log in as an editor and publish a draft, and confirm that backups and snapshots are actually being created. Watch error logs and response times for the first days, check that search engines can still crawl the site, and only then cancel the old hosting.
What does running the server involve?
On shared hosting, the host looks after the server. On AWS, that work becomes yours or your agency's:
- Operating system, PHP and web server updates.
- WordPress core, theme and plugin updates, tested on staging first.
- Automatic snapshots and off-server backups, with regular restore tests.
- Uptime, error and resource monitoring with alerts.
- Security hardening, firewall rules and access management.
Our guides to monitoring a production web app and CI/CD for small teams cover two of these jobs in detail. Ongoing maintenance and security plans exist precisely so this work does not fall through the cracks.
How do the costs compare?
Shared hosting is cheap because the server is shared and managed for you. On AWS, you pay for the server, storage, backups and data transfer, plus the time to manage it. Lightsail bundles most of this into a fixed monthly price per instance, while EC2 bills by usage. Check the current AWS pricing pages for your region and expected traffic, and include management time in the comparison, not just the hosting bill.
When is managed WordPress hosting better?
If your goal is a faster, more reliable site without taking on server work, a good managed WordPress host may give you most of the benefit: staging, daily backups, caching and updates included. AWS makes most sense when you need control, integration with other AWS services, or a platform your WordPress developers and DevOps team will actively manage.
Frequently asked questions
Will moving to AWS make my WordPress site faster?
Often, but not automatically. Dedicated resources remove the slowdowns caused by other sites on a shared server, but slow themes, heavy plugins and large images stay slow anywhere. Measure before and after, and fix the biggest front-end issues as part of the move.
Is AWS more secure than shared hosting?
It can be, because your site no longer shares a server with others, but security depends on how the server is set up and maintained. Firewalls, updates, strong access controls, backups and monitoring are your responsibility on AWS. Without them, a self-managed server can be less secure than good shared hosting.
Can we move email to AWS as well?
Usually email stays with a dedicated email provider, such as Google Workspace or Microsoft 365, and only the website moves. Running your own mail server adds deliverability and security work that most businesses do not need. Keep the existing email DNS records unchanged during the website move.
How long does the migration take?
A typical small business site can be copied, tested on staging and switched over within a few days, most of which is testing. The final cutover itself is short. Large stores or sites with heavy custom code take longer because more flows need checking.
What happens if something goes wrong after the switch?
Keep the old hosting active until the new server has run smoothly for a while. If a serious problem appears, you can point DNS back to the old server while you fix it. Lower the DNS time-to-live before the move so a switch back takes effect quickly.
Last updated