亚马逊AWS CloudFront的声称没有这样的斗存在亚马逊、存在、AWS、CloudFront

由网友(習慣了孤單)分享简介:我试图建立CloudFront的服务形象,但访问它现在不工作,并返回错误指定的水桶不存在。I'm trying to set up CloudFront to serve images, but accessing it currently does not work and returns the error "T...

我试图建立CloudFront的服务形象,但访问它现在不工作,并返回错误指定的水桶不存在。

I'm trying to set up CloudFront to serve images, but accessing it currently does not work and returns the error "The specified bucket does not exist."

<Error>
    <Code>NoSuchBucket</Code>
    <Message>The specified bucket does not exist</Message>
    <BucketName>someBucketName</BucketName>
    <RequestId>irrelevant</RequestId>
    <HostId>
        irrelevant
    </HostId>
</Error>

CloudFront的要求您使用一个域来承载,而不是一个URL为基础。该域是.s3.amazonaws.com,这被认为是等同于s3.amazonaws.com/bucketName

CloudFront requires you to use a domain to host rather than a url as the base. That domain is .s3.amazonaws.com, which is supposed to be equivalent to s3.amazonaws.com/bucketName.

说,我可以通过链接直接访问内容:

That said, I'm able to access the content through the url:

https://s3.amazonaws.com/someBucketName/image.jpg

而不是通过

https://someBucketName.s3.amazonaws.com/image.jpg

返回相同的错误。任何想法,为什么发生这种情况?有什么我需要做的,使其可用的子域?同样的情况与HTTPS和HTTP。

which returns the same error. Any idea why this is happening? Is there something I need to do to make it the subdomain available? The same happens with https and http.

推荐答案

但问题是,AWS不喜欢大写字母。有与它大写字母水桶将无法从子域名访问,因为外壳丢失。

The problem was that AWS does not like capital letters. Having a bucket with capital letters in it will not be accessible from the subdomain, because the casing is lost.

阅读全文

相关推荐

最新文章