Changes

= INVESTIGATION 1: Installing Wordpress AWS Elastic Beanstalk =In this investigation, you'll set up a Wordpress installation using two AWS Elastic Beanstalkinstances. This service takes care of all the infrastructure setup; all you need to worry about is the code platform, and the code, and the database setup.

== Part 1: Creating a Wordpress Web App Logging in to AWS Academy - Cloud Foundations ==

# Log in to AWS Academy and navigate to the AWS Management Console.# Search for ''Elastic Beanstalk'' and click.# On the main page for Elastic Beanstalk, click on the big orange '''Create Application''' button.# You are now in the ''Getting Started - Create a web app'' screen.# For the application name, name it ''wordpress''.# Under ''Platform'', select '''PHP'''. Leave the branch and version on their defaults.# Under ''Application Code'', select '''Upload your code'''.# Open a new browser tab, navigate to here: https://wordpress.org/download and download the latest .zip package.# Back in the ''Getting Started - Create a web app'' screen, go to the ''Source code origin'' section.# For the version label, use the '''current name''' of the zip file. For example: '''wordpress-5.6awsacademy.2''' or '''wordpress-5instructure.7'''# Select '''Local file''.# Click on ''Choose file''. A local filesystem navigation window pops up. Select the wordpress .zip file you downloaded in Step 8.# At the bottom of the screen, click on the white ''Configure more options'' button.# In the next screen, find the ''Software'' box and click the ''Edit'' button inside.# In this new screen, scroll all the way to the top. In the ''Container Options'', in the ''Document root'' field, type: <code>com/wordpress<login/code>canvas# Click on the ''Save'' button at the bottom of the screen to apply and to go back to the 'Under 'Configure more options'' page.# Scroll down to the Courses''Database'' box, and click choose ''Edit'AWS Academy Cloud Foundations'.# In the database options page, enter your username as '''admin'''. Choose a '''complex and unique password''', and save that password in a file. It will appear in the clear occasionally, so make sure it's not reused from something else.# If not already present, enter '''5''' in the ''Storage'' field.# Keep all other defaults.# Click ''Save'' at the bottom of the page.# Back in the main page, find the ''Notifications'' box and click ''Edit'' to add your Seneca e-mail address.# Back in the main page, click on the ''Create app'' button at the bottom of the page.# Your new Wordpress application will now be created. This takes about 10 minutes. The log screen will update it's progress as it goes and let you know when it's complete.

== Part 2: Configuring the Wordpress Installation Module 6 Activity - AWS Elastic Beanstalk ==# Once the web app has completed start up from Part 1, click on the 'Navigate to 'Environments'Modules' link.# You'll have a single environment in the list, most likely named ''Wordpress-env''. Click the name.# Here, you can see the basic status of the web app and associated information. You can also update the code running here if you'd like.# In the left-hand menu, click on ''Configuration''bar.# Near the bottom of this page, you'll see a section labelled ''Database''. Next Scroll down to the ''endpointModule 6 - Compute'' field, a link will be present. # Save this link in a text document, and then open this link in a new window.# Welcome to the MySQL database you created with the web app. We're here to grab database connector information.# Click on the ''ConfigurationActivity - AWS Elastic Beanstalk'' tab link# Follow the lab instructions.# At While you complete the very toplab, look for take the ''DB name'' entry. Write this down in your text file.following screenshots:# Your text document should now have four pieces # First view of information: Database Host (endpoint), Database Name, Database Username, and Database Password# Go back to your first window, the ''Wordpresspre-env'' created sample Elastic Beanstalk environment status page. In the left-hand menu, click on the ''Go to environment'' link.# This brings you to the Wordpress configuration webpage for your personal installation.# Select ''English (United States)'', and then the blue ''Continue'' button.# This The HTTP 404 Tomcat error page just reminds you to have the information from Step 10 handy. (Don't worry about ''Table prefix'', we'll be using clicking on the default.) Click ''Let's go!''.# In URL for the next page, enter the database information from your text file. Leave ''Table Prefix'' at its defaulthosted resource.# When ready, click ''Submit''.# If View of your connector information is correct, you'll get a congratulations environment status page. ("All right, sparky!"). Click ''Run with the installation''. If you got an error page, go back and double-check your informationupdated code deployed.# Now, we're in the blog settings # The Congratulations web page. Use from clicking on the following settings:# '''Site Title''': <code>Full Name's OPS705 Blog</code># '''Username''': <code>Seneca Username</code># '''Password''': Use URL for the supplied password, or choose hosted resource using your own.# '''Your Email''': <new code>username@myseneca.ca</code># '''Search engine visibility''': Check the box.# When ready, click A listing of your EC2 instances running the ''Install Wordpress'' button.# Shortly, above resources to show you'll see a ''Success!'' splash page confirming your username. Click ve fully explored the ''Log In'' button to login to your new bloglab.

= INVESTIGATION 2: Working with Wordpress =In this investigation, you'll interact with the Wordpress blog itself, and create a new post. == Part 13: Writing a Blog Entry A Note About Resource Usage ==# Look around at the Dashboard and familiarize yourself with the available settings.# Create a blog post with the title <code>Post 1: Installing Wordpress Using AWS Elastic Beanstalk</code>Module labs only need to be ended to shut down all resources.# In the post itselfRemember, using your own words, describe your opinion of the installation process and how it compares to other created work youis 've done in this course (or outside this course). Write approximately 500 words. Grammar and spelling are unimportant, as long as I can understand what you're getting at. == Part 2: Research Blog Entry ==# Create a second post describing, in your own words, the differences between the AWS Elastic Beanstalk web application you've installed, and a traditional not''LAMP'' stack. Compare and contrast preserved after you end the two. This will require a little research on your part, but will increase your understanding of PaaS overall. Bonus marks will be given for exceptionally good explanations at my discretion (everyone loves a good visual diagramlab!).

== Part 34: A Note About Resource Usage Exploration ==Web apps are a bit different when it comes A second AWS Academy classroom is available to resource usageyou, '''AWS Academy Learner Lab - Foundation Services''. They're essentially always onHere, you can explore the Elastic Beanstalk service (along with many others), and meant to be create instances that way. This is where auto-scaling becomes importantwill remain for the duration of the class, but that's and try things out of scope . I highly encourage you to take a look and play around! Read through the sidebar readme doc for this lab. For now, leaving your new blog running is expectedservice restrictions.

# The First view of your pre-created sample Elastic Beanstalk Environment environment status page for ''Wordpress-env''.# The Wordpress DashboardHTTP 404 Tomcat error page from clicking on the URL for the hosted resource.# Your first blog postView of your environment status page with the updated code deployed.# Your second blog post. '''In The Congratulations web page from clicking on the ''Comments'' text box URL for your submission on Blackboard, include the URL to each of hosted resource using your blog postsnew code.''' Your professor will review # A listing of your blog directly; EC2 instances running the above resources to show you've fully explored the screenshots are a backup in case of catastrophic issueslab.