As a Premium customer with a substantial number of deployments, we need to be able to differentiate between customers’ storage requirements and bill them accordingly. Our backups are written to AWS S3 which supports per-object tags:
https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html
Adding an option to set custom per-object tags when storing a backup would allow us to quickly get an overview of data stored and cost incurred without having to manually check which trees in which buckets are associated with a contract.
This idea was posted in UpdraftPlus - backup/restore plugin and tagged cost, reporting, s3 on August 9, 2022 by 
info2351.
Hi,
Please can you explain this idea further?
Supposing that you’re doing something like storing your backups in a structure like….
s3://example.com/client1/www.website1.com/
s3://example.com/client1/www.website2.com/
s3://example.com/client1/www.website3.com/
s3://example.com/client2/www.website4.com/
s3://example.com/client2/www.website5.com/
…. etc., how would the tagging clarify the ownership any further? i.e. Since dividers are already a way of creating a hierarchy, what would be added by tagging?
David
It is not just about clarity for the human – AWS allows cost reporting based on tags. So for multiple clients, supporting tags would easily allow to generate separate cost reports automatically. Adding multiple tags would allow setting things like
On client1.example.com: { “Customer”: “client1”, “Project”: “example.com” }
On client2.example.com: { “Customer”: “client2”, “Project”: “example.com” }
On client1.com: { “Customer”: “client1”, “Project”: “client1.com” }
On client2.com: { “Customer”: “client2”, “Project”: “client2.com” }
Create cost categories Customer, Project and CustomerProject for permutations of customer and project, and you have neat and clean bills to give Client1 and Client2, itemized by the websites they use.