> For the complete documentation index, see [llms.txt](https://bastion.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bastion.gitbook.io/docs/configure/configure-bastion.md).

# Configure Bastion

Bastion stores some configurations and credentials in its `settings.yaml` file. It refers to it before booting up and if you have not set it up yet or made some mistakes, Bastion will not be able to start. So, this is a very important step.

Make sure the `settings.yaml` file is present before you start Bastion. If it is not present in there, don't worry, you will find another file named `settings.example.yaml`. Make a copy of this file and remove the `.example` part from the file name. Now, you should have these files in the directory:

* `settings.yaml`
* `settings.example.yaml`

<figure><img src="https://2090128309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LKg6aQ3L4kyoODrZlxA%2Fuploads%2FpNSokibNu9FfAQ10LWL9%2Fimage.png?alt=media&amp;token=f1b6052f-3df9-4dca-97c2-30e2d20b7e61" alt=""><figcaption></figcaption></figure>

Now you can open and edit the `settings.yaml` file to add (or edit) the configurations and credentials for Bastion. After you have done that, save and close the file.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://bastion.gitbook.io/docs/configure/configure-bastion.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 `build a script that syncs our docs to a CMS` 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.