# Services A service describes the collection of all settings and necessary resources (like managing users, setting permissions, starting containerized applications, etc.) as a single point of configuration and execution. Hence, a service - once enabled - may automatically add several users, establish connections, start containerized applications which perform some kind of data manipulation tasks for example. When disabled, all users, connections, and containerized applications created before will be removed again. In more technical words, a service describes a set of resources, their parametrization and relations in between. Services closely follow the *Infrastructure as Code* idea and are modelled very similar to Amazon’s *CloudFormation* project (). Services are installed using a [commissioning file](/1-7-3/documentation/services/structure-of-commissioning-files.md). Within this text-base file in YAML format all resources including their parametrization must be listed. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cybus.io/1-7-3/documentation/services.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.