The template requires that you provide a Route 53 Hosted Zone or Subdomain to redirect your web sites to the LANSA Application Stacks. This is technically simple but it may take time to obtain the appropriate authorisations and for your DNS administrator to apply the changes. Once this is completed the step does not need to be repeated for second and subsequent stacks. Thereafter the LANSA Application Stack template performs all the configuration required.
If you do not want to use a subdomain and instead use the long and cryptic AWS default names then you will need to edit the template to remove the ALIAS record creation.
This is an example of setting up the domain paas.customer.com. You will need to agree on the subdomain name with the DNS administrator before anything may be configured.
1. Use the AWS Route 53 console
Create a hosted zone for "paas.customer.com" and you will get 4 name servers(NS type record)
Email these 4 name server names to your DNS administrator
2. Edit the SOA type record and change the Time-To-Live to 60 seconds
This time effects how quickly a change to a subdomain occurs. This is particularly important when switching between live and backup stacks.
3. DNS Administrator perform on their DNS
Create ns record for "paas.customer.com" and enter the 4 name servers from step 1(From Route 53)
That is, go to the hosted zone for "customer.com" then create NS record for "paas.customer.com"
4. When the template creates the stack it will create an ALIAS record in Route 53 to point to your load balancer.
Following is an example with the NS (the 4 name servers highlighted) and SOA records that are created when creating a Hosted Zone, and two ALIAS records created by two LANSA Application Stacks: