Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Publish AWS AMIs using gp3 block devices as default #4000

Open
jfrancisco0 opened this issue May 28, 2024 · 2 comments
Open

Suggestion: Publish AWS AMIs using gp3 block devices as default #4000

jfrancisco0 opened this issue May 28, 2024 · 2 comments
Labels
status/needs-triage Pending triage or re-evaluation type/enhancement New feature or request

Comments

@jfrancisco0
Copy link

What I'd like:

Currently, Bottlerocket images default to creating two volumes (as explained in the README), and the AWS AMIs have these volumes set as gp2 by default. For example, ami-0b2c067c54702aea4.

I suggest setting it to gp3 instead, since it provides lower price per GB, and the new Amazon Linux version (AL2023) already sets it as default.

I understand the volume type may be overridable, depending on one's deployment scenario, but I don't see any obvious upside to maintaining gp2 as the default, so I decided to leave this suggestion here.

@jfrancisco0 jfrancisco0 added status/needs-triage Pending triage or re-evaluation type/enhancement New feature or request labels May 28, 2024
@ytsssun
Copy link
Contributor

ytsssun commented May 30, 2024

Hi @jfrancisco0, thanks for bringing this up. It is a very valid suggestion to make the default volume type to gp3. We have made some evaluation on gp3 in the past. While gp3 obviously provides a more cost effective way to achieve the SSD performance with better baseline performance, we did notice that the boot time with gp3 is slightly slower than with gp2.

However, it has been a while since the last time we perform that evaluation. I will work with the team to run another boot time tests and see if we see better result.

Again, thanks for bringing this to our attention, I will keep you posted with my testing.

@jfrancisco0
Copy link
Author

Thanks for following up @ytsssun! 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/needs-triage Pending triage or re-evaluation type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants