Showing posts with label route 53. Show all posts
Showing posts with label route 53. Show all posts

Tuesday, 27 November 2012

Amazon Elastic Load Balancing

The book I read to research this post was AWS Elastic Load Balancing Developer Guide which is a very good book which I downloaded from kindle for free. Elastic Load Balancing or ELB works with EC2 & S3 to allow you to configure how many instances need to be open in response to various situations. It's also compatible with SQS. For complicated procedures you can any of a variety of software development kits or SDK's which include java and ruby among others. The default destination server farm is North Virginia but you can specify any & it's a good idea to use two in case one goes offline. You use the command line in the console for most of your work & the book contains useful sample code. Finally a lot of people like there cloud site to have a proper domain name & this can be done using Route 52 or alternatively you can visit http://icann.org for a list of official vendors.

Sunday, 26 August 2012

Amazon Route 53

The book I read to research this post was Amazon Route 53 Developer Guide which is a very good book and which I downloaded for free from kindle. Route 53 works with quite a few other Amazon services like S3 or simple storage service & EC2 or elastic compute cloud. if you have a hosted website by someone else it will also work with that. Basically it lets you link a website which is already up and running to a DNS name or several DNS names. When you sign up part of the process is you get a phone call from Amazon and have to enter a pin number presumably to avoid people running loads of sites maybe for dodgy purposes like selling viagra. I think Amazon want to make sure there is a real person at the other end. If you have a website at more that one Amazon server farm they will direct traffic to the less busy one at any one time. They have a server farm serving most continents ie one in Ireland serving Europe & one in Singapore serving Asia. If you have the Elastic Load Balancing from Amazon the TTL or Time To Live which is the time before it gives up trying to connect you and assumes it's a bad line, anyway the TTL in ELB takes precendence over the one in Route 53 so if you need to adjust it you need to do it in ELB.