ec2base

http://mutexlock.blogspot.com/2010/01/resetting-overwriting-etcresolvconf-in.html

For our purposes – we had set up an internal dns server running (bind – process ‘named’ on a particular host).

Before making the change – the file /etc/resolv.conf was looking as follows.

http://www.ducea.com/2009/06/01/howto-update-dns-hostnames-automatically-for-your-amazon-ec2-instances/

A while ago one of the major problems people faced to use Amazon EC2 into production environments was the dynamic state of the instances IPs. Every time one instance was started it was getting a new, dynamic IP. This has been addressed with the introduction of Amazon Elastic IP Addresses, but even when using this, the private IPs are still dynamic and most of the time people will want to communicate between several instances on the private allocated IPs and not on the public ones. This article will show how you can easily automate the process to update DNS hostnames for your EC2 instances, by adding to the AMI’s the logic for this. I will use for this a master DNS server running bind9, but this can be adapted to any other DNS server.

http://elwoodicious.com/2009/12/23/using-elb-to-serve-multiple-domains-over-ssl-on-ec2-for-giggles/

One of the complaints about EC2 is that you only have one IP address allocated per instance which makes it difficult to host, in a clean manner, multiple domains that require SSL certs. Where you have control over IP allocation you could punch down a couple for one server and then set up your domains and SSL certs by IPs. That method is a no go so you are left with the ugly method of allocating those certs by port, something that Joe and Jane public are a little skittish about (https://superawesomefuntime.com is cool but https://superawesomefuntime.com:8443 smells phishy). Thankfully, ELB makes for a great proxy to hide the hideousness of the port-based workaround.

http://www.kinlane.com/?p=1053

I have been going round and round with Amazon Web Services EC2 and Trend Micro MAPS for about 2 weeks now about the entire Amazon IP address block being black listed.

Finally got some action out of Amazon. They are going to add PTR records for all of the IP addresses that we own.

http://developer.amazonwebservices.com/connect/thread.jspa?threadID=36403

If you want to be really forward-thinking, use an Elastic IP. This gives you a public IP address that you can move from instance to instance (via the AWS Management Console – which is also where you get one of these Elastic IPs). Elastic IPs make it easy to launch a replacement instance but keep the same IP address, which can be very useful if you need to recover from a problem.

http://www.freemindsystems.com/amazon-ec2-introduction-useful-info-and-tricks/

I’m sure many people think the cloud is the future, and more or less have migration plannings. Also, some of these people point to Amazon as supplier for their price, stability and capabilities. This first post of EC2 are things you need to know from the standpoint of a sysadmin.

For a System Administrator, Amazon EC2 is a big challenge, mostly because their ephemeral nature:

http://www.stevenringo.com/elastic-ip-on-amazon-ec2-why-using-a-cname-is

I have two options for creating this in my DNS Zone file:
1. Create an A record pointing to 186.210.34.68, or
2. Create a CNAME record pointing to ec2-186-210-34-68.compute-1.amazonaws.com

On immediate inspection, these seem to essentially give the same end result. And for most purposes this will work fine.

http://www.vim-fu.com/better-dns-scheme-for-amazons-ec2-cloud/

One of the fundamental issues to deal with while building out my company’s cloud deployment was the need to assign our own hostnames to our instances. To accomplish this, we needed some sort of internal dns solution. One complication we encountered was that the instances where located in different EC2 regions (EU, US and soon, a possible second US region). Each Amazon region has it’s own private class A ip range, to which the instances are NAT’d, and public class B’s.