OPS705 Assignment 2

In this assignment, you will install a WordPress blog in AWS using Elastic Beanstalk and RDS. You will construct this assignment in our AWS Academy Learner Lab classroom.

Unlike labs, assignments have minimal instructions. You are given specifications on what the assignment needs, and you must rely on your previous work in the course. If the assignment doesn't have the command you need, you can find it in your labs. As with Assignment 1, don't be afraid to do a little research!

Assignments in OPS705 are built as an assessment of your ability to meet the course objectives.

Task 1: Networking

In this task, you will create all the networking required for your new web application.

Virtual Private Cloud

Create a new VPC with the following settings:

1. VPC only
2. Name: Wordpress VPC
3. IPv4 CIDR: 10.0.0.0/16
4. Leave all other settings on default

Once created, modify this VPC with the following actions:

1. Edit DNS hostnames: Enable

Subnets

Create two private IPv4 subnets in this VPC:

1. Private Subnet 1 – 10.0.1.0/24 – us-east-1a
2. Private Subnet 2 – 10.0.2.0/24 – us-east-1b

Create two public IPv4 subnets in this VPC:

1. Public Subnet 1 – 10.0.11.0/24 – us-east-1a
2. Public Subnet 2 – 10.0.12.0/24 – us-east-1b

Edit your public subnets with the following settings:

1. Enable auto-assign public IPv4 address
2. Enable resource name DNS A record on launch

Internet Gateway

Create a new Internet Gateway with the following:

1. Name: Wordpress Gateway
2. Once created, attach it to your Wordpress VPC.

Route Tables

Edit your default route table for your Wordpress VPC and add the name: VPC-local Route Table

Create a second route table:

1. Name: Wordpress Website Route Table
2. VPC: Wordpress VPC
3. Routes Entry 1:
   1. Destination: 10.0.0.0/16
   2. Target: local
4. Routes Entry 2:
   1. Destination: 0.0.0.0/0
   2. Target: Internet Gateway – Wordpress Gateway

Security Groups

Create a security group with the following settings:

1. Name: Wordpress Website SG
2. Description: Allows HTTP traffic inbound
3. VPC: Wordpress VPC
4. Inbound Rule:
   1. Type: HTTP
   2. Source: Anywhere – IPv4 (0.0.0.0/0)

Create a security group with the following settings:

1. Name: Wordpress Database SG
2. Description: Allows MySQL traffic locally
3. VPC: Wordpress VPC
4. Inbound Rule:
   1. Type: MYSQL/Aurora
   2. Source: Custom (Select Wordpress Website SG in the search field)

Edit both public subnets’ route table associations to: Wordpress Website Route Table

Task 2: Database

Create a new RDS instance with the following settings:

1. Engine options: MySQL
2. Templates: Free tier
3. DB instance identifier: wordpress-db
4. Master username: admin
5. Auto generate a password
6. DB instance class: db.t3.micro
7. Allocated storage: 5
8. Enable storage autoscaling: Unchecked
9. Virtual private cloud (VPC): Wordpress VPC
10. Subnet group: Create new DB Subnet Group
11. Public access: Yes
12. VPC security group: Choose existing, remove default VPC, add Wordpress Database VPC
13. Availability Zone: us-east-1a
14. Additional configuration, Initial database name: wordpress
15. Enable automated backups: Unchecked
16. Enable encryption: Unchecked
17. Enable Enhanced monitoring: Unchecked

Once the database has finished creating, click on the View connection details button by the green success message at the top of the page. This gives you your database password.

Store the Master username, Master password, and Endpoint in a saved document. You’ll need it later.

Task 3: Elastic Beanstalk

Create a new Elastic Beanstalk application with the following settings:

Main settings

1. Application name: wordpress
2. Platform: PHP
3. Application code: Upload your code
4. Choose file: Downloaded wordpress source code zip file
5. Version label: wordpress-versionnumber (Example: wordpress-5.9.3)

Configure more options

1. Software > Document root: /wordpress
2. Security > Service role: LabRole
3. Security > EC2 key pair: vockey
4. Security > IAM instance profile: LabInstanceProfile
5. Monitoring > System: Basic
6. Managed updates > Enabled: Unchecked
7. Notifications: YourSenecaE-mailAddress
8. Network > VPC: Wordpress VPC
9. Network > Public IP address: Checked
10. Network > Instance subnets: Public Subnet 1, Public Subnet 2 (both checked)
11. Network > Database subnets: Private Subnet 1, Private Subnet 2 (both checked)
12. Instances > Wordpress Website SG (both checked)
13. Create the application.

While you wait for the creation to complete, check your e-mail to confirm your notification subscription.

Task 4: Site Configuration

Open the URL presented in the Wordpress EBS instance and begin the site setup:

Database Connector

Use the following database connector information:

1. Database Name: wordpress
2. Username: admin
3. Password: yourRDSpassword
4. Database Host: yourRDSendpoint
5. Table Prefix: wp_

Site Information

Set the following site information:

1. Site Title: OPS705 Fall 2022 – Assignment 2
2. Username: yourSenecaUsername
3. Password: Choose a strong password (do not reuse the DB password)
4. Your Email: yourSenecaEmailAddress
5. Search engine visibility: Checked

Task 5: Blog Posts

Delete the first template post. In your own words, answer the following questions in individual blog posts:

Blog Post: 1

How would you describe how you set up this Elastic Beanstalk+Database instance of Wordpress to a student who has just finished OPS705 Week 1?

Blog Post: 2

What was the most difficult part of this assignment for you?

Blog Post: 3

What parts of this assignment did you find easier compared to our IaaS version of Wordpress from Assignment 1?

Blog Post: 4

In the context of this assignment, briefly describe the function of the following: VPCs, subnets, security groups, route tables, internet gateways

Lab Submission

As with previous labs, your work will be evaluated by accessing your site directly. To formally submit, you must include the following:

1. In the comment section of your submission, paste the URL of your new site.
2. A single screenshot showing your active and complete Wordpress blog.

Once submitted, you can leave your resources running.