-
Notifications
You must be signed in to change notification settings - Fork 35
Description
We deployed this internally for organization as a pilot and one of our requirements is that all traffic from start to finish needs to be encrypted. For the most part, this looks to be the case except that the target groups for the ALB seem to communicate over HTTP and not HTTPS as expected. If I understand correctly, this would mean the web traffic would be unencrypted for just this brief step.
I also notice that it's hardcoded this way in the terraform as well.
guidance-for-multi-provider-generative-ai-gateway-on-aws/litellm-terraform-stack/modules/ecs/alb.tf
Lines 87 to 92 in 8de9f7d
| resource "aws_lb_target_group" "tg_4000" { | |
| name = "${var.name}-4000" | |
| port = 4000 | |
| protocol = "HTTP" | |
| vpc_id = var.vpc_id | |
| target_type = "ip" |
guidance-for-multi-provider-generative-ai-gateway-on-aws/litellm-terraform-stack/modules/ecs/alb.tf
Lines 106 to 111 in 8de9f7d
| resource "aws_lb_target_group" "tg_3000" { | |
| name = "${var.name}-3000" | |
| port = 3000 | |
| protocol = "HTTP" | |
| vpc_id = var.vpc_id | |
| target_type = "ip" |
Could this be changed? It seems like a small oversight.