# Watcher HTTP request when using traffic filters?
**URL:** https://discuss.elastic.co/t/watcher-http-request-when-using-traffic-filters/352152
**Category:** Elastic Cloud Enterprise (ECE)
**Created:** [January 31, 2024, 6:28am UTC](https://discuss.elastic.co/t/watcher-http-request-when-using-traffic-filters/352152 "2024-01-31T06:28:06Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Jared\_Wallace](https://discuss.elastic.co/u/Jared_Wallace)
#### Post date: [January 31, 2024, 6:28am UTC](https://discuss.elastic.co/t/watcher-http-request-when-using-traffic-filters/352152/1 "2024-01-31T06:28:06Z")
I'm having some trouble getting Watcher HTTP requests to function when using traffic filters on Elastic Cloud Enterprise.
A Watcher with the following block works perfectly, returning 200s as expected on a fresh Deployment, where `foo.es.endpoint.io` is the ES endpoint retrieved from the Deployment dashboard.
```auto
{
...
"input": {
"http": {
"request": {
"scheme": "https",
"host": "foo.es.endpoint.io",
"port": 443,
"method": "get",
"path": "/_cluster/health",
"params": {},
"headers": {},
"auth" : {
"basic" : {
"username" : "username",
"password" : "password"
}
}
}
}
},
...
}
```
My trouble starts when adding a Traffic Filter (say a GCP private link filter or IP filter), which results in the Watcher returning 403s. I imagine this is because the endpoint isn't resolved internally.
Does anyone know how to make this work on Elastic Cloud through the traffic filter, or staying 'within the deployment' internally?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 14, 2024, 6:28am UTC](https://discuss.elastic.co/t/watcher-http-request-when-using-traffic-filters/352152/2 "2024-02-14T06:28:12Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.