Technical manual
...
iR Engine on AWS
DNS records
2 min
set up dns records the nginx load balancer must be fully set up and running before this step can be completed in the aws web client, go to route 53, then go into the hosted zone you made earlier click on create record if it starts you under quick create record, click the link 'switch to wizard'; it's not necessary, but the wizard is handy under routing policy, leave it on simple routing and click next then click define simple record the first record should be for the top level domain, e g etherealengine org , so leave the record name text field blank under value/route traffic to, click on the dropdown and select alias to network load balancer select the region that your cluster is in where it says choose load balancer, click the dropdown, and select the nlb that was created leave the record type as 'a route traffic to an ipv4 address and some aws resources', then click define simple record you can keep clicking define simple record to make more records in one batch when you're done, click create records you should make the following 'a' records to the loadbalancer, substituting your domain for 'etherealengine org' etherealengine org etherealengine org @ etherealengine org api dev etherealengine org api etherealengine org dev etherealengine org only if serving client files from client/api pods instanceserver etherealengine org instanceserver dev etherealengine org you also need to make an 'a' record pointing 'resources etherealengine org' or '\<release name> etheralengine org' to the cloudfront distribution you made earlier instead of 'alias to network load balancer', select 'alias to cloudfront distribution', then click the text box that appears that says 'choose distribution' a selector should appear with the subdomain you're routing as well as the cloudfront distribution's domain name, which you should click on then click define simple record