由网友(森林谜了鹿)分享简介：新OpsWorks我... new to OpsWorks I am... 和using- 1）自定义堆栈的Windows操作系统和OpsWorks-UI控制台1) Custom stack for Windows-os and OpsWorks-UI console2）自定义AMI来创建堆栈的实例。 2) C...

新OpsWorks我...

new to OpsWorks I am...

和using-

1）自定义堆栈的Windows操作系统和OpsWorks-UI控制台

1) Custom stack for Windows-os and OpsWorks-UI console

2）自定义AMI来创建堆栈的实例。

2) Custom ami to create stack's instance.

3）实例是t2.micro类型，无论是在同一个子网

3) Instances are of "t2.micro" type and both in same subnet

我创建2个实例其中有一个是停留在引导等是停留在运行，建立状态。我审阅，以 - 这个，但我能得到它粘在实例的运行 - 建立的RDP连接。

I created 2 instances out of which one is stuck at "booting" other is stuck at "running-set-up" state. I refereed to -this but I can get the RDP access of the instance which is stuck at "running-set-up".

我的提问 -

1）为什么实例停留在这样的状态？ Inspite做了简单的配置。

1) Why are the instances stuck at such states? Inspite of the simple configurations done.

2）为什么其他实例是停留在启动状态？虽然它有像被卡在磨合建立状态

2) Why the other instance is stuck at "booting" state ? Although it has the same settings like the one which is stuck in "running-set-up" state

3）什么样的设置或配置我失踪了？

3) What kind of settings or configurations I am missing on?

非常感谢这个任何形式的帮助！

Thanks a lot for any kind of help to this !

推荐答案

我有同样的问题，它看起来像你需要做一些设置你从以创建自定义AMI的OpsWorks正确安装实例在OpsWorks代理时，它推出的实例到堆栈：

I was having the same problem and it looks like you need to do a little setup on the instance you create the custom AMI from in order for OpsWorks to properly install the OpsWorks agent when it launched instances into the stack:

在启动新的Windows 2012 R2的实例（在我们的情况下，它是MS 2012 R2瓦特/ SQL服务器2014年的Web AMI） 在登录到新的实例，并运行EC2ConfigService设置 导航，图像标签 选择随机下的管理员密码 单击关闭以SYS $ P $页 在等待比如关机，然后从它创建AMI （右键单击 - >图像 - >创建映像的EC2实例控制台） 创建一个新的OpsWorks栈（选择的Microsoft Windows Server 2012 R2基地或使用自定义Windows AMI为默认操作 系统） 在堆栈中创建一个新层 添加一个新的实例来图层（选择你所创建的AMI 第6步高级下 - >操作系统） 启动新的实例 在等待，看看从启动，以实例的状态改变  running_setup（可能需要相当长的一段时间，超过20分钟） Launch new Windows 2012 R2-based instance (in our case it was the MS 2012 R2 w/ SQL Server 2014 Web AMI) Log into new instance and run EC2ConfigService Settings Navigate to "Image" tab Choose "Random" under "Administrator Password" Click "Shutdown with Sysprep" Wait for instance to shutdown and then create AMI from it (Right-click->Image->Create Image in the EC2 Instances Console) Create a new OpsWorks stack (choosing "Microsoft Windows Server 2012 R2 Base" or "Use custom Windows AMI" for the "Default operating system") Create a new layer in your stack Add a new instance to your layer (choosing the AMI you created in Step 6 under Advanced -> Operating system) Start your new instance Wait to see instance status change from "booting" to "running_setup" (may take quite some time, 20+ minutes)

HTTP：//www.ryanmelena .COM / 2015年/ 08/13 /自定义窗口实例上-AWS-opsworks /

步骤2-6，你需要做的，为了得到OpsWorks正确初始化实例的关键部分。

Steps 2-6 are the critical parts you need to do in order to get OpsWorks to properly initialize the instance.