search

aws / elastic-beanstalk-roadmap

AWS Elastic Beanstalk roadmap
https://aws.amazon.com/elasticbeanstalk/
Creative Commons Attribution Share Alike 4.0 International
283 stars 11 forks source link

Full console functionality for Arm64-based instance type support #212

Open snnles opened 2 years ago

snnles commented 2 years ago

We have launched arm64 (Graviton) based EC2 instances on Elastic Beanstalk on all of the latest Amazon Linux 2 platforms across all AWS Graviton supported Regions. Please refer to release notes and What’s New post for more details. The functionality to update an existing environment to use arm64-based instances from Elastic Beanstalk console is still a work-in-progress. Meanwhile, we would appreciate your feedback on using arm64-based instances on Elastic Beanstalk by answering below questions. Thank you for your support.

  1. What kind of application are you running on arm64 (Graviton) instances? (web application, worker, APIs, etc.)
  2. Did you face any compatibility issues while deploying your application on arm64 (Graviton) instances? If yes, how did you resolve the issues?
  3. What interface do you prefer to use Elastic Beanstalk? (Console, CLI, CloudFormation, CDK, IDE extension, GitHub app)
  4. How has your experience been on using Elastic Beanstalk console for deploying your applications using Graviton based EC2 instances? Any feedback on improving the console experience?
  5. Have you compared the price-performance improvements offered by arm64 (Graviton) instances? How are the results? How did you compare the price-performance of arm64 vs x86 based instances?
alloylab commented 2 years ago

What is the timeline to update an existing environment?

hjardines commented 2 years ago

Any updates on being able to update an existing environment? How will the new C6g compare to the current C6i?

g3n10z commented 2 years ago

Hi, i'm tryng to create a new enviroment starting from a graviton saved configuration from a perfect enviroment.

i receive this error: Configuration validation exception: Invalid option specification (Namespace: 'aws:ec2:instances', OptionName: 'InstanceTypes'): The instance types you chose (t4g.micro) aren't valid for the architecture types(s) you designated: [x86_64].

Your configuration does'nt save the architecture type!! Very very wonderful! Can you fix?

RobbiewOnline commented 1 year ago

+1 for upgrading an existing environment

In my case from t2.small (64bit Amazon Linux 2 v4.3.3 running Tomcat 8.5 Corretto 11 x86 architecture) to t4g.small arm64.

The workaround appears to be to save the configuration, tweak it to use arm64, then setup a new environment using that configuration.

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environment-configuration-savedconfig.html