问题描述
由于缺乏clientaccesspolicy.xml的的，似乎有问题的Flex经由使用Amazon S3。是否有任何变通？
Due to the lack of clientaccesspolicy.xml, there appears to be problems with using Amazon S3 via Flex. Are there any work arounds?
编辑：说下面的答案是伟大的工作，我已经upvoted两者（我不打算回答分配的问题，因为它们都工作）：
Both of the below answers are great and work, I've upvoted both (I'm not going to assign an answer to the question as they both work):
http://stackoverflow.com/questions/186768/can-you-use-amazon-s3-via-flex#186889
http://stackoverflow.com/questions/186768/can-you-use-amazon-s3-via-flex#194362
推荐答案
您可以CNAME你在亚马逊S3控制一个子域（与子域的名称一桶），就像这样：
You can CNAME a subdomain you control at Amazon S3 (to a bucket with the name of the subdomain), like so:
http://s3.ceejayoz.com/ （去我的's3.ceejayoz.com桶）
http://s3.ceejayoz.com/ (goes to my 's3.ceejayoz.com' bucket)
上传自己的clientaccesspolicy.xml的文件，该叶片的根部（和设置权限为全局可见）应该做的伎俩，如果我正确理解你的问题，因为这将是在的。
Uploading your own clientaccesspolicy.xml file to the root of that bucket (and setting the permissions to be globally viewable) should do the trick, if I'm understanding your question correctly, as it will be accessible at http://s3.ceejayoz.com/clientaccesspolicy.xml.
在S3文档的更多信息：的
More information in the S3 docs: http://docs.amazonwebservices.com/AmazonS3/2006-03-01/index.html?VirtualHosting.html
编辑：从看，你也可以使用为例虚拟托管式法没有CNAME：的
edit: From looking at that, you could also use the "Example Virtual Hosted Style Method" without a CNAME: http://bucketname.s3.amazonaws.com/clientaccesspolicy.xml
这篇关于您可以通过Flex的Amazon S3吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！