How can discourse be fully automated on AWS?

[joelradon]

I wrote a terraform script to boot up an instance, install docker, give public ip, and create app.yml file to automate installation of discourse.

Everything works, but discourse is dependent on having a DNS name so it is unavailable when spun up, as AWS gives you a new IP everytime you create and destroy.

1. What kind of automation is everyone else on aws using?

2. Will everything work as expected if DNS is pointed after build is run?

[Falco]

@joelradon

AWS gives you a new IP everytime you create and destroy.

AWS have floating IPs and you can put a load balancer in front too. There are many ways to approach this, but way beyond the scope of the support we provide here in Meta.

@joelradon

Will everything work as expected if DNS is pointed after build is run?

Depends. If you want to issue an Let’s Encrypt certificate, that happens on rebuild, so the DNS must be set during it.

[michaeld (Michael - Communiteq)]

@joelradon

Everything works, but discourse is dependent on having a DNS name so it is unavailable when spun up, as AWS gives you a new IP everytime you create and destroy.

You can use Terraform to create a DNS entry for your newly assigned IP.