• BlackEco@lemmy.blackeco.comOP
    link
    fedilink
    arrow-up
    4
    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
      5
      ·
      13 days ago

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

    • CosmicTurtle0@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      5
      ·
      13 days ago

      The default for net new buckets is actually very strict.

      But it’s that strictness that makes devs just to open it up to everyone and not learn proper IAM syntax.

      The unfortunate part is that AWS made rules and privileges so nuanced and detailed that it makes people want to make everything public and deal with it “later”.

      • drspod@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        13 days ago

        How do people end up finding them? Don’t they have random UUIDs in the URL? Or are they predictable?