Wordpress Site in AWS

S3 Buckets

- Create new bucket (BucketCode) for Wordpress code in region EU (Ireland).
- Create new bucket (BucketMedia) for Wordpress images in region EU (Ireland).

CloudFront

- Create a new CloudFront Web distribution

Security Groups

- Create a Web DMZ and RDS security group

Web DMZ

RDS

RDS Instance

- Create RDS Instance

IAM

- Create Role to access S3 from EC2
- Add AmazonS3FullAccess policy to the role.
- Role name: MyEC2S3Role

Launch EC2

- Provision your EC2 instances.

#!/bin/bash
yum update -y
yum install httpd php php-mysql -y
cd /var/www/html
echo "healthy" > healthy.html
wget https://wordpress.org/wordpress-5.1.1.tar.gz
tar -xzf wordpress-5.1.1.tar.gz
cp -r wordpress/* /var/www/html/
rm -rf wordpress
rm -rf wordpress-5.1.1.tar.gz
chmod -R 755 wp-content
chown -R apache:apache wp-content
wget https://s3.amazonaws.com/bucketforwordpresslab-donotdelete/htaccess.txt
mv htaccess.txt .htaccess
chkconfig httpd on
service httpd start
                                            

Test EC2

- Get your public IP addres of your EC2 instance. - SSH into your instance.

sudo su
cd /var/www/html

cat .htaccess

service httpd status

cd wp-content
cd uploads
cd 2020
cd 02
ls

cd wp-content
cd /var/www/html
aws s3 ls
aws s3 cp --recursive /var/www/html/wp-content/uploads s3://BucketMedia

cd wp-content
cd /var/www/html
aws s3 ls
aws s3 cp --recursive /var/www/html s3://BucketCode
aws s3 ls s3://BucketCode

aws s3 sync /var/www/html s3://BucketCode

cd /etc/httpd
cd conf
cp httpd.conf httpd-copy.conf
nano httpd.conf

service httpd restart

S3 Bucket Policy

- Use the followting policy for your S3 Bucket (BucketMedia) Policy
- Make sure to update the arn with yours

{
"Version": "2012-10-17",
"Statement": [
    {
    "Sid": "PublicReadGetObject",
    "Effect": "Allow",
    "Principal": "*",
    "Action": [
        "s3:GetObject"
        ],
    "Resource": [
        "arn:aws:s3:::BUCKET_NAME/*"
        ]
    }
]
}

Application Load Balancer

Navigate to EC2 > LOAD BALANCING > Load Balancers > Create Load Balancer > Application Load Balancer

Route 53

Point our domain to our Application Load Balancer
Navigate to Route 53 > Hosted Zones > Your Hosted Zone > Create Record Set

Place EC2 instances into our Target Group

Navigate to EC2 > LOAD BALANCING > Target Groups > Select your targer group > Targets Tab > Edit > Select EC2 instance > Add to registered

High Availability Architecture

- The EC2 instance 34.239.132.188 is our current EC2 instance
- This instance will be our writer node. Everytime the marketing team writes a new blog they will be navigating directly to this instance.
- This instance will be configured to push any changes to our S3 bucket
- We will have a fleet of EC2 instances that will constantly poll the S3 bucket for changes.
- When people visit our domain Route 53 will redirect them to our fleet (group) of EC2 instances on the right of the picture.
- SSH into you current EC2 instance and go to the etc folder.
- This instance will be our base for all other instances (reader nodes) that will be launched.
- Reader node will scan S3 for any changes and do updates if neccessary.

cd /etc
nano crontab
*/1 * * * * root aws s3 sync --delete s3://BucketCode /var/www/html

Create AMI

Navigate to EC2 > Instances > Select your instance > Actions > Image > Create Image

Create Writer Node

SSH into your EC2 instance.
We essentially going to change this instance from a reader node to a writer node, as we have a AMI of a reader node already.

sudo su
cd /etc
nano crontab
*/1 * * * * root aws s3 sync --delete /var/www/html s3://BucketCode
*/1 * * * * root aws s3 sync --delete /var/www/html/wp-content/uploads s3://BucketMedia

Save file and then do a test to see if your writer instance is working:
Execute following code in your EC2 terminal and then check if file is in your S3 bucket.

cd /var/www/html
echo "This is a test" > test.txt
service crond restart
service httpd status

Create Auto Scaling Group

- Navigate to EC2 > AUTO SCALING > Launch Configurations > New configuration
- Click on My AMIs under Choose AMI and select your MyWPReadNode AMI

Remove Write Node

- Navigate to EC2 > LOAD BALANCING > Target Groups > Targets > Edit
- Remove Write node from Registered targets

Surf your Domain