Lb complains if security group not specified, but says SGs are only for http LBs if I specify one about fargatecli HOT 4 OPEN

Hi @darthcabs , did you check that your security group opens this port to the public? (I have only one subnet, but had to open load balanced ports to ingress on that port.)

from fargatecli.

Actually I have same issue. For HTTP & HTTPS it works without problem, however if I use tcp: ports then fargate shows same error.

fargate lb create aml-service-lb --port tcp:80 --security-group-id sg-05e3a638d5d4ada93 --cluster core-master --region eu-west-1
- security groups can only be specified for HTTP/HTTPS load balancers

from fargatecli.

apparently aws does not support security groups on network lb.
https://www.linkedin.com/pulse/aws-new-network-elastic-load-balancernlb-few-silvio-l-de-morais/

from fargatecli.

May it be that your script used application load balancer, and now it converts to Network Load Balancer (TCP) than does not understand security groups?

from fargatecli.