在 Amazon SimpleDB 中重命名和/或复制域
我的客户决定更改项目名称，并要求我更改 SimpleDB 中的域名。我找不到任何方法、服务、API 调用或工具来让我做到这一点。我尝试使用适用于 Eclipse 的 AWS 工具以及其他一些第三方工具。
它们最多允许您删除域或将其内容导出到数据文件。没有导入功能。
我的问题：
- 有没有一种简单的方法来重命名域名？
- 如果做不到这一点，是否有一种简单的方法将内容从一个域复制到另一个域？如果是这样，我就复制到新的并删除旧的。
- 失败2，是否有人有任何现成的代码（最好是PHP）来手动将逐条记录从一个域复制到另一个域？
感谢您的帮助。
My client decided to change the name of the project and requires that I change the domain names in our SimpleDB. I could not find any way, service, API call or tool to allow me to do that. I tried using the AWS tools for Eclipse as well as some other 3rd party tools.
At most, they allow you to delete a domain or export its contents to a data file. There's no import functionality.
My question/s:
- Is there an easy way to rename a domain?
- Failing that, is there an easy way to copy contents from one domain to another? If so, I'll just copy to the new one and delete the old one.
- Failing 2, does someone have any ready-made code (preferably in PHP) to manually copy record-by-record from one domain to another?
Thanks for your help.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
SdbNavigator 可让您导出和导入数据（JSON 格式）。您可以从域 A 导出并导入到域 B。
SdbNavigator lets you export and import data (in JSON format). You could export from domain A and import into domain B.
无法重命名域名，如果必须更改域名，您唯一的办法就是手动复制数据；没有自动或 API 方法来制作副本。
您可以使用在线网络服务 SimpleBackr 或 BackupSDB 备份域名并恢复到不同的域名。我不确定这两种服务都支持恢复到不同的域名，但我确实认识运行这两个站点的人，他们在支持其服务时非常乐于助人且反应灵敏。
每当临时提供您的 AWS 密钥时，即使是向受信任的个人提供，我始终建议您在 AWS 账户网站中生成第二个密钥并将其提供。临时使用完成后，您可以删除第二个密钥，并且应用程序使用的现有密钥仍然有效且保密。
There is no way to rename a domain, if the domain names MUST change, your only recourse is copying the data over manually; there is no automatic or API means to make the copy.
You may be able to use the online web services SimpleBackr or BackupSDB to backup the domains and restore to different domain names. I'm not positive that both services support restoring to different domain names, but I do know the people who run both sites and they are very helpful and responsive when it comes to supporting their services.
Whenever giving out your AWS secret key temporarily, even to trusted individuals, I always recommend that you generate a second key in the AWS Account website and give that out. When the temporary use is done, you can delete the second key, and the existing key used by your apps remains functional and secret.