EricZimmerman / EricZimmerman/KapeFiles

Cannot upload data to GCS buckets that are using uniform bucket-level access

Open
#935 0 comments 0 reactions 1 assignee Claimed by @EricZimmerman View on GitHub
bug
Dominant language
No language data
Stars
874
Forks
234
Avg merge
1h 46m
Merged PRs (30d)
10

Description

**KAPE version**
1.3.0.2

**Describe the bug**
I am trying to upload data to a Google Cloud Storage bucket, using aws credentials. The "aws" CLI works perfectly well, but when I try using kape for uploading data, I receive an error: "Cannot insert legacy ACL for an object when uniform bucket-level access is enabled".
The command line: `--tsource C:\Users\USERNAME\Downloads --tdest C:\temp --tflush --target !BasicCollection --s3r europe-west1 --s3p spGoogleStorage --s3b storage-bucket-1 --s3k XXXXXXXXX --s3s XXXXXXXXX --zip downloads --gui`

Full text of the error message:
```
Using Target operations
Validating connectivity to S3: europe-west1/storage-bucket-1...
Error validating S3 information! Exiting!! Error: InvalidArgument: Invalid argument. (Details: Cannot insert legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access)
```

**To Reproduce**
Steps to reproduce the behavior:
1. Configure GCS bucket with enforced UBLA access, generate HMAC credentials.
2. Try uploading data to the GCS bucket

**Expected behavior**
KAPE should be able to upload data without any issues.

**Additional context**
[Uniform bucket-level access](https://cloud.google.com/storage/docs/uniform-bucket-level-access) is a recommended option in GCS now and some organizations are using guardrails, disabling usage of ACL and enforcing using UBLA.

I presume that you might not have a GCS bucket at hand. Please let me know and I will be happy to help you troubleshooting the issue in my environment.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.