是什么原因造成我尝试启用SSH的AWS-EB失败？ [英] What is causing my attempt to enable SSH for AWS-EB to fail?
问题描述
我想启用SSH我的AWS弹性魔豆的应用，并已执行 EB SSH --setup （与什么似乎的be合适的权限中， ElasticBeanstalkFullAccess ;使用AWS CLI 3.X）;但我的尝试失败，出现以下（GUID的更改，以保护无辜）：
I'm trying to enable SSH for my AWS Elastic Beanstalk application and have run eb ssh --setup (as a user with what seem to be suitable privileges, ElasticBeanstalkFullAccess; using AWS CLI 3.x); but my attempt fails with the following (GUIDs changed to protect the innocent):
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控制台做prevent这个错误？
What is causing this to happen? Is there something I need to do in the AWS Console to prevent this error?
推荐答案
相关错误信息我在这里看到的是 dbinstance具备bxzumnil42x11w不存在。
你可能已经选择加入让弹性魔豆创建一个RDS服务器环境创建过程的一部分。现在看来分贝不再存在。你手动杀了它？
在任何情况下，我会建议不要让EB管理您的RDS。这是最好的做法是自己创建并手动将以下环境变量： RDS_HOSTNAME，RDS_PORT，RDS_DB_NAME，RDS_USERNAME，RDS_PASSWORD
在这一点上，我会建议终止此ENV并创建一个新的，只是这一次没有选中命名的复选框创建RDS数据库实例与这个环境。
the relevant error message i see here is DBInstance bxzumnil42x11w doesn't exist.
You have probably opted into letting Elastic Beanstalk create an RDS server as part of the environment creation process. Now it seems the db is no longer there. Did you kill it manually?
In any case, I would recommend NOT to let EB manage your RDS. it's best practice to create one yourself and manually assign the following environment variables: RDS_HOSTNAME, RDS_PORT, RDS_DB_NAME, RDS_USERNAME, RDS_PASSWORD.
At this point I would recommend terminating this env and creating a new one, only this time don't check the checkbox named Create an RDS DB Instance with this environment.
这篇关于是什么原因造成我尝试启用SSH的AWS-EB失败？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
