> 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/1-9-0/documentation/services/service-commissioning-files.md).

# Service Commissioning Files

Service commissioning files are the foundation for defining and implementing services in Connectware. These files use YAML format to describe all the resources, configurations, and relationships that make up a [service](/1-9-0/documentation/services.md).

A service commissioning file serves as a blueprint for a service, detailing:

1. The resources required by the service (e.g., users, connections, containers)
2. Configuration parameters for each resource
3. Relationships and dependencies between resources

When you enable a service in Connectware, the system reads the service commissioning file and automatically sets up all specified resources according to the defined parameters.

## Structure

Service commissioning files follow a structured format:

1. They begin with service metadata (name, description, etc.)
2. They list resources, each with its own set of parameters
3. They may include references between resources to establish relationships

The YAML format allows for a human-readable yet precise definition of complex service structures.

For more information, see [Structure of Service Commissioning Files](/1-9-0/documentation/services/service-commissioning-files/structure-of-service-commissioning-files.md).

## Usage

To use a service commissioning file:

1. Create the file following the required structure and syntax.
2. Upload the file to Connectware.
3. Enable the service to implement its defined resources.

In the following sections, we'll explore the structure of commissioning files in detail, including syntax, available resource types, and best practices for creating effective service definitions.


---

# 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/1-9-0/documentation/services/service-commissioning-files.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.