Configuration
Last updated
Last updated
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.
This is where the user declares and saves the credentials needed to connect 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)
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 section for more details
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 section for more details
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 section for more details
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 section for more details
