The command-line tools are provided by the Amazon staff and are located at:

http://aws.amazon.com/developertools/351

set JAVA_HOME="C:\Program Files\Java\jre6"
set EC2_PRIVATE_KEY=c:\aws\pk-XUSF3YX32DTZWSBHEIENR24EANXCXUBA.pem
set EC2_CERT=c:\aws\cert-XUSF3YX32DTZWSBHEIENR24EANXCXUBA.pem
set EC2_HOME=C:\AWS\ec2-api-tools\ec2-api-tools-1.3-62308
set PATH=%PATH%;C:\AWS\ec2-api-tools\ec2-api-tools-1.3-62308\bin

Commands used in the book:

These are the commands used in this book:

Command	Description	Chapter
ec2-describe-regions	List all of the current regions available	Chapter 3, Getting Started with AWS and Amazon EC2
ec2-describe-images –o self	List all of the AMIs owned by the AWS user	Chapter 3, Getting Started with AWS and Amazon EC2
ec2-run-instances ami-70b24319 -g migrate_to_aws_secure -k migrate_to_aws_key_pair --availability-zone us-east-1a –monitor	Start up an EC2 instance using AMI ami-70b24319 in the migrate_to_aws security group using the migrate_to_aws_key_pair key pair in the us-east-1a availability zone	Chapter 3, Getting Started with AWS and Amazon EC2
ec2-create-tags i-cc9b92a1 --tag "Name=DB01"	Associate a tag with a running instance	Chapter 3, Getting Started with AWS and Amazon EC2
ec2-describe-instances --filter "instance-state-name=running"	Get a list of running instances	Chapter 3, Getting Started with AWS and Amazon EC2
ec2-terminate-instances i-cc9b92a1	Terminate a running instance	Chapter 3, Getting Started with AWS and Amazon EC2
ec2-stop-instances i-cc9b92a1	Stop a running instance	Chapter 3, Getting Started with AWS and Amazon EC2

The following figure shows the AWS console location for EC2:

The following is a summary of the costs and types of instances:

S3 tools on Codeplex provided by third party.

Alternative tools provided at s3tools.org are located at:

http://s3.codeplex.com

To set up this tool use the following command:

s3 auth <Access Key> <Secret Access Key>

Commands used in the book

The following are the commands used throughout this book.

Command	Description	Chapter
s3 auth AKIAIIJXIP5XC6NW3KTQ 9UpktBlqDroY5C4Q7OnlF1pNX tK332TslYFsWy9R	Set up credentials	Chapter 4, How Storage Works on Amazon
s3 list	List S3 buckets	Chapter 4, How Storage Works on Amazon
s3 put migrate_to_aws_02 myfile.txt	Upload a file to S3	Chapter 4, How Storage Works on Amazon
s3 put migrate_to_aws_02/mybigfile/ mybigfile.txt /big	Upload in chunks a large file to S3	Chapter 4, How Storage Works on Amazon
s3 get migrate_to_aws_02/myfile.txt	Download a file from S3	Chapter 4, How Storage Works on Amazon
s3 get migrate_to_aws_02/mybigfile/mybigfile.txt /big	Download in chunks a big file from S3	Chapter 4, How Storage Works on Amazon

The following screenshot shows the AWS console location for S3:

Storage for S3 costs approximately as follows:

For one (1) terabyte of storage for one year = $1,720

Command-line tools are provided by the EC2 command-line tools package.

ec2-create-volume  --size 20 --availability-zone us-east-1a

ec2-attach-volume vol-b418c2dc -i i-e2fdea8f -d xvdg

ec2-detach-volume vol-b418c2dc

ec2-delete-volume vol-b418c2dc

Windows: xvdf through to xvdp

Unix: /dev/sdf through to /dev/sdp

The following screenshot shows the AWS console location for EBS:

Storage for EBS costs approximately as follows:

For one (1) terabyte of storage for one year = $1,228

Autoscaling command-line tools are provided by Amazon staff.

The Autoscaling tools are located at:

http://aws.amazon.com/developertools/2535

The environment variables used for the autoscaling tools are:

set AWS_AUTO_SCALING_HOME=C:\AWS\AutoScaling-1.0.33.1
set PATH=C:\AWS\AutoScaling-1.0.33.1\bin;%PATH%

as-describe-launch-configs

as-create-launch-config WebLaunchConfig --image-id ami-7cb54915 --instance-type m1.large –group "Web Servers"

as-create-auto-scaling-group WebAutoScaleGroup --launch-configuration WebLaunchConfig --availability-zones us-east-1a --min-size 2 --max-size 4 –load-balancers my-load-balancer

as-put-scaling-policy WebScaleUp --type ChangeInCapacity --adjustment 1 --cooldown 120 --auto-scaling-group WebAutoScaleGroup

as-put-scaling-policy WebScaleDown --type ChangeInCapacity "--adjustment=-1" --cooldown 120 --auto-scaling-group WebAutoScaleGroup

as-describe-auto-scaling-groups --headers

Amazon Autoscaling carries no additional fees for its use other than standard fees associated with EC2 instances, storage, and bandwidth.

The calculation for costs is complex and based on HTTP requests as well as the size of data transferred. However, as a rough guide:

One (1) TB of data transferred each month for the period of one year in the US region = $1,843.

http://aws.amazon.com/code/1137

Development libraries are located at:

There is no console access to Amazon SimpleDB.

It is complex to approximate the cost for SimpleDB, however, as a rough guide:

One (1) TB of data stored in SimpleDB for a year will cost = $3,077.

If all of the data was transferred out in one year, data transfer cost = $1,843.

The command-line tools are provided by Amazon staff and are located at:

http://aws.amazon.com/developertools/2928

This is the only environment variable used:

Set AWS_RDS_HOME

The following screenshot shows the AWS console location for RDS:

Summary of instance types and costs:

The command-line tools are provided by Amazon staff.

The scratchpad is located at:

http://aws.amazon.com/code/1254

The .Net SDK is located at:

http://aws.amazon.com/sdkfornet/

There is no console access to Amazon SQS.

Pricing is $0.01 per 10,000 requests.

Amazon does not currently supply command-line tools for SNS.

The following screenshot shows the AWS console location for SNS:

Pricing for one (1) TB of data transferred in/out of SNS every month over a twelve month period = $1,843

The command-line tools are provided by Amazon staff.

The CloudWatch tools are located at:

http://aws.amazon.com/developertools/2534

The Cloudwatch environment variables used are:

set AWS_CLOUDWATCH_HOME=C:\AWS\CloudWatch-1.0.9.5
set PATH=C:\AWS\CloudWatch-1.0.9.5\bin;%PATH%

Commands used in the book:

The following are the commands for CloudWatch used throughout this book.

Command	Description	Chapter
mon-describe-alarms	Describe configured alarms	Chapter 9, Monitoring and Scaling My Application
mon-put-metric-alarm WebHighCPUAlarm --comparison-operator GreaterThanThreshold --evaluation-periods 1 --metric-name CPUUtilization --namespace "AWS/EC2" --period 120 --statistic Average --threshold 80 --alarm-actions arn:aws:autoscaling:us-east-1:764516644405:scalingPolicy:d3c53ac8-fa73-4cfd-9a06-a5f9d7e1a58f: autoScalingGroupName/WebAutoScaleGroup:policyName/WebScaleUp --dimensions "AutoScalingGroupName=WebAutoScaleGroup"	Create the cloud watch metric	Chapter 9, Monitoring and Scaling My Application

The following screenshot shows the AWS console location for CloudWatch:

Pricing for monitoring one instance is $3.50/month.

Command-line tools are provided by the EC2 command-line tools package.

The following screenshot shows the AWS console location for VPC:

Pricing for one VPC connection over a one year period is = $438.

Command-line tools are provided by the EC2 command-line tools package.

The following screenshot shows the AWS console location for ELB:

Pricing for one load balancer over a one year period if one (1) TB of data is transferred is = $317

The command-line tools are provided by Amazon staff and are located at:

http://awsimportexport.s3.amazonaws.com/importexport-webservice-tool.zip

java -jar lib/AWSImportExportWebServiceTool-1.0.jar CreateJob Import MyManifest.txt

java -jar lib/AWSImportExportWebServiceTool-1.0.jar ListJobs

java -jar lib/AWSImportExportWebServiceTool-1.0.jar CancelJob XHNHC

Around $80 per device