GRAFANA LOKI AND UNINTENDED AWS DATA WRITE ATTEMPTS TO AMAZON S3 BUCKETS

Summary from the TLDR InfoSec newsletter

Grafana has announced that the “unnamed open source project” cited in the “How an empty S3 bucket can make your AWS bill explode” medium post was Grafana Loki. The author of the post used the same name as the default bucket in the Loki Helm chart when he was setting up the S3 bucket for his Loki installation, leading to other Loki clusters deployed using the default configuration to attempt writes to his bucket. Helm charts have been updated to not include default names unless using local storage. AWS also announced changes to S3 billing due to this bug.