We are currently creating a separate ALB for every notebook deployment, which costs about $30 per month, each. It would save a lot of money over time if we can just share a single ALB. The separate ALBs got created as part of the ApplicationLoadBalanedFargateService pattern used in the CDK. Now that we are converting notebooks over to use EC2 instead, we should make sure our new stack does not create a new ALB but instead uses the one we already have. We will have to add correct routing rules as part of the stack so that the ALB can route notebooks by domain name.
We are currently creating a separate ALB for every notebook deployment, which costs about $30 per month, each. It would save a lot of money over time if we can just share a single ALB. The separate ALBs got created as part of the ApplicationLoadBalanedFargateService pattern used in the CDK. Now that we are converting notebooks over to use EC2 instead, we should make sure our new stack does not create a new ALB but instead uses the one we already have. We will have to add correct routing rules as part of the stack so that the ALB can route notebooks by domain name.