跳至内容

Beanstalk console cannot pick arm64 options

0

Using AWS console to create a new environment of an elastic beanstalk app, I cannot select arm64 instances anymore. When I do so, the console automatically applies as default instance types "t3.micro" which is not a valid arm64 instance type and the call to AWS console backend servers for configuration options fails, making the select not update.

{"__type":"com.amazonaws.elasticbeanstalk#ConfigurationValidationException","message":"Configuration validation exception: Invalid option specification (Namespace: 'aws:ec2:instances', OptionName: 'InstanceTypes'): Your selected instance types (t3.micro) aren't available in your selected VPC Subnets. . Please check your VPC Subnets."}

I have never created an env using the AWS CLI and I cwould like to avoid, has anyoene a workaround?

已提问 3 年前425 查看次数
2 回答
0

Hi,

Seems could be related to this bug: https://repost.aws/questions/QU6Fg7aCOuRIuE1JdnQhTgZw/aws-elastic-beanstalk-new-console-2023-bug.

As workaround, if not comfortable with CLI, you should give a try to Infrastructure as Code (Terraform, CDK, Cloudformation).

As an example , this is a walkthrough to deploy a web app to Elastic Beanstalk (https://aws.amazon.com/getting-started/guides/deploy-webapp-elb/module-two/) using JavaScript.

Hope it helps ;)

专家
已回答 3 年前
0

Thanks I will have a look, it seems related indeed. Sadly the old app was created without terraform, so it won't be super easy.

已回答 3 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。