> ## Documentation Index > Fetch the complete documentation index at: https://link.datarelay.run/llms.txt > Use this file to discover all available pages before exploring further. # Scenario Playbooks > Follow complete Data Relay Link workflows, from prerequisites to working traffic and denied-access verification. # Choose your use case These are **operator playbooks**, not feature lists. Each page states which machine runs each command, what the result should be, what to test, and how to recover. > [!NOTE] > > Each playbook uses the installed product CLI. Complete [Server installation](https://link.datarelay.run/getting-started/server-installation.md), then follow the stated Server/Agent role, environment values and expected result. ## Remote Access — outside to inside | Your task | Follow this playbook | | - | - | | Support an SSH server behind NAT | [Remote SSH through NAT](https://link.datarelay.run/use-cases/remote-ssh.md) | | Publish two different services through one LAN relay | [LAN gateway and multiple services](https://link.datarelay.run/use-cases/lan-relay.md) | | Access a private HTTPS administration console | [Private HTTPS console](https://link.datarelay.run/use-cases/private-web.md) | | Allow only your office to connect | [Office-only Remote Access](https://link.datarelay.run/use-cases/office-allowlist.md) | | Access a legacy database via a fixed TCP endpoint | [Fixed TCP remote database](https://link.datarelay.run/use-cases/fixed-tcp-database.md) | ## Internet Access — restricted hosts to approved Internet services | Your task | Follow this playbook | | - | - | | Run Ubuntu APT updates without open Internet | [Restricted Ubuntu updates](https://link.datarelay.run/use-cases/ubuntu-updates.md) | | Allow only approved HTTPS GitHub and API traffic | [Git and API through Internet Access](https://link.datarelay.run/use-cases/github-egress.md) | ## AI and operations | Your task | Follow this playbook | | - | - | | Give verified AI a tightly scoped read-only toolset | [Read-only AI / MCP access](https://link.datarelay.run/use-cases/ai-readonly.md) | | Enroll a small group of branch/partner hosts | [Batch enrollment and inventory groups](https://link.datarelay.run/use-cases/bulk-onboarding.md) | | Apply repeatable configuration safely | [ConfigurationBundle preview and apply](https://link.datarelay.run/use-cases/configuration-bundle.md) | | Safeguard identity and restore after a failure | [Backup, restore and recovery](https://link.datarelay.run/use-cases/backup-recovery.md) | > [!NOTE] > > Images below are visual captures of **actual DataRelay Link CLI terminal output**—not an invented Web UI or synthetic command results. Numbered orange markers point to authentic menu options or result lines. Sources were captured on 2026-10-13/17; sensitive addresses/hosts were masked. Menu choices may change by build: verify the installed **menu**, **help**, and `system version`. ## Shared preparation ![Real Data Relay Link CLI capture — Server menu: enter menu, then choose Remote Access 4, Internet Access 5, AI Access 6 or System 7.](https://mintcdn.com/data-relay/RzAl7zFhuZCRSIKj/images/cli-captures/server-guided-menu.png?fit=max\&auto=format\&n=RzAl7zFhuZCRSIKj\&q=85\&s=b0c33a06335c9fff03e46eddd39eb331) *Figure 1. Server menu: enter menu, then choose Remote Access 4, Internet Access 5, AI Access 6 or System 7. CLI output example; sensitive addresses and hostnames are masked.* ![Real Data Relay Link CLI capture — Agent Host menu: choose 1 to manage its Remote Services; 3 opens ConfigurationBundle.](https://mintcdn.com/data-relay/RzAl7zFhuZCRSIKj/images/cli-captures/agent-guided-menu.png?fit=max\&auto=format\&n=RzAl7zFhuZCRSIKj\&q=85\&s=5752f997527236ce70218caf77a3dc4a) *Figure 2. Agent Host menu: choose 1 to manage its Remote Services; 3 opens ConfigurationBundle. CLI output example; sensitive addresses and hostnames are masked.* 1. Complete [Server installation](https://link.datarelay.run/getting-started/server-installation.md), [deployment mode](https://link.datarelay.run/deployment/modes.md), and [firewall/NAT](https://link.datarelay.run/deployment/firewall-nat.md) using a supported product artifact. Enroll an Agent for Remote Access or Managed Host AI Access; Server-self MCP needs no Agent; agentless HTTP(S) Internet Access does not require one on the protected application host. 2. Open a Server terminal and verify role, installed version and health: ```bash theme={null} sudo drlink system version sudo drlink show status sudo drlink system diagnostics ``` 3. Commands under **Server REPL** run after entering `sudo drlink` on the Linux DRLink Server. **Agent REPL** commands run in `sudo drlink` on the owning Agent Host. **Protected host / outside workstation** commands run in a normal OS shell on that machine. 4. Replace all example addresses, hostnames, client names, account names and ports with values from your deployment. Documentation IP ranges (192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24) are illustrative and do not route on the public Internet. 5. **A policy ALLOW is not a working connection.** Each playbook includes both a policy test and a real application traffic test. **A timeout is not proof of DENY**: look for the actual policy decision/audit. 6. Before changing production-facing policies, assess existing access, preserve a validated backup and use a maintenance window if interruptions are possible. Data Relay Link does not configure external firewalls, DNS, SSH users or TLS certificates on your behalf. ## When something differs Run **help commands**, `system diagnostics` and the corresponding **show** / **test** command on the installed product. Review [CLI reference](https://link.datarelay.run/drlink/cli-reference.md), [troubleshooting](https://link.datarelay.run/troubleshooting/overview.md) and [version and updates](https://link.datarelay.run/reference/release-status.md). Stop if your CLI rejects the documented command; do not invent hidden or legacy syntax. ## New AI workflows — 2026-10-28 | Goal | Follow | | - | - | | Connect Claude and ChatGPT over remote MCP | [HTTPS, OAuth and discovery](https://link.datarelay.run/guides/mcp-clients.md) | | Operate Server-local files, Git and jobs | [Server control lab](https://link.datarelay.run/use-cases/ai-server-control.md) | | Check client compatibility | [MCP compatibility](https://link.datarelay.run/reference/mcp-validation.md) | Server-self operations need separate authorization but no Agent. AI operations on Managed Hosts need a trusted Agent. Screenshots show CLI output examples; MCP examples use the tool arguments alongside the steps. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.