<https://docs.aws.amazon.com/AmazonS3/latest/userg...
# contributing
v
https://docs.aws.amazon.com/AmazonS3/latest/userguide/RequesterPaysBuckets.html - Would be an interesting and cheap (from engineering time perspective) way of offering Meltano data up that gets collected. I think this came up last office hours 🤷 (Let me know if I should put this somewhere else wasn't sure which channel)
looks like this might not work or be designed for the use case I was thinking
re
Copy code
The requester doesn't include the parameter x-amz-request-payer in the header (GET, HEAD, or POST) or as a parameter (REST) in the request (HTTP code 403).
a
I'd definitely be open to putting metrics data into a public bucket though. Generally read and egress costs are pretty low for the volume of data we'd be talking about. cc @pat_nadolny - This could make an interesting experiment for the Hub data project as discussed in #C02GH7KNPAL. Since all of those metrics are public by nature we could definitely make the whole bucket public or (perhaps more reasonaly) make the final dbt transformation outputs public.
p
yeah i think having the transformed data be public is a great idea, especially if our assumptions are correct that giving full open transparency into what were doing with the anonymous metrics will encourage more users to keep them on