AWS Lab Notes
AWS Lab Notes
Contents
Table of Contents ......................................................................................................................................................1
About the Lab ............................................................................................................................................................3
Checking your AWS Usage and Monthly Bill .......................................................................................................4
Creating an S3 Bucket and Uploading Files .........................................................................................................6
Uploading Files to your Bucket .............................................................................................................................7
Downloading files from your bucket ....................................................................................................................9
Troubleshooting..................................................................................................................................................10
Clean Up..............................................................................................................................................................10
Creating a SQL Database with RDS ....................................................................................................................13
Creating a Security Group...................................................................................................................................13
Creating an RDS Database ..................................................................................................................................16
Connecting to your RDS Instance .......................................................................................................................22
Troubleshooting Connection Issues ...................................................................................................................27
Clean Up..............................................................................................................................................................29
Creating a Web Server with EC2..........................................................................................................................32
Viewing your web server ....................................................................................................................................39
Troubleshooting viewing your WordPress application ......................................................................................40
Finding the Username and Password for your WordPress application ..............................................................42
Troubleshooting logging in to the WordPress application .................................................................................44
Clean up ..............................................................................................................................................................45
Sending Emails with Amazon SES ......................................................................................................................47
Requesting full access to SES ..............................................................................................................................49
Creating a Billing Alert with CloudWatch and SNS............................................................................................50
Enabling Billing Alerts .........................................................................................................................................50
Creating a CloudWatch Alarm ............................................................................................................................51
Creating an IAM User .............................................................................................................................................59
Creating a Highly Available Architecture with Elastic Beanstalk .....................................................................62
Clean Up..............................................................................................................................................................65
About the Lab
Please note that not all AWS services are supported in all regions. Please use
the US-East-1 (North Virginia) region for this lab.
These lab notes are to support the hands on instructional videos of the Introduction to AWS section of the
BackSpace AWS Cloud Practitioner Course.
Please note that AWS services change on a weekly basis and it is extremely important
you check the version number on this document to ensure you have the latest version
with any updates or corrections.
Checking your AWS Usage and
Monthly Bill
Creating an S3 Bucket and
Uploading Files
Uploading Files to your Bucket
Downloading files from your bucket
If you get the following screen it means you have clicked on the S3 URL and not the download link as detailed
above. You cannot access files directly from a URL as they have private access.
Clean Up
We will now delete the files and bucket so that you will not be billed by AWS.
Click Empty
Click Empty
Click Exit
Click Delete
By default, inbound access from the Internet to our database instance is blocked. We will create a security group
that defines an inbound rule that allows access from the Internet. We can then associate this security group to
our database instance.
Give it a description
https://dev.mysql.com/doc/workbench/en/wb-installing-windows.html
https://dev.mysql.com/doc/workbench/en/wb-installing-mac.html
https://dev.mysql.com/doc/workbench/en/wb-installing-linux.html
Troubleshooting Connection Issues
The username and password must be the one created when the RDS instance was created.
This error means nothing exists at the endpoint. Check the connection endpoint and port are correct.
The hostname will be the RDS Instance Connection Endpoint without :3306 on the end.
No Connection
This error means your server exists but you are unable to connect to it. This can be caused by:
- You have not selected ‘public’ when creating instance and the security group inbound rules will be
incorrect. This will block traffic to your instance. See Security Group Inbound Rules below.
- You have a dynamic IP address or multiple IP addresses passing through a load balancer. See Security
Group Inbound Rules below.
- Firewall at your end is blocking access to port 3306. See Client-side Firewall below.
If you did not as detailed, your security group will block remote access.
The security group may have an inbound rule for your IP address. If you are using a dynamic IP address or you are
connecting from different networks then this will need to be changed to “anywhere” for the lab.
Client-side Firewall
If you are still having problems connecting, a firewall at your end may be preventing access on port 3306. This is
common if you are connecting from your work environment as port 3306 traffic may be blocked.
Clean Up
Creating a Web Server with EC2
Click EC2
Click Continue (This lab will be covered under the AWS free tier for accounts less than 12 months old)
Choose the t2 micro instance.
Select “I acknowledge that I will not be able to connect to this instance unless I already know the password built
into this AMI.”
When the launch process has started scroll to the bottom of the page and click “View Instances”
After a few minutes, the status of the instance will change to running and status checks will be completed (you
will need to refresh the screen to see any changes).
Viewing your web server
After the Status checks have completed click on the Instance ID to select the instance.
Copy the public IP address of your web server (don’t click on open address).
If you cannot view your website it probably hasn’t finished the launch process completely.
If you navigate to your website and it displays a security message, you have tried to open with https not http.
If after quite some time you still can’t view your website, it may be that your security group does not allow
inbound requests on port 80 (http). The inbound rules should include:
80 tcp 0.0.0.0/0
Click on Edit
Add a rule for HTTP and Anywhere
Go back to the EC2 console and select “Monitor and troubleshoot”, “Get System Log”. Do not click on connect.
Scroll up until you find the log entry for the application username and password and copy it.
Clean up
Make sure you terminate the instance so that you are not billed for it anymore.
Sending Emails with Amazon SES
When you receive your verification email click on the supplied link.