As part of some internal testing @ VMware I was asked to setup an account in AWS aka Amazon Web Services.
Now I had heard a lot about AWS and also studied them extensively as part of my Masters degree so I decided to see what all the hype was about.
Step 1: Create an account on AWS:
Before you can access AWS, you need to create your AWS account by signing up here. AWS provides a “Free Tier” which is perfect for exploring all of their services so as long as you are careful you can run workloads in AWS without incurring any cost.
As part of the verification process, you have to provide a credit or debit card along with a phone number where you will receive a call from an automated service and then key in the PIN shown on the registration screen.
The credit / debit card is only charged if you you happen to go over the limits of the “Free” tier of services.
At a glance the “Free” Tier contains the following:
- Amazon S3 (Storage & Content Delivery) – 5GB
- Amazon RDS (Database) – 750 hours per month
- Amazon EC2 (Compute) – 750 hours per month
This should be more than enough to get started using AWS.
Full list of services available on the “Free Tier” page
Step 2: Create an EC2 Instance
To get started with AWS, lets create and deploy an EC2 instance running Windows Server 2012 R2.
Select Launch a virtual machine from the Build a solution section
Click on the Get Started button to start the EC2 Instance configuration process
Give your EC2 instance a name – for this example I have chosen “aws02”
Select your operating system for your EC2 instance – we choose Windows Server 2012 R2
Select your instance type – for the Free Tier we use the t2 micro instance
Create the key pair which is used to secure the EC2 instance, you download the private key to your computer
Check all details and then click on Confirm this instance button
Once you confirm the configuration the EC2 instance is launched.
In the EC2 Management Console we can see our instance – aws02 is running.
Once we click on Launch Instance we need to choose an Amazon Machine Image (AMI) which is a pre-configured template containing the complete software configuration (OS, applications server, applications etc).
For this example I choose Windows Server 2016 Beta but the end result was Windows Server 2012 R2. This could be a bug with AWS.
Again choose the instance type – for this we will select t2 micro again.
Review Instance Launch details and then click on Launch which assigns a key pair to the instance and completes the launch process
Select the existing key pair for aws02
When you navigate back to the EC2 Management Console you will see the Instance being created is in Pending state
Right click on the newly created instance (contains the Windows OS) and select
Get Windows Password
Locate the Private Key that you saved previously in order to decrypt the password
If the correct Private Key is provided the password is decrypted and displayed on screen
Step 3: Connect to RDP session of EC2 Instance running Windows Server 2012 R2
More info on AWS and all its offerings is available here.
I was a bit apprehensive about providing Credit Card information for a service advertised as “Free” but the onus is on the user to watch their usage and act accordingly.
I found the process of creating a VM running a Windows OS quite straightforward although I was a bit confused about having to create 2 instances but if you think like a VI Admin, the 1st instance is your Bare Metal Hypervisor and the 2nd instance is your VM running the OS. AWS could prevent name duplication in my opinion so it is easy to distinguish between the 2 instances.
Overall I think the “Free Tier” of AWS is a good way to “get your hands dirty” with Amazon’s extensive cloud offerings and to run small workloads. It is important to remember you are restricted and therefore cannot be too ambitious else you will find that your Credit Card is a bit lighter due to the auto charging.
Leave a Reply