In addition to configuring the routing, the onboarding process also provision a separate, siloed infrastructure resources for each tenant that continues to run the application services portion of our silo. If we look closely at the EC2 instances and databases, you’ll find there are separate instances and database that are provisioned for each tenant. We won’t dig into this too deeply. However, it’s a critical element of this model that enables our future incremental move to microservices.
Let’s take a quick look at the EC2 resources that we currently have to get a better sense of what was created. Navigate to the EC2 service in the console and select the “Instances” option from the menu on the left-hand side of the page. In this list of instances, you’ll see instances with the name “saas-factory-srvls-wrkshp-lab2-[identifier]” that represent the instances that were provisioned for your new tenant. If you onboard another tenant, you’d see more instances added here to support that tenant.