Deployment Overview
Last updated
Last updated
Sunbird ED is a cloud-agnostic platform that can be deployed on a variety of cloud platforms, including Azure, Amazon Web Services (AWS), Google Cloud Platform (GCP) and OCI. The most common deployment architecture is to use a cloud-based platform, as it offers a number of advantages, such as scalability, reliability, and maintainability.
Following diagram depicts the high-level deployment architecture of SunbirdEd platform.
The ideal network configuration depends on the quantity of environments you wish to establish. It is advisable to create a corresponding number of virtual cloud networks, each paired with an administrative virtual network. Within each virtual network, there should be a robust bastion host dedicated to SSH access and a CI slave responsible for code deployment. The administrative virtual network, on the other hand, serves as the central hub for essential utility services, including the CI master server and VPN server etc.
Within each virtual network in every environment, there are several distinct subnets, each assigned specific roles for hosting various types of workloads. These roles typically include administrative tasks, containerised and non-containerised applications, and data workloads. To ensure the secure flow of data, the ingress and egress of data between subnets and servers are meticulously controlled by implementing network security groups.
Note: Azure cloud specific resource icons are used in the above diagrams for representation purpose only. However the equivalent resource/service can be used in the other cloud service providers based on your choice