This article provides a brief overview of the architecture and deployment process of Serverless360 private instance.
The following are necessary for successful installation of Serverless360 private instance in your Azure subscription:
Credentials of a Service principal to deploy the Serverless360 private instance.
The above-mentioned Service principal should have Contributor access to the resource group in which the Serverless360 private instance should be deployed.
The following Azure resources will be created in the customer's subscription as a part of the deployment process:
- Web App
- Function App
- Storage Account
Serverless360 provides an installer tool, from which the private instance of Serverless360 can be deployed into the customer's Azure subscription .
The first step in the deployment process is to provide the Service principal details in which the private instance need to be deployed.
- Once the Service principal is validated successfully, the user needs to select the resource group and region in which the resources should be deployed.
- The final deployment section shows the status of the ongoing steps needed to deploy the Serverless360 private instance environment.
The deployment time will most likely be around 10 minutes.
- Once the deployment is complete, a URL will be displayed, and users can begin using their Serverless360 instance by signing up after visiting the URL.