---
icon: material/code-json
---

Specify an inline JSON cli argument or .json file on disk containing launch arguments for pipeline [units](https://doc.log10x.com/engine/pipeline/#units) (i.e., core components) and [modules](https://doc.log10x.com/config/module/) (i.e., user/3rd-party packages). 

JSON configuration follows the same structure as [YAML](https://doc.log10x.com/config/yaml/) configuration. 

Support for JSON configuration enables 10x Engines executing within web server contexts (e.g., [Quarkus](https://doc.log10x.com/api/launch/#quarkus)) to receive arguments as part of a REST request. 

To pass JSON contents to the 10x Engine, [escape](https://stackoverflow.com/questions/10053678/escaping-characters-in-bash-for-json){target="\_blank"} its contents and prefix it with '@': 

This example is derived from the Elastic input default [elastic/config.yaml](https://github.com/log-10x/config/blob/main/pipelines/run/input/analyzer/elastic/config.yaml){target="\_blank"}:

``` console
$ tenx @{\"tenx\":\"@apps/dev\",\"include\":[\"\/run\/modules\/input\/analyzer\/elasticsearch\/module.yaml\",\"\/run\/modules\/input\/analyzer\/elasticsearch\/elastic-input.js\"],\"elastic\":[{\"host\":\"acme.us-central1.gcp.cloud.es.io\",\"token\":\"$=TenXEnv.get(\\\"acmeElasticToken\\\")\",\"targets\":[\"acmeClient\",\"acmeServer\"]}]}
```