AWS 和 AWS Silverlight 你有任何现场笔记吗
我有兴趣了解 AWS（亚马逊 Web 服务）及其作为 Siverlight 应用程序后端的可行性。 最初我对使用 S3 和 SimpleDB 来存储和管理媒体库感兴趣。
在开始之前，我会尝试找出困难的峰值。 是身份验证、Rest 与 Soap、跨域策略还是完全不同的东西。
您在使用 AWS 时遇到的痛点是什么 --- 特别是但不仅限于 Silverlight2
I'm interested in getting my head around AWS (amazon web services) and its viability as a back end for Siverlight applications. Initially I'm interested in using S3 and SimpleDB to store and manage a media library.
Before I start I'm trying to identify the spikes in difficulty. Is it authentication, rest vs soap, cross domain policy, or something totally other.
What are your pain points in working with AWS --- particularly but not exclusively from Silverlight2
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
有必要代理您的 SimpleDB 调用，因为出于安全原因，AWS 拒绝在 sdb.amazonaws.com 上发布跨域策略。 将您的 AWS 密钥公开加载到用户的浏览器中并不安全。 如果您将其托管在 EC2 上，那么您的实例代理 SimpleDB 调用应该不成问题。
使用 REST 或 SOAP，哪个更容易。 那里你不会感到任何疼痛。
It will be necessary to proxy your SimpleDB calls because AWS refuses to publish a cross domain policy on sdb.amazonaws.com for security reasons. It's not safe to load your AWS secret key publicly into the user's browser. If you are hosting it on EC2 then it shouldn't be a problem for your instance to proxy SimpleDB calls.
Use either REST or SOAP, which ever is easier. You won't find any pain there.
我唯一真正的痛点是 Amazon EC2 服务器都位于 NAT 之后。
就 Web 应用程序而言，使用 NAT 并不是真正的问题，事实上，动态分配公共弹性 IP 的能力是一个好处。 就我而言，我的应用程序是基于 SIP 的应用程序，需要将公共 IP 地址放在 SIP 标头中，而 NAT 处理起来很烦人。
我有一个 silverlight 应用程序托管在 Amazon EC2 服务器上的 IIS 实例上，它工作正常，没有任何问题。 我确实使用跨域策略文件和自定义身份验证机制，在这两种情况下它都与普通 Windows 服务器相同。
我没有使用过 SimpleDB，所以无法对其发表评论，但如果您正在考虑托管媒体库，我怀疑弹性块服务 (EBS) 就是您所追求的。 有时，我在让 Windows 服务器识别 EBS 驱动器时遇到一些困难，并且不得不使用 Windows 磁盘管理器来识别该驱动器，但一旦完成，它就可以完美工作，并且与任何普通 Windows 驱动器相同，只是您可以扩展高达 tera 或 pera 字节。
The only real pain point I have is the fact that the Amazon EC2 servers are all behind a NAT.
As far as web applications are concerned the use of NAT is not really a problem and in fact the ability to dynamically assign the public elastic IP's is a benefit. In my case my application is a SIP based one that needs to place the public IP address in the SIP header and NAT is annoying to cope with.
I have a silverlight application hosted on an IIS instance on a Amazon EC2 server and it works fine, no issues. I do use a cross domain policy file and a custom authentication mechanism and In both cases it's just the same as a normal Windows server.
I haven't used the SimpleDB so can't comment on it but if you're looking at hosting a media library I suspect the Elastic Block Service (EBS) is what you're after. I have sometimes had a few difficulties getting my Windows server to recognise an EBS drive and have had to use the Windows Disk Manager to recognise the drive but once that's done it works perfectly and is the same as any normal Windows drive except that you can scale it up to tera or pera bytes.