# Terraform, Traffic Filters and Kibana

**URL:** <https://discuss.elastic.co/t/terraform-traffic-filters-and-kibana/327767>\
**Category:** Elasticsearch\
**Created:** [March 15, 2023, 3:48pm UTC](https://discuss.elastic.co/t/terraform-traffic-filters-and-kibana/327767 "2023-03-15T15:48:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tensor](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@tensor](https://discuss.elastic.co/u/tensor)\
**Post date:** [March 15, 2023, 3:48pm UTC](https://discuss.elastic.co/t/terraform-traffic-filters-and-kibana/327767/1 "2023-03-15T15:48:58Z")

</div>

Hi!

We have been successfully using Terraform to set up Elasticcloud instances, and using traffic filtering to allow only access via private link to our own Azure serup - almost too successful, as it turns out, as it means we cannot access the cluster with Kibana from the cloud portal- - we just get  
{"ok":false,"message":"Forbidden"}

This kind of makes sense - but for support and development we'd like to be able to query our indexes directly.

I assume this means we need to add an additional filter to effectively whitelist the cloud Kibana instance. What would this look like in terraform?

Thanks

Tim

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 12, 2023, 3:49pm UTC](https://discuss.elastic.co/t/terraform-traffic-filters-and-kibana/327767/2 "2023-04-12T15:49:01Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.