How to use Multi-Tenant Architecture when your client has their own AWS account
But what if your client already has an AWS account and they want your product’s infrastructure to live in their infrastructure?
In this scenario, perhaps you have an AI/ML workload or a proprietary DB that they want hosted inside their VPC to have maximum control over data access.
You could absolutely create the ultimate MTA and design it so your product’s server infrastructure could be provisioned in a customer’s existing AWS account.
In this scenario, the customer would still rely on you to fine-tune the provisioned infrastructure and monitor it to ensure maximum uptime, so you would have continued access.
The customer would just get the peace of mind that they have complete visibility to the underlying infrastructure, what/who has access to the hardware, and complete control over their valuable proprietary data.
Does it seem extreme? If you are playing in the big leagues, this isn’t extreme at all.
Now there are a million little details you will need to consider when designing a system like this, and if you want some help with that, you should check out the Schematical Group Coaching Community, where I help people like you design systems like this that will scale up in a cost-effective way.