S3 transfers lose object permissions and tagging intent
Cloud and DevOps teams wanted S3 copy and sync workflows to preserve per-object ACLs and apply tags, including to multipart uploads. The signals describe two related gaps in managing object attributes during bulk transfers; they also show that scripting per-object permissions was considered difficult. These requests date from 2014–2017, so current CLI behavior and remaining demand need to be verified before building.
For cloud administrators and DevOps engineers managing S3 buckets. Mentioned from Aug 2014 to Jun 2017 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.4/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
This feature is really a must have of a sync mechanism, particularly when you have thousands of files with different permissions and want a true sync across buckets not just a copy of files. Do you know of another way to get permissions on a per file basis, so I can script this easily enough?
I would expect the files in bucket2 to have the same permissions as the files in bucket1 by default as it is a "sync" Instead they only have the default permissions
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 5 more quotes from people who have this problem
- Current workarounds, existing solutions and risks