search

hackoregon / civic-devops

Master collection point for issues, procedures, and code to manage the HackOregon Civic platform
MIT License
11 stars 4 forks source link

Validate proposed subdomain use in ELB targets for 2018 services #100

Closed iant01 closed 5 years ago

iant01 commented 6 years ago

This is also associated with issue #96 and issue #99

We will be using load balancer targetting rules for 2018 services which use subdomain/host rather than simple path mapping (ie. civic2018.civicpdx.org )

With this domain setup (which aws did not support when I was learning things early last year, and apparently only started supporting it mid 2017) the civic-2017 should be able to be on path " / " with the other 2017 services and civic-2018 on / now need to make sure hacko is on an application load balancer as I have a suspicion they may have only enabled domian/host on it (if we are on classic load balancer, will check to see if supported there as well)

Setup in route53 will be needed once 2018 services are added to the current ECS and load balancer and the setup verified end to end .

iant01 commented 6 years ago

Hacko is using Application load balancer so domain/host is permitted as listener target (good) AWS documentation only provides information on how to set via the load balancer console if you want a path other than just foo.acme.org AWS changed the field value from host-pattern to host-header but did not get all the references changed in all areas of documentation, examples or snipets. CloudFormation is very picky about how things are done/specified, but provides very little debug information to figure out what is not correct.

But finally got it to work, now pushing to Hacko.

MikeTheCanuck commented 6 years ago

It would be awesome to write a little tiny markdown doc that explains how to do this for when (not if) we need to do such a thing again.