- We currently use one S3 bucket for each client. We have about 70 buckets in use. Amazon limits accounts to 100 buckets. Is there a need to use separate buckets for each client? Can we just create another S3 account?
- As I understand it, the reason we've used a bucket for each client in the past has been so we could keep track of how much bandwidth each client uses. I don't know if this anybody has done this or currently does this, but as we run up against our hundred-bucket limit, we'll need an alternative.
- The way forward is probably to create a bucket for each environment (local dev, development, qa, staging, & prodction). Actually, we'll likely want to have a 'draft' bucket for each of those environments to hold pre-publication assets. Alternatively there could be a 'drafts' folder in each bucket instead of creating a whole separate bucket.
- If we do implement 'drafts' feature, we'll have to add some workflow functiona