AWS Academy Instructions
Getting Started with AWS Academy
- Open email from AWS Academy to accept invite to course.
- Email your course instructor if you did not receive an email.
- You will be joined to a Canvas course called AWS Academy Learner Lab - Foundation Services
- If you are in multiple courses using AWS, you may need to get used to the “Dashboard” to spend funds in the correct course.
- Within the course, click Modules
- Click Learner Lab
- Read and Agree to the Terms and Conditions
- Click the Start Lab Play button on the middle right
- Wait. 2 - 3 minutes. You will see a console appear that you can interact with.
- This terminal is configured with AWS CLI access - you can query resources created on your account with it, but in itself is not what we are aiming for. Proceed with next instructions.
- Click AWS Details (with info icon next to it). Click download PEM from the SSH key options
- You’ll need this for Connecting to the AWS Instance in the sections below, after completing the remainder of these steps
- Click AWS which should have a green dot next to it located on the left
- This will take you to your AWS Console for your account. Now the fun begins.
-
In a new tab, enter the following URL in the browser (or click link to open): https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=ceg2350&templateURL=https:%2F%2Fwsu-cecs-cf-templates.s3.us-east-2.amazonaws.com%2Fcourse-templates%2Fceg2350.yml
- On the first menu, click Next
- On the second menu, under Parameters, under Key Name, select
vockey
- Click Next
- On the third menu, select Next
- Scroll to the bottom and select Submit
- You will be redirected to a status page that says CREATE_IN_PROGRESS
- Refresh this page until CREATE_COMPLETE is the status
- Once you have created the AWS Cloud formation stack you can return to the EC2 menu.
Here you should see additional resources have been created (not everything says 0 anymore)
- Click on Running Instances
- Our instance should now be created (or almost ready). Select the checkbox next to the instance name “CEG 2350” to see all details about this instance.
- Your instance will be assigned a unique Elastic / Public IP address. This IP address is what we will use to SSH to the instance.
You are now ready to make an SSH connection to your AWS server.
View the Connection instructions below appropriate to the system you are using to create a connection - the client system.
WARNING
While exploring and discovery is an important part of this course, any additional resources you create in AWS have an associated charge. If resources besides those strictly asked for by this course stay running, you risk running out of funds for this course. This will hinder your ability to complete assignments on time.
Connecting to an AWS Instance from Linux / Unix / Mac / WSL2
- Open your Terminal program.
-
Copy or navigate to the AWS SSH key that was downloaded to your system to your home directory in your terminal
- Helpful commands:
cd, cp, ls, man
- If using copy / paste method:
- Create a file with a useful name (or the same name as the downloaded file)
ceg3120-aws-vm.pem
- Open a text editor (
vim or nano)
- Copy and paste the contents of the key that was downloaded / viewed from AWS Details into the file.
-
Change the permissions on the key file in your directory
- Because private keys need to be protected, the key needs to be changed to readable by your user by using
chmod
chmod 600 /path/to/private/key - replace /path/to/private/key with your information
- Resource on how to use chmod
- SSH into your AWS server with the following command
ssh -i /path/to/private/keyfile ubuntu@ElasticIP
Note: replace /path/to/private/keyfile and ElasticIP with your information
- If your connection was refused, you may have forgotten to put the username
ubuntu in front of your Elastic IP address
- You are now signed in to your AWS instance as the user
ubuntu
Connecting to an AWS Instance from Windows with PowerShell
You are now ready to make an SSH connection to your AWS server.
- Open PowerShell.
-
Navigate to the AWS SSH key that was downloaded to your system.
- Helpful commands:
cd, ls
- If using copy / paste method:
- Create a file with a useful name (or the same name as the downloaded file)
ceg3120-aws-vm.pem
- Open a text editor (
notepad.exe or code)
- Copy and paste the contents of the key that was downloaded / viewed from AWS Details into the file.
- Make sure to enter a new line character at the end of the file.
-
By default, Windows sets permissions of newly created files as your user in your user’s folder to be accessible only by you.
- SSH into your AWS server with the following command
ssh -i C:/path/to/your/keyfile ubuntu@ElasticIP
Note: replace C:/path/to/your/keyfile and ElasticIP with your information
- If your connection was refused, you may have forgotten to put the username
ubuntu in front of your Elastic IP address
- You are now signed in to your AWS instance as the user
ubuntu
Reconnecting to Your AWS environment
Every 4 hours, instances (virtual machines) on AWS will automatically power down. This is good - it saves funds and use of resources. However, every 4 hours you need to restart the timer OR Start Lab again.
- Log on to the AWS Canvas portal
- Within the course, click Modules
- Click Learner Lab - Foundational Services
- Click the Start Lab Play button on the middle right
- Wait. 2 - 3 minutes. You will see a console appear that you can interact with.
- Click AWS which should have a green dot next to it located on the left
- This will take you to your AWS Console for your account.
- The light next to AWS should now be green
- Be patient, but you should now be able to
ssh in to your instance with your private key to the same IP as before
Building a New Instance
Lost your private key? Following internet advice to try rm -rf /*? You may need to start over with a new instance.
Make sure you are logged in to AWS Academy and have clicked “Start Lab” in the Learner Lab Modules page, then repeat Steps 7 and onward in the Getting Started with AWS Academy section
Notes & Troubleshooting
- Sessions last 4 hours. Session time can be refreshed. Instances spin down after 4 hours
- Budget cannot exceed $50 - account will vaporize - all resources created by account will be deleted
Connection Refused

- Enable Third Party Cookies
- Check browser support
- Good browsers: Chrome, Firefox
- Poor browsers: Safari