AWS quickstart - how to override sslip autogenerated URL?

[robertlagrant]

The Quickstart was very straightforward to set up, other than one aspect.

I have an application that consists of a static web application and a backend. The web application needs to be aware of its own base URL, and the URL to the backend. One issue is that the web application expects to be served on the root of a domain.

To get around this, is it possible to override the long sslip URLs that are issued by default? Hostnames are less of an issue for me in a quickstart; I'd be very happy with (if the ingress route is /) a service being exposed as X.X.X.X and mapping the IP to a hostname in my /etc/hosts file.

I might have missed how to configure this in the documentation; please slap me on the wrist and point me at it if so!

[bashofmann]

It's currently not easily possible to configure the host name through variables. It's currently "hard coded" to use sslip.io here: https://github.com/rancher/quickstart/blob/master/rancher/aws/infra.tf#L146.
Of course, you can change this directly there. Otherwise a PR to make this optionally configurable through variables would be very welcome.

Please note, that these quickstart examples are not meant for production use cases, but only for short-term evaluations. If you want to set up Rancher in a highly available way for production, or even dev/staging use cases, I'd advise to only take these modules here as a blue print but then modify them for high availability and security. E.g. running Rancher on more than one instance, setting up a proper LB, setting up a proper DNS name and TLS certificates from a proper CA or limiting the VPC.

[robertlagrant]

Thank you! This is just to evaluate Rancher. I happen to want to host DependencyTrack at the same time to run an end to end proof of concept of that as well. No worries about it becoming a production instance.

I will have a look at that and if I can see a neat way to make it a variable, I'll drop a PR. Thanks again!