• BlackEco@lemmy.blackeco.comOP
      link
      fedilink
      arrow-up
      57
      arrow-down
      1
      ·
      edit-2
      13 days ago

      From what a gathered, it was the classic misconfigured AWS S3 Bucket. It’s criminal how AWS still makes the default configuration insecure.

      Edit: apparently buckets are private by default now, haven’t set up S3 in a while.

      • grue@lemmy.world
        link
        fedilink
        English
        arrow-up
        30
        ·
        13 days ago

        It was also the classic “collecting the information to begin with,” and it’s criminal how that is allowed, too.

      • rumba@lemmy.zip
        link
        fedilink
        English
        arrow-up
        7
        ·
        13 days ago

        It doesn’t default insecure anymore and it bitches at you when you try to make it public.

        My bet would be that It was either a pre-existing bucket, or some team put a “temporary” measure in (making it public) instead of using the API to pull the data until they got around to implementing it correctly.