I made some big improvements to help with stability of the platform. I've only implemented the changes on dev so far. I've added an Application Load Balancer in front of the wlcp-gateway. This serves the following:
Allows AWS to handle our SSL certs (auto renew, longer expiration and free with aws services) - Before it was a very annoying manual process I had to do every 3 months.
Allows for the creation of multiple wlcp-gateways (for added resilience). Application load balancer will balance between gateway instances and then the gateway instances will balance between the rest of our microservices (api, ui, transpiler, metrics, etc)
And most importantly - handles DNS resolution for us automatically. Right now without the ALB in front of the gateway, everytime the gateway restarts or crashes I have to manually copy the public IP address into our DNS records. Therefore if the gateway goes down if I don't notice it or someone else doesnt, the IP will not get updated and no one will be able to connect to the WLCP. The ALB handles this for us automatically.
I've created a new CNAME record to point to our ALB's DNS Name (A-record)
I made some big improvements to help with stability of the platform. I've only implemented the changes on dev so far. I've added an Application Load Balancer in front of the wlcp-gateway. This serves the following:
I've created a new CNAME record to point to our ALB's DNS Name (A-record)
alb-test.wearablelearning.org