News for hackers. Stuff that matters.
Re:Shipping Multi-Tenant SaaS Using Postgres Row-Level Security by gervwyk on Tuesday July 26, 2022 @03:43PM (#32242975)
Also second this, we even split our AWS org into an AWS account per tentant. Although, this will maybe be a problem if we have +100s of clients. But it makes onboarding and off-loading simple.
Re:Shipping Multi-Tenant SaaS Using Postgres Row-Level Security by HatchedLake721 on Tuesday July 26, 2022 @05:13PM (#32244110)
It depends on an annual contract value (ACV), doesn't it? You can't give an AWS account to every $99 p/m plan, but you can for enterprise $50-100k+ deals.
Re:Shipping Multi-Tenant SaaS Using Postgres Row-Level Security by gervwyk on Tuesday July 26, 2022 @05:26PM (#32244281)
Yeah, that sums it up. I guess it means it can't be labelled as "multi-tenant" then..
Re:Shipping Multi-Tenant SaaS Using Postgres Row-Level Security by jamesfinlayson on Wednesday July 27, 2022 @01:35AM (#32247195)
Is account creation automated?

I know there are some resources where you can only have one per region (I think you can only have one AWS::EC2::VPCEndpoint per... type and service per region) but I don't know if letting multiple tenants use the same VPC endpoint is a risk or not.

Re:Shipping Multi-Tenant SaaS Using Postgres Row-Level Security by X-Istence on Wednesday July 27, 2022 @01:56AM (#32247299)
You can have an instance of a VPC Endpoint per VPC. You can have multiple VPC's all with the same VPC Endpoints.

You just get billed for them ;-)

Re:Shipping Multi-Tenant SaaS Using Postgres Row-Level Security by jamesfinlayson on Thursday July 28, 2022 @09:32PM (#32272145)
Oh yes that makes complete sense - I'm living in a world where our internal AWS management team deploys our VPCs for us (one per account unless you have very special needs).
Re:Shipping Multi-Tenant SaaS Using Postgres Row-Level Security by throw03172019 on Tuesday July 26, 2022 @04:22PM (#32243469)
Each client is running on their own instances / load balancers?