Set custom prefix for Storage uploads, target root of the bucket instead-of folders namespaced by accessLevel?
See original GitHub issueFor all the uploads performed by the code below, my files are put in a public/
folder. Are these prefixes hardcoded in the library based on access levels? If public is the default access level, is there any way I can set a custom prefix for these values, so that I can put my files in root of the bucket instead of public/
?
Amplify.Storage.uploadFile(key, image, options,
{ progress -> uploadProgress(progress) },
{ result -> uploadSuccess(result)},
{ error -> uploadError(error) }
)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Difference between prefixes and nested folders in Amazon S3
A key prefix is a string of characters that can be the complete path in front of the object name (including the bucket...
Read more >Advanced configuration - GitLab Docs
Absolute path to a directory where build caches are stored in context of selected executor. For example, locally, Docker, or SSH. If the...
Read more >Object Gateway Guide Red Hat Ceph Storage 5
This document provides guidance on deploying, configuring, and administering a Ceph Object Gateway environment. This guide uses a "Day Zero", "Day One", ...
Read more >Backup and restore - Percona Operator for MongoDB
If prefix is not set, backups are stored in the root directory. The options within these three subsections are further explained in the...
Read more >List the objects in a bucket using a prefix filter | Cloud Storage
<summary> /// Prefixes and delimiters can be used to emulate directory listings. /// Prefixes can be used to filter objects starting with prefix....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I started migrating to Amplify when i realised that it doesn’t allow bucket configuration upon upload (just like TransferUtility). Why would you limit this, it’s a big deal breaker.
any updates on this? I also want to upload images and files to specific bucket folders like
/profileImages
and/classnotes
.