wordpress-ecs

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #typescript #llm #go #golang #android #machine-learning #rust #deep-learning #linux

(★ 31)

Terraform and packer file to deploy Wordpress on Amazon ECS

wordpress-ecs Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Wordpress on ECS
This project contains `terraform` and `packer` files to provision a Wordpress service on top of AWS EC2 Container Service. It deploys by default in region `us-west-2` and spans two availability zones.

## Instructions
As we're using AWS `ECR` to store our docker containers and that our `ECS` cluster is pulling from it, we'll need to deploy our infrastructure first and then build and push our Wordpress container with `packer`.

What you'll need on your machine
 - packer
 - terraform
 - docker
 - ansible
 
Export your AWS credentials 
```
export AWS_ACCESS_KEY_ID=your_access_key
export AWS_SECRET_ACCESS_KEY=your_secret_access_key
```
Deploy the infrastructure and get the `ECR` url (without the repo name)
```
terraform apply
export ECR_REPOSITORY=$(terraform output ecr_repository | sed 's/\/.*//')
```

Build and push our Wordpress container to `ECR`
```
cd packer
packer build wordpress-packer.json
```

`ECS` agents should automatically pull our freshly pushed Wordpress image and start it. Wait a few minutes and point your web-browser to the `ELB` address:
```
cd ..
terraform output elb_dns
```

## Technical 
We want our wordpress to 
 - scale easily
 - be highly available
 - be secure

#### Making the container stateless
To achieve our goal of easy scalability we want to make our Wordpress container stateless, meaning that no particular data are attached to the host the container is running on. 
Wordpress text article content is stored on an external database so we're good on this side. We'll use a `RDS` mysql instance for that.
Wordpress static content is stored at path `/var/www/html/wp-content` of the container. We'll store this on some storage space shared between hosts and mounted in the container. We'll use the `EFS` service for that (AWS nfs as a service).
We'll use an internal route53 DNS zone to associate simple names to our services:
 - db.wordpress.ael for RDS
 - nfs.wordpress.ael for EFS

We also want to put our ECS instances in an autoscaling group and put an ELB with HTTP healthcheck in front of it (cloudwatch alarms for autoscaling not implemented yet).

#### HA
To achieve HA we'll span our autoscaling group in two different availability zones.
Our RDS and NFS services are accessible to those two zones but are not HA, we should add that for production deployement.

#### Security
We use a dedicated VPC for our project, associate restrictive security groups to instances and put our ECS instances, DB and NFS services in private subnets which access the internet through a NAT (ECS instances need to install nfs-utils at startup and pull ECR repo). Only The ELB resides in the public subnet.

#### Implemented architecture
(NAT and internet gateway are not shown for clarity purposes)
```
us-west-2
+--------------------------------------------------------------+
|                                                              |
|           +----------------+    +----------------+           |
|           |         +-----------------+          |           |
|           |         |      |ELB |     |          |           |
|public     |         +-----------------+          | public    |
|us-west-2a +----------------+ || +----------------+ us-west-2b|
|                              ||                              |
|           +----------------+ || +----------------+           |
|           |                | || |                |           |
|           | +------------+ | || | +------------+ |           |
|           | |ECS instance| | || | |ECS instance| |           |
|           | |            +^------^+            | |           |
|           | +-----^----^-+ |    | +-----^-----^+ |           |
|private    |       |    |   |    |       |     |  | private   |
|us-west-2a +----------------+    +----------------+ us—west—2b|
|                   |    |                |     |              |
|                +--+--+ +-------------+--+--+  |              |
|                | RDS |               | EFS |  |              |
|                +-----+               +-----+  |              |
|                      +------------------------+              |
+--------------------------------------------------------------+
```
# To improve
For production deployments, the following should be implemented:
 - extract logs from Wordpress containers (push to elasticsearch/cloudwatch logs...) 
 - increase instance capacity (t2.micro currently)
 - increase DB size, monitor remaining space and make backups (5GB at the moment)
 - set up CDN to serve static content (AWS one, clouflare, MaxCDN...)
 - set up Cloudwatch alarms on the ASG so we can really autoscale
 - customize Wordpress image for performance (use nginx, php fpm, tweak perf parameters...)

wordpress-ecs

wordpress-ecs Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

wordpress-ecs

wordpress-ecs Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README