6,000 AWS Accounts: ProGlove's Extreme Multi-Account SaaS

The Power and Peril of Account-Per-Tenant

ProGlove's adoption of an account-per-tenant model for their SaaS platform is a bold and insightful architectural choice, particularly noteworthy for its extreme implementation at a scale of 6,000 tenant accounts managed by a small team. The article clearly articulates the substantial benefits, primarily robust isolation, simplified developer cognitive load, and transparent cost attribution, which are critical for SaaS providers aiming for agility and security. The emphasis on automation as a non-negotiable prerequisite for this model is a crucial takeaway, highlighting the shift of complexity from application logic to platform engineering. The challenges around observability and cost management at this scale are also well-addressed, emphasizing the need for centralized, intelligent solutions that avoid reintroducing the very isolation issues the model seeks to prevent. This post serves as a compelling case study for organizations grappling with multi-tenancy challenges and considering advanced AWS strategies.

However, the article could delve deeper into specific strategies for mitigating the inherent complexity in managing thousands of accounts. While AWS Organizations, SCPs, and CloudFormation StackSets are mentioned, more concrete examples of their application in automating account creation, baseline configuration, and lifecycle management would be beneficial. The discussion on observability, while acknowledging advancements in AWS services, leans heavily on third-party solutions; exploring how native AWS services could be further leveraged, perhaps through event-driven architectures or AWS Control Tower, could offer alternative perspectives. The trade-off between serverless and provisioned resources is well-explained, but a more detailed cost-benefit analysis for specific service choices in this extreme multi-account context would add significant value. The article's strength lies in its practical, experience-driven insights, but further elaboration on the 'how' behind the automation and observability could elevate it from a valuable lesson to a comprehensive blueprint.

Key Points

• ProGlove adopted an account-per-tenant model for their SaaS platform, managing 6,000 tenant accounts with a small team.
• This model provides strong isolation, simplified developer cognitive load, and transparent cost attribution, crucial for large-scale SaaS.
• Automation is a mandatory prerequisite, shifting complexity from application code to platform engineering.
• Key challenges include scalable observability across thousands of accounts and managing distributed AWS service limits.
• Serverless services are favored over provisioned resources to mitigate costs associated with idle infrastructure across numerous accounts.
• Investment in platform engineering, including scalable CI/CD and disciplined observability, is essential for success.

---

📖 Source: 6,000 AWS accounts, three people, one platform: Lessons learned