one thing I’m really missing is better tenanting – seems like if I want to deploy this for customers I’d have to deploy a unique instance and bucket for each of them. and even then, the permissioning is very wide.

separate bucket for each tenant sounds like a good idea?

sure, but they require separate instances - and for a single tenant, they may require multiple buckets

yeah, guess, multi-tenant could also be handy to support different regions for the same environment (e.g. staging-nam, staging-pacific etc)

We considered this approach for our cloud. But I remember the number of buckets you can create on AWS is limited so tenant-per-bucket doesn't scale well when you are going to have a lot of tenants.

its moreso that as of now I need unique compute per tenant - instead of sharing compute for all tenants. and all tenants require at minimum some compute running at all times to be available before scaling up