Building a serverless multi-tenant SaaS application
summary
Shows a working serverless SaaS prototype that uses Amazon Cognito + AWS Amplify for auth, a tenant onboarding flow that writes tenants to DynamoDB and creates per-tenant groups, and Lambda-backed APIs that apply a decoded token tenant_id for data partitioning. Implements a shared DynamoDB table with tenantid+productid keys and an IAM policy using a DynamoDB leading key condition so scans only return permitted items. Demonstrates per-tenant user pools for stronger isolation, and notes no universal isolation strategy.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:30Fundamental goal of multi-tenant SaaS
- 2:55Isolation strategies in SaaS
- 6:49Authentication and authorization demo
- 10:43Tenant onboarding process
- 14:21Tenant identity and context
- 20:58Applying tenant identity to services
- 22:23Multi-tenant data partitioning
- 29:22Data isolation in practice
- 39:34Key takeaways and resources
- 41:41Q&A session
related talks
28mSimplify multi-tenant microservice applications
25mLeveraging Serverless in Full-stack Development
42mBuilding Serverless Web Applications with AWS
27mBuilding the full-stack serverless app with AWS Amplify
49mServerless Architectural Patterns and Best Practices
41mYou Don’t Want to Build a Serverless Monolith
21mBuilding Fullstack applications on AWS
30mBuilding serverless applications with infrastructure as code