Support new instance types as soon as they are generally available

[shaicoleman]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave "+1" or "me too" comments. They generate extra noise for issue followers and do not help prioritize the request.

Tell us about your request
If it's possible to launch an EC2 instance type, it should be possible via Elastic Beanstalk.

At the moment some instance types, e.g. m7a.medium are failing to launch via Elastic Beanstalk, with an error:
The specified instance type m7a.medium is not valid

The same instances launch fine as EC2 instances (e.g. in eu-west-1)

Also, these instance types are showing up as valid options in the console.

[shaicoleman]

Related: #309

[Glaaj]

I'm running into this as well in eu-west-1. I cannot find information regarding which instances types are supported by elastic beanstalk at all. They do show up in the list in the UI however making it very confusing with the minimal information provided in the error message.

[rahulrajaram]

In general, you should have access to all instance types that EC2 supports in a given region. This list is sometimes filtered based on the platform type and a list of other internal EB conditional checks.

Given a solution stack, you can get a list of instance types you could use to create an environment with it like:

aws elasticbeanstalk describe-configuration-options \
  --options="Namespace=aws:ec2:instances,OptionName=InstanceTypes" \
  --region us-east-1 \
  --solution-stack "64bit Amazon Linux 2 v5.3.2 running Node.js 12"

You can similarly pass the --environment-name flag to get a list of instances types that you could run the environment with.

[dfsa3ws]

I have the same problem in eu-west-1 with launching an m7i.large via Elastic Beanstalk.

Creating Auto Scaling launch configuration failed Reason: Resource handler returned message: "The specified instance type m7i.xlarge is not valid (Service: AutoScaling, Status Code: 400, Request ID: )" (RequestToken: , HandlerErrorCode: InvalidRequest)

I can launch these fine from the console.

I ran @rahulrajaram 's command, and the desired instance shows when searching both via soluton-stack and environment name.

[MADDY312]

I am trying to switch from t2.small to c7a.medium/m7a.medium, It throws the same error, but when trying to switch from t2.small to c5a.large, it works fine. And my region is us-east-1. Has anybody found any solution to this?

[dfsa3ws]

I re-tested this today and can confirm that it remains an issue.