• tristan
    link
    fedilink
    arrow-up
    57
    arrow-down
    1
    ·
    1 month ago

    In other words, a big customer finally got effected

    • VeganCheesecake@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      18
      ·
      edit-2
      1 month ago

      Haven’t read into this too much, but I think the affected person that made this get attention was a solo dev that was prototyping a solution for one of his customers.

      And the reason he raised a stink was because he had a huge bill, as the name he chose for his bucket was by chance the same an open source project used as a sample bucket name, so whenever someone deployed it without first customising the config, it was pinging his bucket and getting a 403.

      Edit: Here’s his original medium post / Archive