Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Download Roost Installation Script

    Code Block
    cd /var/tmp/Roost
    curl -L https://remote-roostprod.s3.us-west-1.amazonaws.com/roost-enterprise.sh -o roost-enterprise.sh
    chmod +x roost-enterprise.sh

  2. Download config.json

    Code Block
    curl -L https://remote-roostprod.s3.us-west-1.amazonaws.com/main-config.json -o config.json

    Sample Config looks like the below

    1. Replace the values to reflect for your organisation

    2. Keep values empty of the client_id/secrets for the 3rd party that is not needed

    3. Keep ENV_DATABASE detail unchanged if database is not external

    4. Add JWT_SECRET

    5. Recommend value of remote_console_proxy is same as enterprise_dns unless you want to start proxy elsewhere.

    6. If your servers are behind Load Balancer user load_balancer : “true” for different configuration.

    Code Block
    {
      "enterprise_name": "MyCompany",
      "enterprise_logo": "https://roost.ai/hubfs/logos/LOGO-roost.png",
      "enterprise_email_domain": "mycompany.io",
      "enterprise_dns": "mycompany.io",
      "remote_console_proxy": "mycompany.io",
      "admin_email": "admin@mycompany.io",
      "email_sender": "noreply@mycompany.io",
      "email_sender_pass": "",
      "email_smtp_host": "",
      "email_smtp_port" : 465,
    
      "load_balancer": "false",
    
      "enterprise_ssl_certificate_path": "/var/tmp/Roost/certs/server.cer",
      "enterprise_ssl_certificate_key_path": "/var/tmp/Roost/certs/server.key",
    
      "ENV_SERVER": {
        "DEFAULT_PORT": 3000,
        "JWT_SECRET": "32-character-secure-long-secret",
    
        "GOOGLE_CLIENT_ID": "",
        "GOOGLE_CLIENT_SECRET": "",
        "AZURE_CLIENT_ID": "",
        "AZURE_CLIENT_SECRET": "",
        "GITHUB_CLIENT_ID": "",
        "GITHUB_CLIENT_SECRET": "",
        "LINKEDIN_CLIENT_ID": "",
        "LINKEDIN_CLIENT_SECRET": "",
        "OKTA_CLIENT_ISSUER": "",
        "OKTA_CLIENT_ID": "",
        "OKTA_CLIENT_SECRET": ""
      },
    
      "is_own_sql": "false",
      "ENV_DATABASE": {
        "MYSQL_HOST": "mysqldb_host_url",
        "MYSQL_PORT": 3306,
    
        "MYSQL_USERNAME": "Roost",
        "MYSQL_PASSWORD": "Roost#123",
        "MYSQL_ROOT_PASSWORD": "Admin#123"
      }
    }


  3. Start Roost Control Plane Server

    Code Block
    cd /var/tmp/Roost
    ./roost-enterprise.sh -i all -c config.json 

  4. Verifying the Roost.ai components

    1. Connect to the <dns-name>/login using a browser

    2. Use the 3rd party auth to connect to the control-plane

  5. Next Steps:

    Go to Admin Settings and

    1. Enable cloud vendor of choice and provide default settings

    2. Add the Roost EAAS Server EC2 details in the “Configure EAAS Server”

    3. Enable JumpHost and refresh the page

    4. Go to JumpHost settings and add the Roost EAAS Server EC2 details as 'default' jumpHost

<< Previous >> Next Next>>