> For the complete documentation index, see [llms.txt](https://docs.remote.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.remote.it/features/connection-options/jump-service.md).

# Jump Service

Use one device as a jump box to reach TCP services on other devices on the same LAN — printers, appliances or an AWS VPC — without installing Remote.It on each.

A jump service lets one device running Remote.It reach TCP services on other devices on the same LAN, without installing Remote.It on those other devices. The device running Remote.It is often called a **jump box**.

Use a jump service when the device you want to reach can't run Remote.It, such as a printer, a network appliance, or a hosted resource. In AWS, for example, a single EC2 instance can act as the jump box into your VPC.

{% hint style="info" %}
Install Remote.It on a device that's online at all times. The jump service only works while the jump box is available.
{% endhint %}

For step-by-step setup, see [How to set up a Jump Service](https://link.remote.it/support/jumpbox).

For a walkthrough aimed at non-technical users, see [Remote Access Over Starlink](https://docs.remote.it/introduction/get-started/starlink.md), which uses a jump service to reach cameras and DVRs behind CGNAT.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.remote.it/features/connection-options/jump-service.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
