• dejected_warp_core@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    7 months ago

    What kills me about S3 is that the use cases for publicly accessing S3 contents over HTTP have got to be vanishingly small compared to every other use of the service. I appreciate there’s legacy baggage here but I seriously wonder why Amazon hasn’t retired public S3 and launched a distinct service or control for this that’s harder to screw up.

    • capital@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      7 months ago

      Public access is disabled by default and it warns you when you enable it. How much more idiot proof does it need to be?

      • dejected_warp_core@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        Honestly, I’m for removing the option and moving that “feature” somewhere else in AWS entirely. And those warnings aren’t really a thing when using IaC. Right now it’s still a “click here for self harm” button, even with the idiot proofing around it.