Closed ErinWeisbart closed 1 month ago
This is a bucket configuration issue, there's nothing that DCP should do about it; we link to how to fix it in the documentation.
We could/should probably catch it with a nicer error message, but my $0.02 is we don't want DCP messing with bucket permissions.
Man, I've been working in too many AWS accounts recently because I totally missed that it was account specific based on on the bucket configuration. I'll update it to a nicer error message and call it good. I agree that we don't wan't DCP changing permissions.