You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
What do you want us to build?
Currently in US-east-1, we can select the option for m7a.medium, however when we started to build env with this instance type, it will shows the following error:
The specified instance type m7a.medium is not valid (Service: AutoScaling)
Is this request specific to an Elastic Beanstalk platform?
If so, which one(s)? so far i tested this in .NET 8 running on 64bit Amazon Linux 2023/3.1.6
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
the problem is that we cannot select this instance type, tried the option where from the UI where we disable the IMDSv1, however this doesnt force EB to use launch template.
Are you currently working around this issue?
How are you currently solving this problem?
Currently from AWS the only workaround is by modifying the ebextension where we
option_settings:
aws:autoscaling:launchconfiguration:
DisableIMDSv1: true
this will force the EB to use launch template, however this is not the most effective option as customer will need to modify their app and include that, customer should be able to use that instance type straight away
Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
The text was updated successfully, but these errors were encountered:
Community Note
Tell us about your request
What do you want us to build?
Currently in US-east-1, we can select the option for m7a.medium, however when we started to build env with this instance type, it will shows the following error:
The specified instance type m7a.medium is not valid (Service: AutoScaling)
Is this request specific to an Elastic Beanstalk platform?
If so, which one(s)? so far i tested this in .NET 8 running on 64bit Amazon Linux 2023/3.1.6
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
the problem is that we cannot select this instance type, tried the option where from the UI where we disable the IMDSv1, however this doesnt force EB to use launch template.
Are you currently working around this issue?
How are you currently solving this problem?
Currently from AWS the only workaround is by modifying the ebextension where we
option_settings:
aws:autoscaling:launchconfiguration:
DisableIMDSv1: true
this will force the EB to use launch template, however this is not the most effective option as customer will need to modify their app and include that, customer should be able to use that instance type straight away
Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
The text was updated successfully, but these errors were encountered: