I created a bucket on Amazon S3 and went to the url (which is a url I need to put in an initializer in my rails app)
https://mtest73.s3.amazonaws.com/
and got this message
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>NoSuchBucket</Code>
<Message>The specified bucket does not exist</Message>
<BucketName>mtest73</BucketName>
<RequestId>9FBDCC50303F4306</RequestId>
<HostId>
owG6PSSjvcS7QZwEMKzTjMnYiwclXkRG7QGIF/Ly+jc8mHnmbvWHXqitDzfjnzgM
</HostId>
</Error>
However, in the Amazon console i've even uploaded a small file to this bucket.
Is there a reason for this? I thought it might be saying the bucket doesn't exist due to security reasons, but if there's something I've done wrong it might be why I can't get my Rails application to work...
#JohnFlatness and #pjotr pointed out, I wrote the wrong url
https://mtest73.s3.amazonaws.com/
It should have been
https://73mtest.s3.amazonaws.com/
Related
When I upload files to s3 from my hosted environment, everything works. I can see the file in the bucket, and when I look at the Server-side Encryption settings on that file it looks like this:
I can also successfully visit the file via its Object URL.
When I upload files from my local environment, I can still see the files in the bucket, but they have this error in Server-side encryption settings:
When I visit the Object URL for these files it comes back with XML saying 'Access Denied'
Anyone encountered this error before?
I'm running a SageMaker Training Job with a custom algorithm and the input data from s3. The SagaMaker AIM role ARN has a Read/Put policy on the specified S3 bucket folder, but while creating the job I get a client error:
ClientError: Data download failed:NoSuchKey (404): The specified key does not exist.
Unfortunately no more error info is provided in the SageMaker dashboard to investigate further.
SageMaker team member here.
The problem here is that the training job in question was setup with S3DataType=ManifestFile. In this case SageMaker expects to be able to download a single manifest file from the location specified by the S3Uri, if the file does not exist in S3 we get a 404 which is what we're sending back as the error here.
See here for documentation on S3DataType/S3Uri and manifests: https://docs.aws.amazon.com/sagemaker/latest/dg/API_S3DataSource.html#SageMaker-Type-S3DataSource-S3DataType
We will work to make this error message a bit more user-friendly, thanks for calling this out!
To upload files to S3, I'm following the tutorial at http://blog.fineuploader.com/2014/01/15/uploads-without-any-server-code/
I got the first few errors out of the way, but i'm stuck at this one.
Failed to load resource: The certificate for this server is invalid.
You might be connecting to a server that is pretending to be
“videoupload.mobdesignapps.fr.s3.amazonaws.com” which could put your
confidential information at risk.
I'm hosting the site on S3 and need to upload files to another S3 buckets.
Any clue appreciated
Found the answer in this question: Amazon S3 Bucket naming convention causes conflict with certificate
Essentially bucket name need to not contain any period (".") to work with the default S3 SSL certificate.
I am using Cloudfront to serve assets stored in s3. Most of the files work fine, but some do not, specifically my fonts.
I am completely stumped as to why:
https://xxxxxx.cloudfront.net/assets/application-xxxxxxx.js
returns fine, but
https://xxxxxx.cloudfront.net/assets/fontawesome-webfont.woff?v=3.1.0
returns:
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>xxxxxx</RequestId>
<HostId>xxxxxx</HostId>
</Error>
Does anyone know why this is? I suspect it has to do with CORS, but I am using the CORS specified in this answer. And the request is getting returned as forbidden on all browsers, not just firefox.
Any help would be greatly appreciated.
After you fix your S3 permissions, you then need to invalidate CloudFront's cache of error messages from that URL.
Or wait 24 hours. Whichever.
When you invalidate the cache you can't just update the assets. I had to create a whole new cloudfront distribution package.
I'd suggest doing that. Create a new cloudfront asset package, point your server to that and delete your old one.
I have created an Amazon S3 account and trying to upload some files with S3fox add-on.
I have added S3fox and logged in with my accesskey and secure id credentials.
Now, i created a bucket by right clicking and selecting create a directory and selected the option to put the bucket in europe. Now when i try to drill down into my folder, i keep getting an error message saying "Error connecting! - Temporary Redirect". And also i can not transfer any files.
but if i create the bucket without selecting the option to put it into europe, then i am able to drill down into the bucket.
I would like my bucket to be in europe as i am from UK. Please suggest what i am missing and how can i resolve this issue?
Thanks
Sreekanth
I have the same problem - it still doesn't work after an hour. To save waiting I've installed Cloudberry (freeware for Windows), which seems to be a better alternative anyway (it looks more user-friendly and has more options): http://www.cloudberrylab.com/free-amazon-s3-explorer-cloudfront-IAM.aspx