> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/api-reference/endpoints/host-access.md).

# Host access

Use these endpoints to define the hosts that access Silk storage, organize them into host groups, register their initiators (IQNs), set up CHAP authentication, and map volumes to them.

| Resource                   | Path                         | Description                                                                                               |
| -------------------------- | ---------------------------- | --------------------------------------------------------------------------------------------------------- |
| Hosts                      | `/hosts`                     | Hosts represent the application and database servers that connect to the system to use its volumes.       |
| Host CHAP profile mappings | `/host_auth_profile_mappers` | Mappings between CHAP profiles and the hosts that use them.                                               |
| Host CHAP profiles         | `/host_auth_profiles`        | CHAP profiles hold the credentials used to authenticate iSCSI connections from hosts.                     |
| Host groups                | `/host_groups`               | Host groups organize hosts that need access to the same volumes, such as the nodes of a database cluster. |
| Host IQNs                  | `/host_iqns`                 | iSCSI Qualified Names (IQNs) identify each host's iSCSI initiator.                                        |
| Mappings                   | `/mappings`                  | Mappings give hosts access to volumes.                                                                    |


---

# 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.silk.us/api-reference/endpoints/host-access.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.
