导致我尝试为AWS-EB启用SSH失败的原因是什么?

时间:2015-01-14 15:46:30

标签: amazon-web-services ssh elastic-beanstalk

我正在尝试为我的AWS Elastic Beanstalk应用程序启用SSH并运行eb ssh --setup(使用似乎be suitable privilegesElasticBeanstalkFullAccess的用户;使用AWS CLI 3.x );但我的尝试失败了以下(改变GUID以保护无辜者):

INFO: Environment update is starting.
INFO: Updating environment sitetest-develop-env's configuration settings.
INFO: Created Auto Scaling launch configuration named: awseb-e-notrea1nUm-stack-AWSEBAutoScalingLaunchConfiguration-MAdUpa2bCrCx
ERROR: Updating Auto Scaling group failed Reason: Template error: DBInstance bxzumnil42x11w doesn't exist
ERROR: Service:AmazonCloudFormation, Message:Stack named 'awseb-e-notrea1nUm-stack' aborted operation. Current state: 'UPDATE_ROLLBACK_IN_PROGRESS'  Reason: The following resource(s) failed to update: [AWSEBAutoScalingGroup]. 
ERROR: Failed to deploy configuration.
INFO: Created Auto Scaling launch configuration named: awseb-e-myjrm7xr9n-stack-AWSEBAutoScalingLaunchConfiguration-5uKixPQCM71K
INFO: Deleted Auto Scaling launch configuration named: awseb-e-notrea1nUm-stack-AWSEBAutoScalingLaunchConfiguration-MAdUpa2bCrCx
INFO: The environment was reverted to the previous configuration setting.

是什么导致这种情况发生?我是否需要在AWS控制台中执行某些操作来防止此错误?

1 个答案:

答案 0 :(得分:1)

我在此处看到的相关错误消息是DBInstance bxzumnil42x11w doesn't exist。 您可能已经选择让Elastic Beanstalk创建RDS服务器作为环境创建过程的一部分。现在看来数据库不再存在了。你手动杀了它吗? 无论如何,我建议不要让EB管理您的RDS。最好自己创建一个并手动分配以下环境变量:RDS_HOSTNAME, RDS_PORT, RDS_DB_NAME, RDS_USERNAME, RDS_PASSWORD 此时我建议终止此env并创建一个新的env,但这次不要选中名为Create an RDS DB Instance with this environment的复选框。