> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/data-flows/agents/configuring-agents.md).

# Configuring Agents

Deploy connections, endpoints, and mappings on agents by setting the agentName property in your service commissioning file.

Agents support the following resource types:

* [Cybus::Connection](/2-6-1/data-flows/service-commissioning-files/resources/cybus-connection.md)
* [Cybus::Endpoint](/2-6-1/data-flows/service-commissioning-files/resources/cybus-endpoint.md)
* [Cybus::Mapping](/2-6-1/data-flows/service-commissioning-files/resources/cybus-mapping.md)

The endpoint resource can also use the `rules` property to enable data manipulation and pre-processing on the edge, using the [Rule Engine](/2-6-1/data-flows/rule-engine.md) for edge processing.

To deploy these resources on an agent, set the `agentName` property for each connection in the service commissioning file. All endpoint resources that rely on that connection will automatically run on the same agent, without needing additional configuration.

{% hint style="danger" %}
The value of the `agentName` property (for `Cybus::Connection` resources) must exactly match the `CYBUS_AGENT_NAME` environment variable value used during agent startup.
{% endhint %}


---

# 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.cybus.io/2-6-1/data-flows/agents/configuring-agents.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.