Amazon web services AWS Beanstalk环境创建问题。无法启动环境。环境必须具有与其关联的实例配置文件
我正在尝试使用CLI和JavaAPI在AWS Elastic Beanstalk应用程序中创建环境。运行CLI命令后,我在AWS控制台中看到以下错误日志Amazon web services AWS Beanstalk环境创建问题。无法启动环境。环境必须具有与其关联的实例配置文件,amazon-web-services,amazon-ec2,amazon-elastic-beanstalk,aws-sdk,Amazon Web Services,Amazon Ec2,Amazon Elastic Beanstalk,Aws Sdk,我正在尝试使用CLI和JavaAPI在AWS Elastic Beanstalk应用程序中创建环境。运行CLI命令后,我在AWS控制台中看到以下错误日志 2017-07-18 10:26:22 UTC+0530 INFO Deleting SNS topic for environment MySampleApplicationThree-env. 2017-07-18 10:26:20 UTC+0530 ERROR Failed to launch environment
2017-07-18 10:26:22 UTC+0530 INFO Deleting SNS topic for environment MySampleApplicationThree-env.
2017-07-18 10:26:20 UTC+0530 ERROR Failed to launch environment.
2017-07-18 10:26:20 UTC+0530 ERROR Environment must have instance profile associated with it.
2017-07-18 10:26:19 UTC+0530 INFO Using elasticbeanstalk-ap-south-1-839135229895 as Amazon S3 storage bucket for environment data.
2017-07-18 10:26:18 UTC+0530 INFO createEnvironment is starting.
我在API中也看到了同样的错误日志下面是我的CLI命令
aws elasticbeanstalk create-environment --cname-prefix mysampleapplicationthree --application-name MySampleApplicationThree --version-label "Sample Application" --environment-name mysampleapplicationfour --solution-stack-name "64bit Amazon Linux 2017.03 v2.6.1 running Tomcat 8 Java 8"
下面是我的API代码
AWSElasticBeanstalk client = AWSElasticBeanstalkClientBuilder.defaultClient();
CreateEnvironmentRequest createEnvironmentRequest = new CreateEnvironmentRequest()
.withApplicationName("MySampleApplicationThree")
.withEnvironmentName("MySampleApplicationThree-env")
.withCNAMEPrefix("MySampleApplicationThree")
.withSolutionStackName("64bit Amazon Linux 2017.03 v2.5.1 running Java 8")
.withVersionLabel("Sample Application");
CreateEnvironmentResult envresult = client.createEnvironment(createEnvironmentRequest);
我没有找到合适的解决办法。如果有人帮助解决这个问题,这将是有帮助的。谢谢 用户似乎没有足够的权限。转到您的IAM控制台,并将
AWSELASTICBEanstolkFullAccess
策略附加到相应的角色。我刚刚将我所在的地区从孟买(AP_SOUTH_1
)改为新加坡(AP_SOUTH_1
),现在可以使用了。但我不知道这背后的原因。如果有人对此有任何了解,请将其发布在此处。不知道此区域更改如何解决此问题,据我所知,AWS不存在也不应该存在特定于区域的错误,要解决此问题,我遵循下面的答案
即使在附加了
AWSElasticBeanstalkFullAccess
政策之后,我也面临着同样的问题。经过6个小时的努力,我找到了你的答案。谢谢。