--- layout: "docs" page_title: "proxy Stanza - Job Specification" sidebar_current: "docs-job-specification-proxy" description: |- The "proxy" stanza allows specifying options for configuring sidecar proxies used in Consul Connect integration --- # `proxy` Stanza
Placement |
job -> group -> service -> connect -> sidecar_service -> **proxy**
|
---|
(int:[port][])
- The port the local service binds to.
Usually the same as the parent service's port, it is useful to customize in clusters with mixed
Connect and non-Connect services
- `upstreams` ([upstreams][]: nil)
- Used to configure details of each upstream service that
this sidecar proxy communicates with.
- `config` (map: nil)
- Proxy configuration that's opaque to Nomad and
passed directly to Consul. See [Consul Connect's
documentation](https://www.consul.io/docs/connect/proxies/envoy.html#dynamic-configuration)
for details.
## `proxy` Examples
The following example is a proxy specification that includes upstreams configuration.
```hcl
sidecar_service {
proxy {
upstreams {
destination_name = "count-api"
local_bind_port = 8080
}
}
}
```
[job]: /docs/job-specification/job.html "Nomad job Job Specification"
[group]: /docs/job-specification/group.html "Nomad group Job Specification"
[task]: /docs/job-specification/task.html "Nomad task Job Specification"
[interpolation]: /docs/runtime/interpolation.html "Nomad interpolation"
[sidecar_service]: /docs/job-specification/sidecar_service.html "Nomad sidecar service Specification"
[upstreams]: /docs/job-specification/upstreams.html "Nomad upstream config Specification"
[port]: /docs/job-specification/network.html#port-parameters "Nomad network port configuration"