AWS Week in Review - September 10th to September 16th, 2012

 



Let's take a quick look at what happened in AWS-land last week:

Tuesday, September 11	AWS launched the EC2 Reserved Instance Marketplace.
Wednesday, September 12	AWS  announced that Cluster GPU Instances are now available in the EU West (Ireland) region and inside of VPCs. AWS  opened up a new CloudFront / Route 53 edge location in Madrid, Spain.
Thursday, September 13	AWS  published a tutorial to show you how to manage ASP.Net session state using DynamoDB. AWS  announced that Oracle Data Pump can now be used to import and export data from an Amazon RDS DB Instance. AWS  announced the AWS Global Start-Up Challenge. You can now use RDS for SQL Server inside of a Virtual Private Cloud. AWS  added additional VPN features to the Virtual Private Cloud.

SOURCE

Sign in to and Use the AWS Account

In this guide, lets understand below topics:

• Understand AWS Manament Console
• Different ways of logging into the AWS Management Console.
• Sign into the AWS Management Console using the Account level credentials
• Configure AWS Management Console as per your suitability.

AWS Management Console simple definition by AWS :

Access and manage Amazon’s growing suite of infrastructure web services through a simple and intuitive, web-based user interface. The AWS Management Console provides convenient management of your compute, storage, and other cloud resources.

AWS constantly keeps pushing new features and support for various services in the console. If any feature is not available throught the AWS Management Console, the user must employ the APIs and/or SDKs provided by AWS.

In AWS, there are basically two different ways for a user to sign in to the AWS Management Console for handling the services:

• Using the Account level credentials

Consider this as a "POWER USER LOGIN" (this is a term coined by me to set perspective and not by AWS)

A user can sign in using the typical AWS Console login URL. The user must use email-address using which the account is created and password provided.

This way of sign in allows the user complete control over the AWS services, resources and  account management.

In this guide we will be concentrating more on Account-level login to the AWS Management Console.  

• Amazon Indentity and Access Management (IAM) User

Consider this as a "ACCESS CONTROLLED USERs"(this is a term coined by me to set perspective and not by AWS)

In case there is need of more than 1 user to login to the AWS account, you can use the IAM Service. Each user may have same or different access controls over the various AWS services and resources. The users can sign into the console using a different alias, specific to your account and using specific user login name & password. These privilieges are not only applicable to the AWS Management Console. The same can be applied to the use of SDKs and APIs. This can be achieved by creating user specific Access Keys and Secret Keys.

IAM also enables identity federation between your corporate directory and AWS services.

I'm NOT covering IAM user login in this tutorial, but I will surely write a guide on the topic and provide updated links.

Sign into the AWS Management Console using the Account level credentials :

Amazon VPC - New Additions

 

AWS has added 3 new features / options to the  Amazon Virtual Private Cloud (VPC) service.

 

• Create Hardware VPN connections to your VPC using static routing.
• Configure automatic propagation of routes from your VPN and Direct Connect links (gateways) to your VPC's routing tables
• Launch RDS database instances running Microsoft SQL Server inside of a Virtual Private Cloud (VPC).

 

PFB extract for the two blogs written by Jeff on the same:

 

Amazon VPC - Additional VPN Features

 

The Amazon Virtual Private Cloud (VPC) gives you the power to create a private, isolated section of the AWS Cloud. You have full control of network addressing. Each of your VPCs can include subnets (with access control lists), route tables, and gateways to your existing network and to the Internet.

 

You can connect your VPC to the Internet via an Internet Gateway and enjoy all the flexibility of Amazon EC2 with the added benefits of Amazon VPC. You can also setup an IPsec VPN connection to your VPC, extending your corporate data center into the AWS Cloud. Today we are adding two options to give you additional VPN connection flexibility:

1. You can now create Hardware VPN connections to your VPC using static routing. This means that you can establish connectivity using VPN devices that do not support BGP such as Cisco ASA and Microsoft Windows Server 2008 R2. You can also use Linux to establish a Hardware VPN connection to your VPC. In fact, any IPSec VPN implementation should work.
2. You can now configure automatic propagation of routes from your VPN and Direct Connect links (gateways) to your VPC's routing tables. This will make your life easier as you won’t need to create static route entries in your VPC route table for your VPN connections. For instance, if you’re using dynamically routed (BGP) VPN connections, your BGP route advertisements from your home network can be automatically propagated into your VPC routing table.

If your VPN hardware is capable of supporting BGP, this is still the preferred way to go as BGP performs a robust liveness check on the IPSec tunnel. Each VPN connection uses two tunnels for redundancy; BGP simplifies the failover procedure that is invoked when one VPN tunnel goes down.

Cancel an AWS Account

AWS allows users to cancel their AWS account.

If you wish to cancel your AWS account follow the below steps:

• Login to your AWS Account as a returning user by selecting the option : "I am a returning user and password is:" , click on Sign in using our secure server button.