> For the complete documentation index, see [llms.txt](https://docs.feast.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feast.dev/reference/registries/remote.md).

# Remote

## Description

The Remote Registry is a gRPC client for the registry that implements the `RemoteRegistry` class using the existing `BaseRegistry` interface.

## How to configure the client

User needs to create a client side `feature_store.yaml` file, set the `registry_type` to `remote` and provide the server connection configuration. The `path` parameter is a URL with a port (default is 6570) used by the client to connect with the Remote Registry server.

{% code title="feature\_store.yaml" %}

```yaml
registry:
  registry_type: remote
  path: localhost:6570
```

{% endcode %}

The optional `cert` parameter can be configured as well, it should point to the public certificate path when the Registry Server starts in SSL mode. This may be needed if the Registry Server is started with a self-signed certificate, typically this file ends with \*.crt, \*.cer, or \*.pem.

For **mutual TLS (mTLS)**, you can also configure:

* `client_cert` — Path to the client certificate presented to the server. Must be paired with `client_key`. Typically ends with `*.crt` or `*.pem`.
* `client_key` — Path to the client private key. Must be paired with `client_cert`. Typically ends with `*.key` or `*.pem`.

When connecting through a tunnel or proxy where the connection address differs from the server hostname, set:

* `authority` — Overrides the gRPC `:authority` header so the server certificate is validated against the correct hostname.

{% code title="feature\_store.yaml" %}

```yaml
registry:
  registry_type: remote
  path: localhost:8443
  cert: /path/to/ca.crt
  client_cert: /path/to/tls.crt
  client_key: /path/to/tls.key
  authority: feature-registry.example.com
```

{% endcode %}

More info about TLS configuration can be found in [feast-client-connecting-to-remote-registry-sever-started-in-tls-mode](/how-to-guides/starting-feast-servers-tls-mode.md#feast-client-connecting-to-remote-registry-sever-started-in-tls-mode)

## How to configure the server

Please see the detail how to configure registry server [registry-server.md](/reference/feature-servers/registry-server.md)

## How to configure Authentication and Authorization

Please refer the [page](/getting-started/concepts/permission.md) for more details on how to configure authentication and authorization.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.feast.dev/reference/registries/remote.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.