Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The specified bucket does not exist
See original GitHub issueI’m trying to download some of the existing data sets and I used the following command:
$ aws s3 sync s3://ldbc-snb.s3.amazonaws.com/ .
But got the following error:
fatal error: An error occurred (NoSuchBucket) when calling the ListObjects operation: The specified bucket does not exist
Are the files still hosted there?
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
AWS s3 api error: specified bucket does not exist
The error is stating that bucket does not yet exist. By the looks of your code, the bucket name is not correct, which...
Read more >Bucket does not exist · Issue #92 - GitHub
I have successfully built the template and every thing is in buckets. While creating cloud formation its failing to complete and following ...
Read more >Error putting object in S3 bucket example11225588 ... - Edureka
But I am getting this error. Error putting object in S3 bucket (example11225588): NoSuchBucket: The specified bucket does not exist status code: ...
Read more >“Connection Failed:...The specified bucket does not ... - Search
Article Details · Make sure that the bucket name provided under Folder path is correct and is of correct case. · Ensure that...
Read more >Amazon S3: Bucket does not exist - WordPress.org
I tried to save my backups in Amazon's S3 but I always get “ERROR: AMAZON S3 Bucket <bucket-name> does not exist“. My latest...
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
Turns out the --request-payer option was really only added to
s3apiand thes3 lscommand, but not to other subcommands likesyncfor some reason (see https://github.com/aws/aws-cli/issues/797).I posted a patch in that thread as a temporary workaround.
@shrivijaya that’s expected to be broken. Email me (address in next msg)