CodeDeploy 不适用于 ASG 暖池
我最近试图为ASG建立一个温暖的游泳池，以减少扩展的发布时间。但事实证明，从温暖池中启动的实例被困在“待定：等待”状态，而没有完成编码eploy应该完成的部署。同时，如果直接从ASG启动一个实例，则效果很好。
在与AWS支持联系后，我在用户达塔的最后一行中添加了AWS自动化完整的lifecycle-action命令，以手动完成编码Eploy托管生命周期挂钩。另外，我将lambda函数定为由事件桥规则触发的lambda函数，该功能在从温暖池中启动后，发送aws自动化完整的lifecycle-action请求使实例进入“内部服务”状态。但是，此方法仅使实例处于“内部服务”状态，但部署实际上仍未完成。编码eploy活动历史记录表明部署被卡住了，没有处理任何事件。当我远程远程查看时，我发现编码器代理甚至没有安装。
AWS支持承认，温暖的游泳池并不是一定会支持编码人员。但是，他还确认这两项服务应该与一些额外的作品合作。有任何想法吗？提前致谢。
I recently tried to set up a warm pool for an ASG to reduce the launch time of scaling out. But it turns out the instance launched from the warm pool got stuck at the 'pending:wait' status and did not finish the deployment which should be done by CodeDeploy. At the same time, if an instance is launched from the ASG directly, it works well.
After contacting AWS support, I added a aws autoscaling complete-lifecycle-action command in the last line of the userdata to manually complete the CodeDeploy managed lifecycle hook. Also, I creted a Lambda Function triggered by a EventBridge rule that send aws autoscaling complete-lifecycle-action request to forcely make instances go into "inservice" status after launched from the warm pool. However, this method only makes the instance be in the "inservice" status but the deploymemt actually still not finished. The CodeDeploy activity history shows that the deployment is stuck and no Event is processed. When I remoted into the instance to have a look, I found the codedeploy agent is not even installed.
AWS support admits that the warm pool does not offically support CodeDeploy. However, he also confirms that these two services should work well with some extra works. Does any have a thought about this? Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论