document minimum required allowed actions in S3 policy
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
https://guides.dataverse.org/en/latest/installation/config.html describes AWS S3 configuration, but doesn't enumerate necessary bucket permissions. We've been running with
"s3:PutObject",
"s3:GetObject",
"s3:DeleteObject",
"s3:PutObjectTagging",
"s3:GetObjectTagging",
"s3:DeleteObjectTagging"
but apparently have been getting permission denied warnings on GetBucketAcl since mid-January 2022.
Propose the addition of a minimum bucket permission policy suitable for the average Dataverse installation using S3 storage.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the AWS S3 configuration section at guides.dataverse.org/en/latest/installation/config.html and review the listed object permissions alongside the reported GetBucketAcl warning. Document a minimum bucket policy for an average Dataverse S3 installation, including the required actions, and make clear that the configuration covers the reported permission issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100