-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS Amplify Storage #13065
Comments
Hi @cwomack , |
Hi @saharJ95 thank you for opening this issue. I see that you are console logging the |
Hi @nadetastic , Thank you for your response. I fixed the issue by adding an S3 object in the amplify configuration. |
One more thing i want to know how we can upload files in multiple buckets ? @nadetastic |
@saharJ95 glad to hear that you were unblocked. As for your follow up question, Amplify doesn't currently support multiple buckets, and we are tracking this as a feature request on this github issue - aws-amplify/amplify-cli#5836 - feel free to subscribe and follow to the issue for whenever we have future updates. There may also be some workarounds in the comments that could work for you. |
Before opening, please confirm:
JavaScript Framework
React, Next.js
Amplify APIs
Storage
Amplify Version
v6
Amplify Categories
storage
Backend
None
Environment information
Production and Development
Describe the bug
Unable to access bucket which is already described in Configuration. I am getting missing bucket name issue
Can You please Identify if there is anything wrong with config things?
Expected behavior
Upload images in multiple bucket
Reproduction steps
Configure Storage (s3 bucket) in Amplify
Upload Data in respective buckets
Code Snippet
This is Amplify.getConfig() result

Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: