43

在为 Elastic Beanstalk 设置我的配置时,我没有为解决方案堆栈提供任何选项。

以下是有问题的行:

`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

4

5 回答 5

78

您使用的凭据没有管理员权限..

转到身份和访问管理 (IAM) 并向用户添加适当的权限。

于 2013-05-18T10:15:35.420 回答
7

我创建了一个具有访问密钥和 ID 的 IAM 用户,然后单击“附加用户策略”并为该帐户提供了 PowerUserAccess。(我不确定哪些权限对于“eb init”来说足够了)

然后键入“eb init”再次运行该程序,出现了解决方案堆栈!

于 2014-11-13T14:28:19.343 回答
3

我也有同样的问题。我通过以下步骤解决了它。

  1. 创建策略(管理员访问)
  2. 将其附加到用户

https://console.aws.amazon.com/iam/home?region=us-east-1#policies

于 2015-02-12T13:36:27.827 回答
2

我遇到了同样的问题,就像 Michelle Glauser 我根本没有任何选项编号。考虑到问题可能与我在“eb init”过程中让我的机器休眠了几次有关,我按 CTRL+C 退出并重新尝试了“eb init”。第二次,我看到了一组 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”时,我还没有创建任何 AWS Identity and Access Management (IAM) 组或用户,尽管当“eb init”向我询问密钥时,我创建了这些 IAM 实体。

于 2014-06-26T21:18:03.213 回答
1

1.转到用户;2.附加策略:选择administratorAccess 3.ctrl + c 停止并从eb init 重新启动!

于 2015-02-23T15:30:59.080 回答