In our ongoing journey of designing and implementing a real-world network architecture, we’ve previously tackled the creation of a load balancer. However, the absence of web servers or backends renders our load balancer incomplete, triggering an alarm due to the lack of servers to monitor for health.
Setting the Stage for Backend Creation
To rectify this, we must delve into the creation of backend sets and their respective web servers. This task presents unique challenges, particularly within a private subnet environment where direct access to servers is restricted. Our access is limited solely to an internet gateway, necessitating an alternative approach.
Leveraging Webmaster Collaboration
A strategic approach involves collaborating with webmasters responsible for web server development. Rather than crafting server images within our restricted environment, webmasters can generate these images externally, perhaps within a testing or development environment. Once prepared, these images are made accessible to us, typically stored within an object storage bucket.
Transferring Images Across Regions
However, the location of these object storage buckets poses logistical challenges. For instance, our buckets reside not within our primary region but in an other region within the Architecture Compartment. Transferring these images across regions requires careful management, distinct from simple intra-compartment transfers.
Importing Images into Our Region
To facilitate this transfer, we employ a pre-authenticated request mechanism to obtain temporary links for image retrieval. These links must be securely stored for future use. Once obtained, we import these images into our designated region, ensuring they are available for subsequent use.
Deploying Web Servers
With our images successfully imported, we proceed to instantiate web servers within our region. Leveraging custom images, we configure compute instances named WebServer1 and WebServer2, distributed across different availability domains to enhance fault tolerance.
Integrating Servers into Backend Sets
Once instantiated, these servers are seamlessly integrated into backend sets, enabling them to serve as viable targets for our load balancer. Upon completion, our load balancer transitions from an incomplete to a pending state, signifying successful integration of backend resources.
Verifying Functionality
To validate our setup, we verify connectivity to our web servers via port 80. Additionally, we ensure appropriate security rules are in place within our public subnet, granting necessary access to port 80. With successful validation, we confirm the operational status of our load balancer and the functionality of our web servers.
Looking Ahead
As we conclude this segment of our network architecture implementation, we anticipate further advancements. In our next lesson, we will embark on the creation of another virtual cloud network using a wizard, culminating in the integration of a database cloud system. Join us as we continue to expand and refine our real-world network architecture.