How to update Elastic Beanstalk instance to Graviton

0

I logged into the AWS Console this week and saw the following message:

AWS Graviton now supported AWS Graviton, an arm64-based processor, can offer up to 40% better price performance over the comparable x86 processor. To upgrade to an arm64 instance type, choose it in the 'Capacity' settings in 'Additional configuration.'

I am having trouble finding the 'Capacity' settings in 'Additional configuration.'. Where is this located? Is there a guide available on how to do this?

I've already reviewed the following resources:
https://github.com/aws/aws-graviton-getting-started
https://aws.amazon.com/about-aws/whats-new/2021/11/elastic-beanstalk-aws-graviton-ec2/

已提问 2 年前510 查看次数
1 回答
0

Hello,

I understand that you are trying to update Elastic Beanstalk instance to AWS Graviton. In the Elastic Beanstalk console, select your environment, and on the navigation pane a drop down will appear, click Configuration, in here different types of configurations will appear. Since you want to change the instance type, click Edit next to Capacity as your configuration option.

Under Modify capacity you will see different configurations in which Instance types is included.

By default, Elastic Beanstalk selects the x86 processor architecture when you create a new environment. You can choose the processor architecture (x86, arm64) for the instance types only when you’re creating a new environment. After you create an environment, you can only change the instance types to others within the same processor architecture of your running environment. You can't change the processor architecture.

For a list of Graviton image IDs for each supported platform branch and Region, see Graviton image IDs for supporting platforms on this page.

I hope this information is helpful.

Lunga T
已回答 2 年前
  • @Lunga if I understand you correctly, you said:

    "After you create an environment, you can only change the instance types to others within the same processor architecture of your running environment."

    Currently my instance types are: t2.micro and t2.small, and my AMI ID is: ami-0329b80de801a0663

    Would this imply that I am sort of locked in and would need to create a new instance using arm64 from the start?

    I do see that the above AMI ID is editable. I suppose modifying that to:

    64bit Amazon Linux 2 v5.4.6 running Node.js 14 ami-0b35d2f960c29d3d7

    Would do anything?

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

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

回答问题的准则