> 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/services.md). # Services Services allow you to automate deployment and management of multiple connected operations. Services in Connectware are configurations that allow for the simultaneous setup and execution of multiple operations. They follow the Infrastructure as Code principle, enabling you to manage complex setups through a single point of configuration. ## What is a Service? A service is a collection of resources and their configurations, which can include: * User management and permissions * Network connections * Containerized applications * Data processing tasks When enabled, a service automatically implements all its defined resources. When disabled, it removes these resources, returning the system to its previous state. ## How to Implement Services? Services are defined using a [service commissioning file](/2-6-1/data-flows/service-commissioning-files.md) - a YAML-formatted text file that specifies all required resources and their parameters. This file serves as a complete description of the service's components and their relationships. ## Key Aspects of Services * They allow for consistent, repeatable deployments * They can be version-controlled * They simplify the management of complex configurations Two features build directly on services: the [Rule Engine](/2-6-1/data-flows/rule-engine.md) transforms data as it flows through your mappings and endpoints, and [FlowSync](/2-6-1/data-flows/flowsync.md) enables transactional data flows that carry a response or error back to the requesting system. The following sections explain how to create, manage, and use services effectively within Connectware. --- # 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/services.md?ask=&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.