3 ms·

The limits on tenants are soft limits and should be extendable by reaching out to them.

• treeman79 6y ago
  Responses have ranged from, your doing it wrong to “no” At one point we had a dozen different Amazon accounts to keep everything separate. Thankfully the business model was crap, so if resolved itself.
  • sirkarthik 6y ago
    LoL, for the way you finished your point. Good to know your experience :) Did Amazon mere said, "you are doing it wrong", without an explanation? In retrospective, do you think you could have done better? I'm looking to hear the lessons you learned, so may be, I don't end up making that mistake ;)
    • treeman79 6y ago
      For dynamodb it was “you need to rethink your data structure” S3, I think they did up the bucket limit on request, but maxed out at 1,000. That was years ago though.
      • dkersten 6y ago
        I guess the way they want you to do it in S3 is using a per tenant key prefix with security policy set? AWS roles and security policies are quite flexible so I guess in theory you would get the desired isolation that way. Separate buckets are still easier, though...
  • zzzeek 6y ago
    Self-destructing business model is the most effective scalability strategy for developers by far. Just make sure you do net 30.