Remove private ACLs for buckets (#104)

AWS has changed the behavior of bucket ACLs and is essentially
deprecating the feature.

In general, we don't need to set these ACLs as private is the default
anyway, so removing this is a non-breaking changing for existing
deployments and fixes new deployments with the recent change to behavior
for new buckets

tiered_storage.tf

@@ -23,11 +23,6 @@ resource "aws_s3_bucket" "tiered_storage" {
   }
 }
 
-resource "aws_s3_bucket_acl" "tiered_storage" {
-  bucket = aws_s3_bucket.tiered_storage.id
-  acl    = "private"
-}
-
 resource "aws_s3_bucket_server_side_encryption_configuration" "tiered_storage" {
   bucket = aws_s3_bucket.tiered_storage.bucket
   rule {

velero.tf

@@ -23,11 +23,6 @@ resource "aws_s3_bucket" "velero" {
   }
 }
 
-resource "aws_s3_bucket_acl" "velero" {
-  bucket = aws_s3_bucket.velero.id
-  acl    = "private"
-}
-
 resource "aws_s3_bucket_server_side_encryption_configuration" "velero" {
   bucket = aws_s3_bucket.velero.bucket
 
@@ -207,4 +202,4 @@ resource "kubernetes_namespace" "velero" {
   metadata {
     name = var.velero_namespace
   }
-}
+}