CISO Assistant Deployment using Azure App Service

[fdicarlo]

Summary of Deployment and Troubleshooting Steps for CISO Assistant on Azure

1. Deployment to Azure:

   • Cloned the CISO Assistant project from GitHub.
   • Set up an Azure Container Registry (ACR) to store Docker images.
   • Built and tagged Docker images (backend, frontend, caddy) locally.
   • Pushed the images to ACR.
   • Created an Azure App Service Plan to host the web apps.
   • Created three web apps (backend, frontend, caddy) and set them to use their respective Docker images from ACR.

2. Configured ACR Authentication:

   • Assigned system-managed identities to the web apps.
   • Granted the AcrPull role to each web app’s managed identity for pulling images from ACR.
   • Configured each web app to use the images stored in ACR.

3. Configured Environment Variables:

   • Set WEBSITES_PORT=80 for both backend and frontend apps.
   • Set an environment variable in the frontend app to point to the backend API.

4. Troubleshooting and Logs:

   • Monitored the application logs for both backend and frontend.
   • Observed that both apps were listening on a non-standard port, despite the configuration.
   • Verified app settings to ensure environment variables were correctly set.
   • Tested accessibility and communication between the frontend and backend.
   • Attempted to address any potential HTTPS, CORS, or communication issues.

Key Issues Encountered:

• Both backend and frontend apps are listening on a non-standard port rather than the expected port.
• Frontend unable to connect to the backend.

Current Status:

• Backend is running but on the incorrect port.
• Frontend is deployed but unable to establish a connection with the backend.