I typically use Amazon’s AWS EC2 cloud services which include Route53 for DNS however I have certain clients that prefer RackSpace and therefore require RackSpace Cloud DNS services. One of the primary reasons for not just using an external DNS service such as Amazon’s Route53 DNS service is because when you setup large cloud deployments you typically are going to need internal DNS entries for communication between cloud instances and DNS services such as Route53 will not respond externally to RFC1918 or private IP space for those DNS entries. Anyhow one thing that is well documented or easy to accomplish on Route53 is creating A records with multiple IP’s for round robin DNS which provides a cheap easy to configure load balancing of sorts for different services such as MySQL. I could not find any documentation or mention of round robin DNS setup on RackSpace Cloud DNS so I wanted to explain how I was able to accomplish this.
Amazon’s AWS products are pretty amazing and allow you to scale with ease for short or long term projects. One thing that can be helpful is mounting extra storage to AWS instances so you have the ability to unmount the storage and mount to different instances in the future. The other benefit is the ability to terminate an Amazon AWS instance and keep the Elastic Block Store (EBS) volume to use on another AWS instance at a later date. Use the directions below to create an Amazon EC2 EBS volume, attach the volume to an Amazon AWS instance, format the volume, and then mount the volume to the instance.
When I first was working with an Amazon Web Services instance at EC2 I was getting frustrated trying to use SecureCRT to connect to the AWS instance. When you configure an instance you are required to configure an Amazon EC2 key pair which will allow you to connect to your instances via SSH. The problem is once you receive the key pair via download it will not work with SecureCRT so you need to convert it to a public key to work. I did a lot of searching and didn’t find much but the below worked for me.
LOG: could not translate host name “localhost”, service “5432” to address: Name or service not known
I recently installed PostgreSQL on an Amazon Web Services CentOS instance however when I first attempted to start Postgres I received an error that I had never seen before. The pgstartup.log file located in /var/lib/pgsql contained the below data.
./lib/rubygems/custom_require.rb:31:in `gem_original_require’: no such file to load — rdoc/rdoc (LoadError)
When attempting to install rubygems on a fresh Amazon Web Services EC2 instance I received the below error. Ruby had been installed by default on the instance and I was installing rubygems manually. The below error was received when attempting to run the setup.rb script with ruby.