What do you think about WordPress on AWS?

Hi all! What do you think about WordPress on AWS? I found a WordPress Docker image, so, probably, if I want to setup failover/autoscaling, AWS could be the solution. Are there hidden pitfalls? Fargate pricing looks reasonable. So why don’t I use AWS for WordPress?
I read this group and haven’t found a discussion about AWS; it looks like AWS isn’t an option for WordPress, but why?

Answers:

I wouldn’t recommend AWS unless you really want to become embedded in the AWS ecosystem. There’s a big barrier for entry due to it’s excessive complexity.

If all you need is a basic semi-scalable website, then something like Digital Ocean or Linode would be more suitable IMHO.

I think you need to implement your own scaling system for it.

A control panel for AWS would be awesome. I don’t think user friendliness is a strong point of AWS unfortunately. It does clearly work though.

AWS is very powerful but very complicated, it was my first venture in cloud servers and wow what a headache. Made switching to Linode and DO very very easy for me. You can get the hang of it but the price is what ultimately made me move, but leaving the configuration headache behind was a big plus. I wouldn’t bother with AWS unless you’re running a seriously huge site than needs some serious scaling ability. And I mean huge cause even a big site can be run a bigger single server or most cloud providers have a load balancer I would go to first before AWS. If you’re just looking to run a Docker container, go with a simple provider.

They are not a host so no, they have control panels to manage the servers themselves, not to manage what you choose to put on them. They are an Infrastructure as a service. If you want a control panel to manager WordPress or website installs you’re looking at a traditional hosting company or if you want a cloud server maybe something like Cloudways or GridPane where they provide you with a software stack that runs on a cloud provider for you and a control panel that you can use to manager your sites over APIs to your cloud providers. If you’re looking to run a Docker container, I would have to think you would need the control panel software in the Docker with the WordPress install, but I’m sure there are ways to have the control panel in one Docker and your application in another but I’m not knowledgeable enough in Docker to know that far.

AWS Control Panel, Cloudformation, Terraform and some others. There are plenty of options when you need to manage your AWS.

I think AWS is complicated for most that are running WP on AWS. That said, if you know how WP works it’s more than scalable and usually less expensive for large scale sites.

There is a template for deploying WordPress on AWS property but it’s about 2-3 years out of date. Should work if you want to give a go.
Running WordPress inside Docker on AWS is a strange and inefficient approach. If you run on AWS you want to use AWS services rather than just EC2. As there are cheaper ways to run Docker.

> If you run on AWS you want to use AWS services
I supposed smth like WordPress docker image in Fargate, some load balancer (ELB?), free certificate by Amazon, MySQL RDS as a database and something as a file storage (don’t know what exactly, S3?) Maybe, CloudFront as CDN. Are you talking about this, or you meant smth different?
> As there are cheaper ways to run Docker.
Could you share a couple of such ways? 🙂 I found articles about WordPress in Docker on Azure, but not sure it’s cheaper 🙂
I’d like to eliminate any maintenance operations. I mean, I want to setup it once and do not do anything – updates, manual scaling, backups, etc.

It’s not feasible to run WordPress without performing regular maintenance. Unless you run it behind a firewall and don’t permit access from the internet at all. I.e. headless WordPress. But it will have limited usefulness.

Hi. Pagely.com has been running Managed WordPress on AWS for about 8yrs now.
It most certainly can be done, at scale, or just a hobbyist site.
AWS actually ends up being a tad bit more expensive then vultr, do, gcp, or whatever current provider is in vogue with this group.. hence why it may not be discussed as much.
It has suited us and our clients well. Give (AWS) a crack for yourself and see what you think.

AWS is definitely an option for WordPress. But you see it depends what kind of a website you are running on WordPress. For example if you are running a cooking blog with 3 to 4 plugins and a simple theme, then AWS is a bit too much for you. You can easily host such a site using DigitalOcean or Vultr.

But if you are running a LMS site where you have hundreds of students signing up daily and learning from the hundreds of courses you have uploaded, then AWS is the suitable option.

I changed to wpms on AWS and love it. Can scale up and down easily. At least 3 geographically separated locations…free or more accutately, automatically part of a server (instance).

I tried setting up myself and did, but there are so many options that i went to an outside guy who did/does everything. I dont use CNN yet but he can set it up in 10 min.

My thought is that i wanted one company that was the besr, that would be able to handle everything i will ever need. Love that feeling.