This message was deleted.
# generals
sparse-intern-71089
02/28/2022, 9:54 AMThis message was deleted.
g
great-queen-39697
02/28/2022, 2:24 PMCan you share a bit of your code? I went digging in the code and don't see any reason that it wouldn't be supported, but I want to reproduce if I can so we can open an issue.
w
wet-fall-68417
03/01/2022, 4:46 PMyes
wet-fall-68417
03/01/2022, 4:47 PM Copy code
const internalLbTargetGroup = new aws.lb.TargetGroup("internal-lb-target-group", {
name: "studio-internal-lb-target-group",
targetType: "alb",
port: 80,
protocol: "HTTP",
vpcId: vpc.id,
healthCheck: {
path: "/api/health",
interval: 10,
enabled: true,
},
tags: {
Owner: "studio",
project: "studio"
},
});wet-fall-68417
03/01/2022, 4:51 PMIn addition, you can see in the error message that there is no ‘alb’ option -
[instance ip lambda] , and also in pulumi docs there is no mention to it, only in the aws docs.
https://www.pulumi.com/registry/packages/aws/api-docs/alb/targetgroup/
wet-fall-68417
03/01/2022, 5:49 PM@great-queen-39697
g
great-queen-39697
03/01/2022, 8:49 PMOk, as I've stood up a similar bit of code, and I can create one with the ALB target type. However, the error is coming when we try to set it to the HTTP protocol. TCP works; HTTP does not. I'm looking into why
great-queen-39697
03/01/2022, 8:52 PMAh, right. ALBs can only have TCP as a target protocol:
6. For Protocol, only TCP is allowed. Select the Port for your target group. This target group port must match the listener port of the Application Load Balancer. Alternatively, you can add or edit the listener port on the Application Load Balancer to match this port.https://docs.aws.amazon.com/elasticloadbalancing/latest/network/application-load-balancer-target.html#register-application-load-balancer-target
w
wet-fall-68417
03/02/2022, 8:03 AMthanks @great-queen-39697! i guess the error msg is confusing. anyway, you are the best, thanks again!
🙌 1
5 Views