agree, while AWS added a bunch of tooling around this, is it still entirely to easy to accidental or lazily make a bucket public. I honestly think they should c

agree, while AWS added a bunch of tooling around this, is it still entirely to easy to accidental or lazily make a bucket public. I honestly think they should consider splitting S3 into S3 public and S3 private independent services. Buckets in S3 private cannot be made public unless migrated to S3 public.