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.'''The purpose of this assignment is to demonstrate your knowledge of Amazon Web Services gathered from our lectures and assigned labs and to show you how you can leverage PaaS to build a web application easily.

# Existing VPC security groups: Remove default VPC, add '''Wordpress Database VPCSG''' (look to see that it's there below the dropdown after you select it)

= Task 3: Wordpress Source Code Modification ='''Explanation:''' From your work with Wordpress in Assignment 1, you know you can simply upload the source code and the first time you load the webpage, you'll be asked for database connector information. However, Elastic Beanstalk applications are meant to be disposable. In A1, when you were adding that database connector info, it was being saved in a file called ''wp-config.php'' on the webserver VM. This is fine for that kind of setup, but in Elastic Beanstalk, changes made to static HTML or PHP ''are not saved if the Beanstalk application restarts'', which it will do often. Whenever the application restarts, it will load from the source zip file. If you did as in A1, you'd have to constantly re-enter your DB connector info every time you started up your Learner Lab environment. We ''could'' add the DB connector info to '''wp-config.php''' manually before we upload the source code, but there's a much better way. We use environment variables to allow us to put all the info in the Elastic Beanstalk application wizard. That way, every time the application restarts and reloads from the source code zip, it'll then read our connector information from AWS. Read below for details and steps. '''Note:''' All other information, like the Wordpress website name, users, theme settings, blog posts, etc., are saved in the actual database you created in RDS. This database does not get reset when the Elastic Beanstalk application restarts, so your actual blog will remain intact. == Download and Unzip - Local Computer ==# On your local machine, download the current Wordpress source code from here: https://wordpress.org/latest.zip# Unzip the file. You should end up with a '''wordpress''' directory. (Do not delete the original .zip file) == Modify Wordpress Configuration File == === Duplicate and Open Configuration File ===# In the local ''wordpress'' folder, find a file called: '''wp-config-sample.php'''# Duplicate this file, and call it: '''wp-config.php'''# Open '''wp-config.php''' in a plain text editor. I recommend Sublime. (https://www.sublimetext.com/download) === Adding Database Connector Info as Environment Variables ===[[Image:Ops705_a2_wp-config-example.png|thumb|right|450px|Figure 1: Adding database connector information to ''wp-config.php''.]]In this file (wp-config.php), you will be adding database connector information as '''environment variables''', not the actual connector information. (We'll add that information later.) Find the following lines and add the bolded values:# define('DB_NAME', '''getenv('DB_NAME'))''';# define('DB_USER', '''getenv('DB_USER'))''';# define('DB_PASSWORD', '''getenv('DB_PASSWORD'))''';# define('DB_HOST', '''getenv('DB_HOST'))'''; === Adding Authentication Unique Keys and Salts as Environment Variables ===In the same file (wp-config.php), you'll be adding the authentication keys and salts as '''environment variables'''. Find the following lines and add the bolded values:# define('AUTH_KEY', '''getenv('AUTH_KEY'))''';# define('SECURE_AUTH_KEY', '''getenv('SECURE_AUTH_KEY'))''';# define('LOGGED_IN_KEY', '''getenv('LOGGED_IN_KEY'))''';# define('NONCE_KEY', '''getenv('NONCE_KEY'))''';# define('AUTH_SALT', '''getenv('AUTH_SALT'))''';# define('SECURE_AUTH_SALT', '''getenv('SECURE_AUTH_SALT'))''';# define('LOGGED_IN_SALT', '''getenv('LOGGED_IN_SALT'))''';# define('NONCE_SALT', '''getenv('NONCE_SALT'))'''; == Zip As New File and Rename - Local Computer ==# Find the '''wordpress''' folder on your local computer.# Zip the ''entire wordpress directory'', not just the files inside. (Use the zip compression protocol. Don't use something else like .rar.)# Rename your new zip file: '''wordpress-6.2-modded.zip''' (Use whatever version the source zip file has.) = Task 4: Elastic Beanstalk =

# Environment name: '''Wordpress-env'''# Domain: ''' ''yourSenecaUsername''-assignment2''' (Click on the ''Check availability'' button to verify the URL is free.)

# Choose file: '''Downloaded wordpress source code -6.2-modded.zip file''' (You can download the wordpress source code here: https://wordpress.org/latest.zipFrom your local computer)# Version label: ''wordpress-versionnumber'' (Example: wordpress-6.1.1)2'''

 === Software ===[[Image:Ops705_a2_beanstalk-environment-variables-example.png|thumb|right|650px|Figure 2: Adding database connector information, auth keys and salts to your Elastic Beanstalk application as static Environment Variables.]]Before beginning this section, you will need two things: # Your database connector information (you saved this, right?)# Randomly generated auth keys and salts from here: https://api.wordpress.org/secret-key/1.1/salt/ (it's a good idea to save these in a text file, too) Settings:# Software > Document root: '''/wordpress'''# Environment properties## DB_HOST: ''your RDS database URL''## DB_NAME: ''initial database name''## DB_USER: '''admin'''## DB_PASSWORD: ''your auto-generated database password''## AUTH_KEY: ''(use gathered info from salt page)''## SECURE_AUTH_KEY: ''(use gathered info from salt page)''## LOGGED_IN_KEY: ''(use gathered info from salt page)''## NONCE_KEY: ''(use gathered info from salt page)''## AUTH_SALT: ''(use gathered info from salt page)''## SECURE_AUTH_SALT: ''(use gathered info from salt page)''## LOGGED_IN_SALT: ''(use gathered info from salt page)''## NONCE_SALT: ''(use gathered info from salt page)''#* ''(Hint: None of these values should have single quotes in them. i.e. ') === Security > ===# Service role: '''LabRole'''# Security > EC2 key pair: '''vockey'''# Security > IAM instance profile: '''LabInstanceProfile''' === Monitoring ===# Monitoring > System: '''Basic'''# === Managed updates > === # Enabled: '''Unchecked''' === Notifications === # NotificationsEmail: ''YourSenecaE-mailAddress'' === Network ===# Network > VPC: '''Wordpress VPC'''# Network > Public IP address: '''Checked'''# Network > Instance subnets: '''Public Subnet 1, Public Subnet 2''' (both checked)# Network > Database subnets: '''Private Subnet 1, Private Subnet 2''' (both checked) === Instances ===# Instances > EC2 Security Groups: '''Wordpress Website SG''' (both checked)# '''Create the application.'''

= Task 45: Site Configuration =

Once submitted, you can leave your resources Elastic Beanstalk application running, but '''shutdown your Learner Lab environment'''.