As part of the post-installation process, consider reviewing your RaaS configurations. RaaS, which stands for Returner as a Service, is the central component in Automation Config. RaaS provides RPC endpoints to receive management commands from the Automation Config user interface, as well as RPC control endpoints to interface with connected Salt masters. The RaaS configuration settings are in the /etc/raas/raas configuration file on the RaaS node.

Before you start

Configuring the RaaS node is one post-installation step in a series of several steps that should be followed in a specific order. First, complete one of the installation scenarios and then read the following post-installation pages:

Check configuration settings

  1. Open the RaaS configuration file on the RaaS node. By default, it is usually stored in /etc/raas/raas.
  2. Check the following required settings:
    Setting Description
    customer_id Your customer ID, or sample UUID.
    sql

    username, password, host, and port can be configured to match your database configuration. For more on storing credentials securely, see the Securing credentials in your Automation Config configuration knowledge base article.

  3. Check the following additional settings:
    Setting Description
    tls_minumum Sets the minimum TLS version that RaaS accepts. By default, this property is set to 1.2. You can change this setting to a lower version number if needed. However, using a version lower than 1.2 is not recommended because of security issues in earlier versions.
    tls_crt Path to the crt file for encrypted communication. If this certificate is self-signed and should not be validated using a known CA, be sure to set the sseapi_validate_cert option to False in the Salt master configuration file.
    tls_key Certificate key file.
    port Port that is used for connections from the Automation Config user interface and Salt controllers.
    audit Include the API (RaaS) information in the Debug report for administrator accounts. If valid_logins is set to True, this information is also included in bug reports that are generated by non-admin users.
    raas_presence_expiration Seconds of inactivity before a minion is considered not present. Default is 3600 seconds (one hour).
    target_grou[s_from_master_pnly Set to true if the tgtmatch engine is enabled on your salt-masters, false otherwise.

Default RaaS configuration file

To generate the default RaaS configuration file, run this command: 
raas genconfig /tmp/raas-config

This prompts the RaaS node to generate raas-config. Explanations for each configuration setting are provided by in-line comments in the file.

What to do next

After configuring the RaaS node, you must complete additional post-installation steps. The next step is to log in to the Automation Config user interface for the first time. To continue the post-installation process, see Log in for the first time and change default credentials.