问题描述
我改名为亚马逊S3存储来自：多字名
I renamed an Amazon S3 Bucket from:"multi-word-name"
什么亚马逊建议作为最好的命名约定：multi.word.name
to what Amazon suggests as being the best naming convention:"multi.word.name"
的问题是，这会导致与SSL证书的一个问题：您尝试访问multi.word.name.s3.amazonaws.com，而是你居然达到一台服务器是标识为* .s3.amazonaws.com ......
The problem is that this causes a problem with the SSL certificate:"You attempted to reach multi.word.name.s3.amazonaws.com, but instead you actually reached a server identifying itself as *.s3.amazonaws.com ..."
任何想法？
感谢
推荐答案
有涉及桶命名中的。
首先，有下的地方记录警告仍就建议DNS兼容的桶名称约定一个巨大而严重，看到的虚拟主机：
First and foremost, there is a huge and severely under documented caveat in place still regarding the suggested DNS compliant bucket name convention, see Virtual Hosting of Buckets:
当使用虚拟托管式的水桶使用SSL，的SSL通配符证书只匹配水桶不包含句。要解决此问题，使用HTTP或写自己的证书验证逻辑。 [重点煤矿] 的
- 所以从这个角度看您想要的方式是行不通的 - 这个问题的探讨更详细的克里的回答亚马逊S3 - HTTPS / SSL - 是否有可能，其特点就从 AWS这个问题的一个专门的答案吗？支持为好。
- So from this perspective your desired approach simply won't work - this problem is explored in more detail in Kerry's answer to Amazon S3 - HTTPS/SSL - Is it possible?, which features a dedicated answer regarding this problem from AWS Support as well.
如果你问周围的 AWS的Java SDK 上下文/范围，则可能要与新的 AWS的Java SDK 1.4.0 ，该功能相关的重试更改S3主机名SSL验证的：
In case you are asking from a context/scope around the AWS SDK for Java, you might want to try again with the new AWS SDK for Java 1.4.0, which features related Changes to S3 host name SSL verification:
验证主机名时，使用DNS样式桶寻址（默认值）时，Amazon S3的客户端现在已经不那么严格。 现在s3.amazonaws.com结尾的域名将绕过严格的SSL检查的要求。这一变化解决客户在使用水桶在名称中使用时段非美地区经历的问题。 [重点煤矿] 的
请注意，这种变化已被释放就在昨天，我还没有探索无论其背景或它关系到上述通用的限制还没有，但它可能会帮助你对你的方式。
Please note that this change has been released just yesterday and I haven't explored either its background or its relation to the aforementioned generic restriction yet, but it might help you on your way.
祝你好运！
这篇关于亚马逊S3存储的命名规则导致与证书冲突的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！