Hello to all the community! I would like to know if one of you has encountered the following issue, and hopefully has solved it ! I’m deploying Kong Docker image as a front-end of an AWS EKS cluster (using NodePort). An ELB is deployed in front of this EKS cluster. The issue is that it looks the …

You can create a route such as /health in Kong (of course make sure that the route doesn’t collide with any of your existing routes) and then add a request-termination plugin on that route to send back a 200 always. Now, you can configure your ELB to have the following healthcheck for Kong’s proxy …

Alright, next I see two options: Make Kong listen on plain HTTP port, open that port up only to the subnet in which ELB is running (public most probably), and then don’t open up port 80 on the ELB. So ELB will be able to Talk on port 80 for health-check but there won’t be a HTTP port available to …

[image] hbagdi: se L4 proxying ( stream_listen ) in kong, open up the port and then make ELB healthcheck that Can you confirm a solution? I believe the below options work when you are routing via a application load balancer, and have control over the health check settings. However, with a …

You can use status_listen in new versions of Kong and turn of error_log for the status endpoint: [image] Open-Source API Management and Microservice Management Secure, Manage & Extend your APIs or Microservices with plugins for authentication, logging, rate-limiting, transformations and m…

Fantastic!! Thanks so much. I was about to fall back to a more radical and hacky solution.

@michael.bowers could you please help me, how to get rid of this logs while using aws nlb load balancer

Yep. Do a few things: In you kong.conf configuration, do the following: enable status_listen, example "status_listen=0.0.0.0:8100 set status_access_log=off set status_error_log=off Then, for your nlb target group, do: “HealthCheckPort”: “8100”, “HealthCheckProtocol”: “TCP” Be sure to enable …

@michael.bowers Thanks ofr that detailed answer. I tried everything you said, but my health checks for AWS NLB fails. Is that because status_listen is internal only and cant be exposed through service. If yes, then I am wondering how the NLB will each it. Maybe I am missing something here?

Stopping logs generated by the AWS ELB health check

Questions

pamiel June 19, 2019, 7:42am 3

Thanks @hbagdi for your reply. Unfortunately, ELB’s health check configuration only allows to select “TCP” as protocol => no way to configure any http endpoint

Topic		Replies	Views
How to configure AWS ELB with HTTPS to Kong on K8S? Questions kubernetes	1	3049	June 30, 2021
How do I deploy Kong with HTTP Load Balancer on EKS Questions kubernetes	5	941	July 25, 2021
Kong Health check failing on AWS ECS	0	301	March 17, 2023
HTTPS between AWS ELB and Kong Questions kubernetes	1	1974	February 25, 2019
How do I deploy Kong with HTTP Load Balancer on GKE kubernetes , kong-gateway	14	4521	February 18, 2022

Stopping logs generated by the AWS ELB health check

Related topics