I've recently come across an issue whereby I spin up the stack but then have to manually update the compose instance if I want to use a custom Domain with valid SSL certs.
Example:
Spin up the 2 tiered Stack
Define Domain in Route53
Add record set to point the domain name adop.customdomain.com to the outer Proxy
Add the SSL termination rules on the outer proxy
Update the Stack: Need to update the tools Manually
doesn't get persisted and will revert on compose restart
log in to the stack, change the PROXY_IP variables, re-run compose
might create inconsistent behaviour with some of the tools (need to test)
A way to get around this would be to change the setup order and spin up all of the infrastructure components before spinning up the stack. This will allow inputting a CUSTOM_URL to the compose start which will then be used at up time.
Hi,
I've recently come across an issue whereby I spin up the stack but then have to manually update the compose instance if I want to use a custom Domain with valid SSL certs.
Example:
A way to get around this would be to change the setup order and spin up all of the infrastructure components before spinning up the stack. This will allow inputting a CUSTOM_URL to the compose start which will then be used at up time.