1,576
edits
Changes
no edit summary
# Followed the e-mail instructions in your AWS Academy invite, found in your Seneca inbox
= INVESTIGATION 1: Managing a Windows Server 2019 VM in AWS Academy Amazon Web Services =In this investigation, you'll create, configure, and manage a Windows Server 2019 Virtual Machine using log in to Amazon Web Services ' Educate classroom and familiarize yourself with the interface. We'll be using AWS for the majority of our work in this course. == Part 1: Completing Your AWS Academy Registration ==# Follow the e-mail instructions in your AWS Academy invite, found in your Seneca inbox.# Check your spam filter before asking for a presecond invitation e-built imagemail. Compare # '''Warning:''' Do not create your own student account manually! Doing so can interfere with the AWS Academy account and contrast this experience with your setup of a Windows Server VM in Azure from Lab 2cause login issues. Use the e-mail invitation link for registration.
== Part 12: Logging In to AWS Academy ==
[[Image:Ops705_lab5_fig1.png|thumb|right|500px|Figure 1. AWS Academy Lab Environment.]]
This section assumes you've followed the directions in your AWS Academy invitation e-mail and have successfully logged in to your account. Check your spam filter before asking for a second invitation e-mail.
# A new browser window will launch automatically. This is the '''AWS Management Console''' where you will do most of your work. From this point on, your experience will closely match a normal production account.
= INVESTIGATION 2: Managing a Windows Server 2019 VM in AWS Academy =In this investigation, you'll create, configure, and manage a Windows Server 2019 Virtual Machine using Amazon Web Services and a pre-built image. Compare and contrast this experience with your setup of a Windows Server VM in Azure from Lab 2. == Part 21: Creating a Windows Server 2019 VM with EC2 ==
[[Image:Ops705_lab5_fig2.png|thumb|right|500px|Figure 2. Default AWS Management Console view.]]
We will now create a virtual machine in AWS using the EC2 service.
# Click on the new entry to view the VM instance. This will display information about the VM, as well as its current state.
== Part 32: Remotely Connecting to your Windows Server VM in AWS ==
# From the Instance details page of your new VM in AWS, click on the '''Connect''' button near the top-right of your browser window.
# Don't be alarmed by the red warning!
# Once connected, open Notepad, and write <code>My name is ''insertFullName'', and I've completed the AWS Windows Server VM investigation!</code> Save the file to your VM's desktop, with the filename ''yourSenecaUsernameAWS.txt''.
== Part 43: Managing your VM from the AWS UI ==
# Go back into the Instance details page for your new VM.
# As noted earlier, this screen contains details about the VM along with its current status.
# At this point, power down your VM. Either do so from within your RDP connection, or click the '''Stop instance''' option in the AWS ''Instance state'' drop-down menu.
== Part 54: A Note About Resource Usage ==
As with our work in Microsoft Azure, keeping out costs down is important. When you aren't using a resource (like a VM), make sure it's in a stopped state.
You've been allocated $100 in AWS credits for the course, and that should be more than enough for the remaining labs. Please be responsible with your usage!
= INVESTIGATION 23: Managing a Linux VM in AWS EC2 =
In this investigation, we'll create, configure, and manage a Red Hat Enterprise Linux Virtual Machine using Amazon Web Services. This version of the OS is command line only, so you'll be using SSH to remotely connect to the VM and issue basic commands. This VM will be used extensively in Lab 3.
