1. Upon launching the AMI several scripts will run to configure the instance. By default, it is setup to listen on ports 80 for PrivateGPT and port 8080 for the identity provider (Keycloak) using the public DNS hostname provided by AWS:
2. The instance ID will be the default password for both your keyadmin and gptuser default accounts. Both should be reset to unique values. When browsing to the public DNS, you will be presented with the MDACA login page:
3. You can login with gptuser as your username and the instance ID as your password.
4. Before you can utilize the chat functionality, you must configure either an Azure Open AI deployment and key or an Open AI API key. You must login to the server using SSH. You will then run this command “sudo vi /opt/mdaca/privategpt/.env“. If you are using Auzre Open AI, you will populate: AZURE_API_KEY, AZURE_API_INSTANCE_NAME, AZURE_API_DEPLOYMENT_NAME, and AZURE_API_VERSION. If you are using the Open AI API you will populate: OPENAI_API_KEY. After saving and exiting (“:wq”), you will need to run “sudo /opt/mdaca/scripts/restart-privategpt.sh”. Once the application restarts, it should now work properly.
User management can be performed through Keycloak by logging in to http://:8080/auth using keyadmin and your instance ID as your password. Keycloak can be federated with an existing enterprise IdP, synced with LDAP, and utilize Kerberos authentication. For more information please see the Keycloak documentation here: https://www.keycloak.org/documentation
Updating the Hostname
By default, the application is setup to utilize the public DNS provided by AWS. If you would like to use an alternative hostname, you can run the following scripts: