# Expose Kibana externally using NLB with AWS LoadBalancer Controller

**URL:** https://discuss.elastic.co/t/expose-kibana-externally-using-nlb-with-aws-loadbalancer-controller/364347
**Category:** Kibana
**Created:** [August 5, 2024, 6:37am UTC](https://discuss.elastic.co/t/expose-kibana-externally-using-nlb-with-aws-loadbalancer-controller/364347 "2024-08-05T06:37:22Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![toduythienluong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/toduythienluong/32/132460_2.png) [@toduythienluong](https://discuss.elastic.co/u/toduythienluong)
#### Post date: [August 5, 2024, 6:37am UTC](https://discuss.elastic.co/t/expose-kibana-externally-using-nlb-with-aws-loadbalancer-controller/364347/1 "2024-08-05T06:37:22Z")

</div>

Hi,

I am following [this guide](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-overview.html) to have ECK then Elastic Search and Kibana installed on EKS.

Everything is just fine, I have Kabana up and run with port-forwarding as documented, however when I expose the service with type LoadBalancer I cannot access to my kibana. Please notice that I am using EKS and AWS LoadBalancer Controller which provisions a service typed LoadBalancer to a NLB, and an Ingress to ALB. In my case, I see a NLB provisioned on AWS but I cannot access the service via the dns name.

```auto
apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: kms-dev-kibana
spec:
  version: 8.14.3
  count: 1
  elasticsearchRef:
    name: elasticsearch
  http:
    service:
      spec:
        type: LoadBalancer # default is ClusterIP
    tls:
      selfSignedCertificate:
        disabled: true

```

Not sure if I missed something with Kabana, it is working with port-forwarding with localhost, but it doesn't with NLB