- 최신
- 최다 투표
- 가장 많은 댓글
Hello,
As you described, the NLB with TCP healthcheck is basically just going to open a TCP connection on the target + port, and report it healthy if it can open the TCP session. There is no notion of passive healthcheck, it is all actively opening connections to targets to evaluate their health.
The way the ECS Task (container(s)) gets added to the Target Group "targets", is that after your container is up, ECS will go ahead and attach the container as a target to aforementioned Target Group. Then the health check starts.
If you stop the fargate task, then ECS will remove it from the Target Group (and therefore from the Listener Rule and therefore from the NLB (or ALB)).
The healthy hosts metric indeed is a good indicator of whether your targets are healthy or not.
If you want an end-to-end demo with NLB + ACM (so, using TLS at the NLB) and Fargate, have a look at this (part 2 is in the writing).
Hope this helps,
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전