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

default to gp3 volumes #784

Merged
merged 1 commit into from
Dec 21, 2020
Merged

default to gp3 volumes #784

merged 1 commit into from
Dec 21, 2020

Conversation

yob
Copy link
Contributor

@yob yob commented Dec 21, 2020

AWS announced gp3 EBS volumes earlier this month. They're slightly cheaper and have the same or better performance than gp2, so we may as well default to the new type.

AWS announce gp3 EBS volumes earlier this month [1]. They're slightly
cheaper and have the same or better performance than gp2 [2], so we may
as well default to the new type.

[1] https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ebs-general-purpose-volumes-gp3/
[2] https://aws.amazon.com/ebs/general-purpose/
@yob yob merged commit 59b8bab into master Dec 21, 2020
@yob yob deleted the new-storage-type branch December 21, 2020 12:37
@pda
Copy link
Member

pda commented Feb 8, 2021

When building elastic-stack AMIs, we search for the latest upstream amzn2-ami-hvm-2.0.*-gp2 as a base. Note the gp2 in the name. But currently there's no …-gp3equivalent. Maybe one day there will be, though 🤷‍♂️ I guess we could useamzn2-ami-hvm-2.0.-gp?oramzn2-ami-hvm-2.0.-gp*` or something. Anyway, fine for now, just a note for future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants