Running Ubuntu on Amazon EC2 in Sydney, Australia
It is time to expand the AWS footprint once again, with a new Region in Sydney, Australia. AWS customers in Australia can now enjoy fast, low-latency access to the suite of AWS infrastructure services.” Read More
The official Ubuntu AMI lookup pages (1, 2) are showing the new location, and the official Ubuntu AMI query API seems to be working, so the new ap-southeast-2 Ubuntu AMIs are available for lookup on Alestic.com.
Point and Click
At the top right of most pages on Alestic.com is an “Ubuntu AMIs” section. Simply select the EC2 region from the pulldown (say “ap-southeast-2” for Sydney, Australia) and you will see a list of the official 64-bit Ubuntu AMI ids for the various active Ubuntu releases.
Both EBS boot and instance-store AMI ids are listed, but I recommend you start with EBS boot AMIs.
To launch a listed Ubuntu AMI, simply click on the orange arrow to the right of the AMI id and you will be taken to the EC2 section of the AWS console with the AMI id selected:
The AWS console walks you through setting up required ssh keys and security groups and even has a point and click way to ssh to your instance, provided you have Java in your browser (I disable that).
[Newvem continuously analyzes the status of your instances and identifies unhealthy and over loaded instances that may not perform properly or increase outage and recovery vulnerabilities. Learn More]
You can also launch Ubuntu AMIs with the EC2 command line tools. First, make sure you upload your ssh key to the new Sydney, Australia EC2 region using something like:
ec2-import-keypair --region ap-southeast-2 --public-key-file $HOME/.ssh/id_rsa.pub $USER
If you haven’t already, open the ssh port on your default security group:
ec2-authorize --region ap-southeast-2 default -p 22
Then, to launch Ubuntu 12.04 LTS Precise EBS boot, you would use a command like:
ec2-run-instances --region ap-southeast-2 --key $USER --instance-type t1.micro ami-fb8611c1
where you should always look up and use the most recent AMI id. Make a note of the instance id.
Wait a few seconds for the instance to be assigned an IP address and to start booting, then find out what the IP address was with:
ec2-describe-instances --region ap-southeast-2 <INSTANCEID>
If you ran the instance with your uploaded personal ssh key, you can then access the Ubuntu server using
ssh [email protected]<IPADDRESS>
where is the public IP address of the instance (does not start with “10.”).
Always remember to terminate your temporary EC2 instances when you are done with them so you don’t keep paying charges:
ec2-terminate-instances --region ap-southeast-2 <INSTANCEID>
Note: The official Ubuntu AMI ids listed on Alestic.com are created, published, and supported by Canonical, an official sponsor of Ubuntu. (Alestic.com/Eric Hammond used to publish community Ubuntu AMIs for EC2 starting in 2007, but that fun job was transferred to Canonical back in 2009.)
[Newvem analytics tracks you AWS cloud utilization:
- Hourly Utilization Pattern Analysis
- Reserved Instances Decision Tool
- Resource Resizing Opportunities
About the Author
Eric Hammond is a builder of technology and technology teams for early stage Internet startups. He has been involved with a series of great startups including Citysearch.com, Stamps.com, Rent.com, ThisNext.com, and is currently helping to grow CampusExplorer.com.
He is a tech blogger at Alestic.com supporting Ubuntu on Amazon EC2.
Keywords: Amazon web services, Amazon AWS console, Amazon Cloud Services, Amazon S3, Cloud Availability, Cloud Performance, AWS Console, AWS Region, Amazon AMI, Ubuntu, EC2 instance, ssh, AWS region, EBS,