---
title: "Configure the XDR Proxy"
description: "Configure the Aerospike XDR Proxy using the YAML config file to manage ports, destination nodes, and logging settings."
---

# Configure the XDR Proxy

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

The XDR Proxy is configured using the `/etc/aerospike-xdr-proxy/aerospike-xdr-proxy.yml` YAML formatted configuration file.

The configuration file has the following sections:

-   [service](https://aerospike.com/docs/database/8.1.2/manage/xdr/proxy/config/service) - configures the connector’s listening ports, TLS and network interface.
-   [aerospike](https://aerospike.com/docs/database/8.1.2/manage/xdr/proxy/config/aerospike) - configures Aerospike destination nodes.
-   [logging](https://aerospike.com/docs/database/8.1.2/manage/xdr/proxy/config/logging) - configures the destination and level for the connectors logs.
-   [record-ordering](https://aerospike.com/docs/database/8.1.2/manage/xdr/proxy/config/record-ordering) - configures ordering of outbound records.

## Aerospike Database setup

The XDR Proxy requires the Aerospike database to push updates and record deletes to the proxy using [change notification](https://aerospike.com/docs/connectors/streaming/common/change-notification).

## XDR 5.0.0 connector wire protocol

A sample configuration is shown below with

```yaml
service:

  port: 8080

aerospike:

  seeds:

    - 192.168.2.3:

        port: 8080

  socket-timeout: 1000

  total-timeout: 1000

logging:

  enable-console-logging: true

  file: /var/log/aerospike-xdr-proxy/aerospike-xdr-proxy.log
```

## HTTP based connector configuration

Requires XDR Proxy version `2.0.0` or higher.

```yaml
service:

  port: 8080

  protocol: HTTP_2

aerospike:

  seeds:

    - 192.168.2.3:

        port: 8080

  socket-timeout: 1000

  total-timeout: 1000

logging:

  enable-console-logging: true

  file: /var/log/aerospike-xdr-proxy/aerospike-xdr-proxy.log
```