弹性beanstalkconfiguration中没有列出解决scheme堆栈
当为Elastic Beanstalk设置我的configuration时，我没有给出解决scheme堆栈的任何选项。
这里是有问题的线路：
`Select a solution stack. Available solution stacks are: Select (1 to 0):` 这是整个输出：
bret@ubuntu:~/myapp$ eb init To get your AWS Access Key ID and Secret Access Key, visit "https://aws-portal.amazon.com/gp/aws/securityCredentials". Enter your AWS Access Key ID: Enter your AWS Secret Access Key: Select an AWS Elastic Beanstalk service region. Available service regions are: 1) US East (Virginia) 2) US West (Oregon) 3) US West (North California) 4) EU West (Ireland) 5) Asia Pacific (Singapore) 6) Asia Pacific (Tokyo) 7) Asia Pacific (Sydney) 8) South America (Sao Paulo) Select (1 to 8): 1 Enter an AWS Elastic Beanstalk application name (auto-generated value is "myapp"): Enter an AWS Elastic Beanstalk environment name (auto-generated value is "myapp-env"): Select a solution stack. Available solution stacks are: Select (1 to 0):
我正在运行32位Ubuntu 12.10和AWS Elastic Beanstalk CLI工具版本2.4.0
您使用的凭据不具有pipe理员权限..
转到身份和访问pipe理（IAM）并向用户添加适当的权限。
我创build了一个带有访问密钥和ID的IAM用户，然后单击“附加用户策略”并给该账户一个PowerUserAccess（我不确定“eb init”有什么权限是足够的）
然后键入“eb init”再次运行该程序，解决scheme堆栈出现！
我也有同样的问题。 我用下面的步骤解决它。
- 创build策略（AdministratorAccess）
- 附加到用户
https://console.aws.amazon.com/iam/home?region=us-east-1#policies
我有同样的问题，像米歇尔Glauser我没有任何选项号码表明。 考虑到或许这个问题与我在'eb init'过程中让我的机器睡了几次有关，我做了CTRL + C退出并重新尝试'eb init'。 第二次，我为解决scheme堆栈提供了一组31个选项。 就我而言，提供的选项是：
Select a solution stack. Available solution stacks are: 1) 64bit Amazon Linux 2014.03 v1.0.3 running PHP 5.5 2) 64bit Amazon Linux 2014.03 v1.0.3 running PHP 5.4 3) 32bit Amazon Linux 2014.03 v1.0.3 running PHP 5.5 4) 32bit Amazon Linux 2014.03 v1.0.3 running PHP 5.4 5) 32bit Amazon Linux running PHP 5.3 6) 64bit Amazon Linux running PHP 5.3 7) 64bit Amazon Linux 2014.03 v1.0.3 running Node.js 8) 32bit Amazon Linux 2014.03 v1.0.3 running Node.js 9) 64bit Windows Server 2008 R2 running IIS 7.5 10) 64bit Windows Server 2012 running IIS 8 11) 64bit Amazon Linux 2014.03 v1.0.3 running Tomcat 7 Java 7 12) 64bit Amazon Linux 2014.03 v1.0.3 running Tomcat 7 Java 6 13) 32bit Amazon Linux 2014.03 v1.0.3 running Tomcat 7 Java 7 14) 32bit Amazon Linux 2014.03 v1.0.3 running Tomcat 7 Java 6 15) 32bit Amazon Linux running Tomcat 7 16) 64bit Amazon Linux running Tomcat 7 17) 32bit Amazon Linux running Tomcat 6 18) 64bit Amazon Linux running Tomcat 6 19) 64bit Amazon Linux 2014.03 v1.0.3 running Python 2.7 20) 32bit Amazon Linux 2014.03 v1.0.3 running Python 2.7 21) 64bit Amazon Linux 2014.03 v1.0.3 running Python 22) 32bit Amazon Linux 2014.03 v1.0.3 running Python 23) 32bit Amazon Linux running Python 24) 64bit Amazon Linux running Python 25) 64bit Amazon Linux 2014.03 v1.0.4 running Ruby 2.0 (Puma) 26) 64bit Amazon Linux 2014.03 v1.0.3 running Ruby 2.0 (Passenger Standalone) 27) 64bit Amazon Linux 2014.03 v1.0.3 running Ruby 1.9.3 28) 32bit Amazon Linux 2014.03 v1.0.3 running Ruby 1.9.3 29) 32bit Amazon Linux 2014.02 v1.0.1 running Ruby 1.8.7 30) 64bit Amazon Linux 2014.02 v1.0.1 running Ruby 1.8.7 31) 64bit Amazon Linux 2014.03 v1.0.0 running Docker 1.0.0 Select (1 to 31): 25
当我第一次启动'eb init'时，我还没有创build任何AWS身份和访问pipe理（IAM）组或用户，但是当我被'eb init'询问时，我的密钥是当我创build了这些IAM实体。
1.转到用户; 2.Attach策略：selectadministratorAccess 3.ctrl + c停止并从eb init重新启动！
