AWS re:Invent 2021 - Amazon EKS SaaS deep dive: A multi-tenant EKS SaaS solution [REPEAT]

Amazon EKS provides SaaS developers with a rich collection of constructs that can be used to compose a SaaS architecture. Navigating the mix of multi-tenant Amazon EKS patterns and strategies can be challenging. In this session, dig into a complete, end-to-end Amazon EKS SaaS reference solution, looking at how it addresses fundamental multi-tenant considerations. Examine its approach to core SaaS topics, including tenant isolation, identity, onboarding, tenant administration, and data partitioning. The goal is to explore an Amazon EKS SaaS architecture through the lens of working code and highlight the key architectural strategies that were used in this reference environment.

Subscribe:

ABOUT AWS
Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts.

AWS is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers—including the fastest-growing startups, largest enterprises, and leading government agencies—are using AWS to lower costs, become more agile, and innovate faster.

#AWS #AmazonWebServices #CloudComputing

[srirajan]

Well explained SaaS concepts for AWS, Tod, and revealing insight into tenant isolation that lies at the heart of cloud computing generally. Thank you! For future sessions, at t=38 to t=39 min, where you provide an overview of the functional scenario via conceptual tables, it would be helpful to elaborate on the functional content of the shared "Product" table and its attributes "Partition Key" and "SKU". Should not the "Product" table be look-up-only with a list of all Product IDs (or "SKUs" if that is the same?). For the non-shared "Order" tables, it's clear, since each customer has their specific order with line items of their order. Whereas for "Product", it's less clear the meaning of "Partition Key" and "SKU" (isn't this just "Product ID"?). Of course, this is all about the requirements specification, but the natural meaning of Product and its defined attributes didn't immediately follow as shown.