# Basic Ingress not working **URL:** \ **Category:** Questions\ **Tags:** kubernetes\ **Created:** [May 13, 2022, 10:43am UTC](https://discuss.konghq.com/t/basic-ingress-not-working/10170 "2022-05-13T10:43:03Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![robincher](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/robincher/32/1245_2.png) [@robincher](https://discuss.konghq.com/u/robincher)\ **Post date:** [May 18, 2022, 1:37pm UTC](https://discuss.konghq.com/t/basic-ingress-not-working/10170/2 "2022-05-18T13:37:53Z")
I supposed you are using Application Load Balancer to front the cluster? Have you check if you have any security groups that restrict traffic from your origin(workstation), or if the ALB targets group are properly reference to the EKS nodes? Maybe this will give you a better picture > [@Kong with AWS Application Load Balancer](https://discuss.konghq.com/t/kong-with-aws-application-load-balancer/6568/13): > > hi, sorry for the late reply. 1. deploy the alb-ingress-controller Instructions to install the alb-ingress-controller can be found here (I used helm ): [https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html](https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html) 2. deploy the kong-proxy Deploy kong without creating a load balancer (use NodePort type). I used helm again: [https://github.com/Kong/charts](https://github.com/Kong/charts) 3. Create your ingress Then create your ingress pointing to the kong proxy service: apiVersion: networking.k8s.io/v1… --- _[View the full topic](https://discuss.konghq.com/t/basic-ingress-not-working/10170)._