quick-action-34599
04/18/2019, 5:59 PMawsx.elasticloadbalancingv2.ApplicationListener
to a port on an ecs service other than the port that it’s listening on? i.e. the AL listens on port 80 and forwards to port 8081 on the container. I assume you can’t pass the listener itself as an argument to the container’s portMappings
?white-balloon-205
lemon-spoon-91807
04/18/2019, 5:59 PMnew awsx.elasticloadbalancingv2.NetworkTargetGroup("custom", { port: 8081 })
.createListener("custom", { port: 80 });
quick-action-34599
04/18/2019, 6:01 PMlemon-spoon-91807
04/18/2019, 6:02 PMquick-action-34599
04/18/2019, 6:02 PMlemon-spoon-91807
04/18/2019, 6:03 PMquick-action-34599
04/18/2019, 6:04 PMlemon-spoon-91807
04/18/2019, 6:05 PMquick-action-34599
04/18/2019, 6:07 PMlemon-spoon-91807
04/18/2019, 6:07 PMnew awsx.elasticloadbalancingv2.NetworkTargetGroup("custom", { port: 8081 })
.createListener("custom", { port: 80 });
quick-action-34599
04/18/2019, 6:07 PMlemon-spoon-91807
04/18/2019, 6:07 PM.createListener
quick-action-34599
04/18/2019, 6:07 PMlemon-spoon-91807
04/18/2019, 6:08 PMquick-action-34599
04/18/2019, 6:08 PMlemon-spoon-91807
04/18/2019, 6:13 PMquick-action-34599
04/18/2019, 6:14 PMlemon-spoon-91807
04/18/2019, 6:17 PMquick-action-34599
04/18/2019, 6:19 PMlemon-spoon-91807
04/18/2019, 6:19 PMwaitForSteadyState: false
on your EC2Servicequick-action-34599
04/18/2019, 6:19 PMlemon-spoon-91807
04/18/2019, 6:20 PMquick-action-34599
04/18/2019, 6:20 PMlemon-spoon-91807
04/18/2019, 6:21 PMwaitForSteadyState: false
at least gets you in a position where you can start interrogating AWS to see what issue they have.quick-action-34599
04/18/2019, 6:25 PMNone of these Availability Zones contains a healthy target. Requests are being routed to all targets.
lemon-spoon-91807
04/18/2019, 6:27 PMquick-action-34599
04/18/2019, 6:32 PMlemon-spoon-91807
04/18/2019, 6:43 PMquick-action-34599
04/18/2019, 6:46 PM