Why are we creating a route53 in an ansible playbook?

[mahmoudimus]

This is going around cloudformation, which reduces the value and entire point of using cloudformation. When I delete a stack, this route should be cleaned up.

https://github.com/balanced-ops/ansible-base/blob/master/tasks/dns.yml#L22-L29

[mahmoudimus]

Related to #7

[mjallday]

http://serverfault.com/questions/599721/how-do-i-create-dns-entries-for-ec2-instances-created-by-auto-scaling

This is not something you can do with CloudFormation, as its involvement stops at defining the auto-scaling groups - it doesn't got to see the instances started by the ASG. Auto-scaling groups don't give you any way to do this either.
Instead, you could ensure your instances run something on startup to register themselves in Route 53. This post talks about using Chef to do it, but you could do the same thing in a standalone script.

That's assuming no new functionality has been added since then.

The question could be, what's the point of DNS entries? Can we just change the local hostname and be done with it?

[bninja]

agree w/ this. ansible roles ideally know nothing about aws and so should not be creating aws resources (*-infra does that using cfn and ansible plugins). there may be ways to do this (scaling event to r53 or something) but imo are not worth it (ansible host matching is simple).