# Linkerd-Viz Tap FailedDiscoveryCheck while Running on EKS

**URL:** <https://linkerd.buoyant.io/t/linkerd-viz-tap-faileddiscoverycheck-while-running-on-eks/252>\
**Category:** Linkerd General Discussion\
**Tags:** configuration\
**Created:** [September 7, 2023, 1:18pm UTC](https://linkerd.buoyant.io/t/linkerd-viz-tap-faileddiscoverycheck-while-running-on-eks/252 "2023-09-07T13:18:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![yourbromike](https://avatars.discourse-cdn.com/v4/letter/y/d78d45/32.png) [@yourbromike](https://linkerd.buoyant.io/u/yourbromike)\
**Post date:** [September 7, 2023, 1:18pm UTC](https://linkerd.buoyant.io/t/linkerd-viz-tap-faileddiscoverycheck-while-running-on-eks/252/1 "2023-09-07T13:18:59Z")

</div>

I wanted to post some information here in case someone runs into this issue with Linkerd in the future and are running on EKS. Specifically those running the Terraform EKS Module.

```auto
‼ tap API service is running
    FailedDiscoveryCheck: failing or missing response from https://100.64.57.235:8089/apis/tap.linkerd.io/v1alpha1: Get "https://100.64.57.235:8089/apis/tap.linkerd.io/v1alpha1": dial tcp 100.64.57.235:8089: i/o timeout
    see https://linkerd.io/2.13/checks/#l5d-tap-api for hints

```

Also, when viewing the linkerd viz dashboard you will see 503 errors that relate to this issue.  
The way to fix this issue is to allow port 8088-8089 inbound from the EKS Cluster Security group, to the security group running on the nodes.  
To be clear - create a rule on the inbound security group rule list on the nodes, with a source of the EKS Cluster Security Group.

You may have to restart the linkerd-viz tap component, but shortly after tap will be running and you will be able to see your traffic.

---

<div class="post-metadata">

**Author:** ![william](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/william/32/5_2.png) [@william](https://linkerd.buoyant.io/u/william)\
**Post date:** [September 7, 2023, 1:46pm UTC](https://linkerd.buoyant.io/t/linkerd-viz-tap-faileddiscoverycheck-while-running-on-eks/252/2 "2023-09-07T13:46:03Z")

</div>

Thank you @yourbromike!

---

<div class="post-metadata">

**Author:** ![dverzolla](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/dverzolla/32/152_2.png) [@dverzolla](https://linkerd.buoyant.io/u/dverzolla)\
**Post date:** [February 26, 2024, 7:22pm UTC](https://linkerd.buoyant.io/t/linkerd-viz-tap-faileddiscoverycheck-while-running-on-eks/252/3 "2024-02-26T19:22:20Z")

</div>

Thank you @yourbromike

---

<div class="post-metadata">

**Author:** ![vertrost](https://avatars.discourse-cdn.com/v4/letter/v/e36b37/32.png) [@vertrost](https://linkerd.buoyant.io/u/vertrost)\
**Post date:** [December 8, 2025, 3:21pm UTC](https://linkerd.buoyant.io/t/linkerd-viz-tap-faileddiscoverycheck-while-running-on-eks/252/4 "2025-12-08T15:21:36Z")

</div>

Thank you and God bless you, it’s 2025 but the issue is still relevant.