This is the list of Windows Images. I couldn't find one with what you are asking, so you need to start from an existing one (better to start with one that has IIS already installed) and then install PHP and MySQL yourself. Then you could save this as your base image and use it for all your subsequent deployments.
However, the infrastructure you are describing doesn't fit well with a Cloud environment. At first, MySQL or any other relational database isn't a suitable persistence mechanism. It is not guaranteed that your instance will not go away, and if that does happen, then all data stored in the local file system will be lost. You can only safely use MySQL by employing Elastic Block Storage. This is another consideration for you.
For the same reason, it is not recommended to use a simple image to serve files. Amazon offers S3 service, which is great on this respect.
As a conclusion, deploying in a Cloud environment is different than deploying in dedicated servers. You need a different architecture, not just to reproduce your installations.
Depending on how well-documented and well-backed up your site is, it shouldn't be too bad. Of course, try to stick to an OS as similar as possible to your original system. In fact, you can even build your image from scratch by following the documentation. There are even ways to build a system from install media in your own VMWare setup and then push it up to EC2 (see here and here). I've never done that but it sounds doable in principle. If I had a long-term server I was to run on EC2.
On the other hand, you could just spend a hundred bucks or so and go to odesk.com or somewhere and have somebody migrate it for you. Just tell him you want a comprehensive listing of everything he did, and voila—instant documentation.
Edit: As kgiannakakis says, make sure you are clear on the EC2 technology, as it is not the same as hosting.
发布评论
评论（2）
这是 Windows 映像的 列表。 我找不到符合您要求的产品，因此您需要从现有的产品开始（最好从已安装 IIS 的产品开始），然后自行安装 PHP 和 MySQL。 然后，您可以将其保存为基础映像并将其用于所有后续部署。
但是，您所描述的基础设施不太适合云环境。 首先，MySQL 或任何其他关系数据库都不是合适的持久性机制。 不能保证您的实例不会消失，如果发生这种情况，则存储在本地文件系统中的所有数据都将丢失。 您只能通过使用弹性块存储来安全地使用 MySQL。 这是您的另一个考虑因素。
出于同样的原因，不建议使用简单的镜像来服务文件。 Amazon 提供了 S3 服务，这在这方面非常出色。
总之，在云环境中部署与在专用服务器中部署不同。 您需要不同的架构，而不仅仅是为了重现您的安装。
This is the list of Windows Images. I couldn't find one with what you are asking, so you need to start from an existing one (better to start with one that has IIS already installed) and then install PHP and MySQL yourself. Then you could save this as your base image and use it for all your subsequent deployments.
However, the infrastructure you are describing doesn't fit well with a Cloud environment. At first, MySQL or any other relational database isn't a suitable persistence mechanism. It is not guaranteed that your instance will not go away, and if that does happen, then all data stored in the local file system will be lost. You can only safely use MySQL by employing Elastic Block Storage. This is another consideration for you.
For the same reason, it is not recommended to use a simple image to serve files. Amazon offers S3 service, which is great on this respect.
As a conclusion, deploying in a Cloud environment is different than deploying in dedicated servers. You need a different architecture, not just to reproduce your installations.
根据您网站的记录和备份情况，情况应该不会太糟糕。 当然，请尝试坚持使用与原始系统尽可能相似的操作系统。 事实上，您甚至可以按照文档从头开始构建图像。 甚至有方法可以在您自己的 VMWare 设置中从安装介质构建系统，然后将其推送到 EC2（请参阅 此处 和 此处）。 我从来没有这样做过，但原则上听起来是可行的。 如果我有一台长期服务器，我将在 EC2 上运行。
另一方面，您只需花费一百美元左右，访问 odesk.com 或其他地方，让某人为您迁移它。 只要告诉他你想要一份他所做的一切的完整列表，瞧——即时文档。
编辑： 正如 kgiannakakis 所说，请确保您清楚 EC2 技术，因为它与托管不同。
Depending on how well-documented and well-backed up your site is, it shouldn't be too bad. Of course, try to stick to an OS as similar as possible to your original system. In fact, you can even build your image from scratch by following the documentation. There are even ways to build a system from install media in your own VMWare setup and then push it up to EC2 (see here and here). I've never done that but it sounds doable in principle. If I had a long-term server I was to run on EC2.
On the other hand, you could just spend a hundred bucks or so and go to odesk.com or somewhere and have somebody migrate it for you. Just tell him you want a comprehensive listing of everything he did, and voila—instant documentation.
Edit: As kgiannakakis says, make sure you are clear on the EC2 technology, as it is not the same as hosting.