<p>I’m looking at EKS architecture patterns for a saas multi tenant saas application and found some great resources in the AWS saas factory space. However, I have couple of questions that that I couldn’t find answers for in those resources:</p>
<p>The proposed application will broadly have following components:</p>
<ol>
<li>Landing and Tenant Registration App (React SPA)</li>
<li>Admin UI To Manage tenants (React SPA)</li>
<li>Application UI (the product - React)</li>
<li>Core/Support Micro-services (Lambda)</li>
<li>Tenant App Micro-services(Go/Java)</li>
<li>RDS - Postgres per tenant</li>
</ol>
<p>I’m currently leaning towards <strong>EKS with Fargate</strong> where namespaces used for tenant isolation.</p>
<p><strong>Questions:</strong></p>
<ol>
<li><p>Is the namespaces right way to go about for tenant separation (as opposed to separate cluster/vpc per tenant)</p>
</li>
<li><p>Regarding tenant data (RDS) isolation, if I go with namespaces isolation, what’s the best way to go about it?</p>
</li>
</ol>
<p>Apologies of the question isn’t clear, happy to provide further clarification of needed.</p>

sheeni
<p>Question 1: Could you please let me know if AWS global Accelator has capability to route the request to different ALB based on dns(base url)?</p>
<p>Answer: Unfortunately Global Accelerator does not have the ability to do smart routing based on URL.</p>
<p>Question 2: Do we require multiple AWS accelator for each customer?</p>
<p>Answer: That is correct.</p>
<p>Question 3: Do we have any other solution to access the application in-isolation for each customer?</p>
<p>Answer: Not in isolation it is possible to use one ALB with host header rules for your listeners. Each rule going to its own target group. This way you will control traffic by making a target group for each customer. However it does not fullfill your isolation requirement.</p>
<p>Question 4: Do you suggest to have different pods for each customer with routing the request to various target group based on path?</p>
<p>Answer: Yes that is the option I mentioned above you can use path based or host header option depending on the URL. If the URL's are completely different then host header if the URL is just different paths then path based would be best.</p>
<p>hope these answer help you to resolve @sheeni's queries.</p>
