3 ms·
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 on
by gervwyk 4y ago
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.
- HatchedLake721 4y agoIt 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.
- gervwyk 4y agoYeah, that sums it up. I guess it means it can't be labelled as "multi-tenant" then..
- throw03172019 4y agoEach client is running on their own instances / load balancers?
- jamesfinlayson 4y agoIs 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.
- X-Istence 4y agoYou 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 ;-)
- jamesfinlayson 4y agoOh 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).