ElasticBeanstalk 尝试在authorized_keys 中添加ssh 访问答案

【问题标题】：ElasticBeanstalk Tried to add ssh access in authorized_keysElasticBeanstalk 尝试在authorized_keys 中添加ssh 访问
【发布时间】：2019-03-22 05:36:11
【问题描述】：

昨天我尝试按照 stackoverflow 的这个答案将多个用户添加到我们的 Elastic Beanstalk 环境中的 authorized_keys 以进行 QA。

https://stackoverflow.com/a/46269015/1827986

但是在这样做之后，部署失败并出现以下错误

2018-10-16 19:04:22    INFO    Environment update is starting.
2018-10-16 19:05:05    INFO    Deploying new version to instance(s).
2018-10-16 19:06:09    ERROR   [Instance: i-05cc43b96ffc69145] Command 
failed on instance. Return code: 1 Output: (TRUNCATED)...erform: 
iam:GetGroup on resource: group BeanstalkAccess
declare -a users_array='()'
chmod: cannot access ‘/home/ec2-user/.ssh/authorized_keys’: No such 
file or directory
chown: cannot access ‘/home/ec2-user/.ssh/authorized_keys’: No such 
file or directory.
Hook /opt/elasticbeanstalk/hooks/appdeploy/post/980_beanstalk_ssh.sh 
failed. For more detail, check /var/log/eb-activity.log using console 
or EB CLI.
2018-10-16 19:06:09    INFO    Command execution completed on all 
instances. Summary: [Successful: 0, Failed: 1].
2018-10-16 19:06:10    ERROR   Unsuccessful command execution on 
instance id(s) 'i-05cc43b96ffc69145'. Aborting the operation.
2018-10-16 19:06:10    ERROR   Failed to deploy application.

然后我尝试部署以前的应用程序版本，该版本已知可以工作但失败了。我试图重建环境，以便我可以部署一个工作的应用程序版本。但是，它会继续尝试部署导致错误的相同卡住版本。

现在重建后，我收到一堆关于 ELB 无法访问实例的错误。

100.0 % of the requests are erroring with HTTP 4xx. Insufficient request 
rate (12.0 requests/min) to determine application health.
Command failed on all instances.
ELB health is failing or not available for all instances.

当我进入 EC2 时，它显示实例正在运行，并且运行状况为绿色。

我只是尝试转到应用程序版本并删除了不会部署的版本，希望它能从工作版本中恢复。但是，现在当我尝试部署工作版本时它只是给出以下错误。

Environment health has transitioned from Degraded to Severe. Command 
failed on all instances. Incorrect application version found on all 
instances. Expected version "app-v1_5_13-719-gc533-181016_092351" 
(deployment 291). Application update failed 2 minutes ago and took 2 
minutes. ELB health is failing or not available for all instances.

我还能做些什么来让它恢复工作状态？

【问题讨论】：

标签： amazon-web-services amazon-elb amazon-elastic-beanstalk

【解决方案1】：

原来是内存问题，因为我们是在微服务器上运行的，我不知道为什么我们会突然达到极限，但是升级到一个小实例解决了这个问题。

【讨论】：