> For the complete documentation index, see [llms.txt](https://dbi-services.gitbook.io/yak-user-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dbi-services.gitbook.io/yak-user-doc/user-interface/configuration.md).

# Configuration

The "Configuration" menu is divided into 5 sub-menus and allows the user to declare and save the following objects that will be used when declaring infrastructures and servers.

* [Secrets](#secrets)
* [Templates](#templates)
* [Provider shapes](#provider-shapes)
* [Provider images](#provider-images)
* [Artifact providers](#artifact-providers)

## Secrets

This is where the user declares and saves the credentials needed to connect to servers or cloud providers accounts.

Examples:

* AWS access key ID, secret access key and session token
* Azure client ID, secret, subscription ID, tenant
* OCI region, tenancy, user fingerprint, user ID, private key
* WinRM certificate, WinRM certificate private key (used for communication from YaK to Windows servers)
* SSH key (used for communication from YaK to Linux servers)

<figure><img src="/files/VRwDYhx8z0UDvfRO6T9p" alt=""><figcaption><p>Secrets configuration</p></figcaption></figure>

## Templates

Templates are predefined sets of values one can reuse at will in order to avoid manually setting parameters every time a new item is declared

* Component template : set of values and variables for a given component type that can be recalled when declaring a component
* Storage template : set of predefined storage values that can be recalled when declaring storage as part of a component (ex: size, mount path, filesystem...)

See [Templates](/yak-user-doc/configuration/templates.md) section for more details

<figure><img src="/files/9JsvQVfFhH0X8dwCy9r2" alt=""><figcaption><p>Templates configuration</p></figcaption></figure>

## **Provider Shapes**

Instance types at each cloud provider end.\
This menu gives an administrator the ability to have control over the types of shape users can deploy and hence keep costs under control.

Examples:

* AWS "t3.xlarge"
* Azure "Standard\_B2ms"
* OCI "VM.Standard3.Flex"
* etc

See [Provider Shapes](/yak-user-doc/configuration/shapes.md) section for more details

<figure><img src="/files/gdZKZJliEgDiv1Mj6lp2" alt=""><figcaption><p>Provider Shapes configuration</p></figcaption></figure>

## **Provider Images**

OS images on cloud provider end that are available to the user for server deployment and installation.

This allows administrators to keep control of the licenses and costs and restrict the available images to only the ones allowed by the company policy.

See [Provider Images](/yak-user-doc/configuration/images.md) section for more details

<figure><img src="/files/fuVzxu9IPrOt7ok8siOj" alt=""><figcaption><p>Provider Images configuration</p></figcaption></figure>

## **Artifact Providers**

Declares where artifacts are stored.

This menu tells the YaK which artifact provider (AWS S3 bucket, OCI bucket, Azure container) to use when installing component on your servers.

See [Artifact Provider](/yak-user-doc/configuration/manage-artifact-providers.md) section for more details

<figure><img src="/files/MzFXl5YVLcdkGkKZNyKr" alt=""><figcaption><p>Artifact Providers configuration</p></figcaption></figure>