bind9-aws-vpc-vagrant-ansible

Vagrant and ansible files to build a bind9 instance in an AWS VPC

repreqs

• install vagrant http://www.vagrantup.com/downloads
• install vagrant-aws plugin via vagrant plugin install vagrant-aws
• install ansible (doesn't work with Windows), see http://docs.ansible.com/ansible/intro_installation.html

env spec file updates

• make a file with your aws access keys with the following two lines $aws_key_id = "<...>" $aws_secret = "<...>"

• vagrant/Vagrantfile

  • edit line "external = File.read ''" to reference file containing your aws keys (see above)

  • edit line "{ :instance_name => 'dns-a-1', :ssh_user => 'ubuntu', :instance_ip => '10.10.10.2', :public_ip => 'false', :ami => 'ami-XXXXXXXX', :subnet => 'subnet-XXXXXXXX', :sg => 'sg-XXXXXXX', :instance_type => 't2.micro' }":

    • instance_name = Name tag
    • ssh_user = AMI's default sudo user
    • instance_ip = private IP if desired to set statically
    • public_ip = 'true' if desired, 'false' if not set
    • ami = ami id
    • subnet = VPC's subnet
    • sg = security group id
    • instance_type = instance type

  • edit line "aws.keypair_name = "<...>"" with the ec2 keypair name associated with your instance

  • edit line "override.ssh.private_key_path = "<...>"" to ref local pem file used to ssh into instance; associated with aws.keypair_name

  • edit line "aws.availability_zone = "us-east-1d"" to be az specific

• ansible/ansible_hosts -- populate ansible hosts file with private ip and hostname of dns instance [aws-dns] hostname=

• ansible/roles/util-dns-bind-config/files/db.site change 10.10.10.2 to desired ip of your dns host change testsite to whatever your site suffix will be

• ansible/roles/util-dns-bind-config/files/named.conf.local testsite to your site

• ansible/roles/util-dns-bind-config/files/named.conf.options -- make specific for your VPC forwarders {172.31.0.2; }; allow-recursion {localnets; 172.31.2.0/24;};

###contact [email protected]