Set Up and Monitor a WordPress Instance
(AWS Solutions Architect : Associate Level)
Business Scenario
A startup that wishes to publish blogs and provide documentation services for other businesses and technologies, requires the following:
- To set up a live WordPress instance to publish blogs
- To set up a WordPress instance that can be used for development and testing purposes so that any work done on this instance will not impact the live blog
- To configure the WordPress instance for development and testing purposes, which will be available only for business hours (9 AM–6 PM)
- To monitor the health of the WordPress instance
My Solution
Step 1.0 = I created/configured an “AWS Instance Scheduler” in AWS CloudFormation. And I named thist stack as “Assessments2-InstanceScheduler”.
Step 1.a – You can find the AWS Instance Scheduler Template in this link https://aws.amazon.com/solutions/implementations/instance-scheduler/
Step 1.b – I edited the Instance-Scheduler’s DynamoDB Table, and set the begintime to 9.00 and endtime to 18.00 and selected the ‘US/Pacific’ and ‘Europe/London’ timezones.
Step 2.0 = Under AWS CloudFormation, I created a new stack with the help of “WordPress Blog” Sample-Template. And I names this stack “Assessment2-WordpressStack”.
Step 2.a – Using the stack’s Website URL, I installed-&-configured Wordpress on the instance.
Here is the Website’s URL = http://ec2-54-221-6-167.compute-1.amazonaws.com/wordpress.
(Please note that the Instance may be in the “Stopped State” because of the Set-Scheduled-Timings)
Step 2.b – I added the TAGS for the instance so that Lambda will be able to link the instance with the Instance-Scheduler.
Step 2.c – I created an AMI (image) of this instance and named the image “Assessment2-WordpressInstanceImage”.
Step 3.0 = Created a new HealthCheck.
Step 3.a – In AWS Route53 and under Health checks, created a new HealthCheck using the Domain.
Step 3.b – Checked and confirmed that the instance was Healthy.
Final Result = The Wordpress Website is Deployed..