Wordpress in Docker container on Fargate

Hi

I understand that you would like to host a Simple WordPress application into the Cloud infrastructure. before jumping into your questions, I would like to add my opinion on your request. If you want to host an Simple wordpress application blog/portfolio you can use a small Ec2 instance like t2,t3.micro instance to host your website,

How to host Wordpress in Ec2 AWS ?

Solution 1:

• You can use the Light sail in AWS to host your app in aws, Please check the pricing here https://aws.amazon.com/lightsail/pricing/, This costs are very cheap

Solution 2:

• You can use AWS Ec2 instance which is Micro instance Linux and install and configure the LAMP stack then host your application, Please check the instructions here https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/hosting-wordpress.html

The above solutions 1 & 2 doesn't have scalability and HA, as you said your application you can use any of the above based on your preferred pricing.

Answers to your questions:

1. Yes you can deploy Wordpess and Mysql in container, You can leverage AWS ECS with fargate or EKS Container based solutions. When you are deploying the Wordpress container and Mysql you need to think about persistent storage so if container is dead you shouldn't lose the data in this case for both containers you can use EFS as persistant storage when you are deploying the Containers.

You can find the AWS Example to deploy the Wordpress https://aws.amazon.com/blogs/containers/running-wordpress-amazon-ecs-fargate-ecs/

2. Pricing Calculation for the Wordpress and EFS for 2 pods Example in Ohio region, Please check the Calculation link https://calculator.aws/#/estimate?id=e6da60cc5cba559e452e6829a3fcf121fb0562ae. this link will expire in 3 years.

If you still have any questions, I am happy to help you.

Thank You GK

Answers below. As long as you understand that when the container running the MYSQL DB is killed (for any reason), you will lose your data. When it restarts, the MYSQL DB will be like a fresh install of WP. Hence why most solutions have the DB on EC2 or RDS, so you dont lose data. A more easier solution, based on your use case may be Lightsail: https://aws.amazon.com/blogs/compute/launching-a-wordpress-website-using-amazon-lightsail-containers/

1. It really depends on what you want. If you just want to use Fargate, and run both WP and the DB in containers, then you dont need other services (RDS). And then if you choose this option of using Fargate only, you can choose to have a single container (less preferred), with both WP and a DB, or separate containers for each (more preferred). If you have separate containers for WP and the DP, you can set Fargate to spin up multiple tasks/pods of the WP container (but then will need a shared filesystem like EFS), but only one of the DB (for obvious reasons, otherwise you going to have inconsistent data or data loss). But I suppose if you dont expect much traffic, and only you are adding content, then a single container for both could work, and again Fargate set to run only one task/pod, then that may be ideal for your scenario.
2. Correct, Fargate pricing is based on time the task runs, so if you to run it for an entire month, then set the duration to the number of minutes in a month: 43800. So a .25 vCPU task will cost $324 for a month. (I dont know if .25 CPU will be enough for WP and a DB though...)