Let's Encrypt being provisioned before EIP is attached about zoolander-ci HOT 3 OPEN

Will need to create an elastic network interface and then attach it to the EIP, and then attach the interface to the instance, that way the instance boots with the EIP and can run the provisioners with the EIP working.

from zoolander-ci.

Build plan would look like this:

• eip
  • route53 record
• security-group
• vpc
  • subnet
    • eni
      • attach eip to eni
      • attach security-group to eni
      • instance
        • provision with route53 record

Alternatively, could attempt to base the route53 record on the ephemeral address of the instance, since the TLS certificates won't care if that changes:

• instance
  • route53 record of instance ip
    • provision instance with route53 record

Though it remains to be seen whether terraform will regard this as a circular dependency. Even if that is the case, we could possibly do this in two passes:

Pass 1

• instance
  • route53 record of instance ip

Pass 2

• Wait for DNS to propogate
  • Provision instance (ansible-style) with Route53 record

from zoolander-ci.

The latter approach would obsolete the EIP and we could forgo #61

from zoolander-ci.