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

Updates to AWS EC2 AMI defaults #1502

Closed
prestist opened this issue May 31, 2023 · 9 comments
Closed

Updates to AWS EC2 AMI defaults #1502

prestist opened this issue May 31, 2023 · 9 comments

Comments

@prestist
Copy link
Contributor

prestist commented May 31, 2023

Describe the enhancement

With the upcoming development on F39, we should make a few changes in bulk as there is a overhead overlap between the following changes.

  • Update our AWS AMIs with the IMDSv2-only flag
    • Since IMDSv1 is not part of this consideration, there is some potential application breakage. We need to be sure to announce this change in the f39 rebase and opening of next
  • Default EC2 AMI's to the gp3 EBS volume type
    • The gp3 volume type has a lower minimum IOP rating for volumes smaller than 3TB. We should include it in the release notes to inform the enduser of the default change.
  • Switch AMIs to uefi-preferred
    • Existing Draft PR

System details

F39

Additional information

These were discussed in the FCOS community meeting 5/31/23

xref:

@dustymabe dustymabe changed the title F39: AWS EC2 update AMIs F39: Updates to AWS EC2 AMI defaults May 31, 2023
@bgilbert
Copy link
Contributor

Since the gp3 volume type has a higher minimum IOP rating (3000) we should include it in the release notes

The concern is that it has a lower minimum IOPS for volumes > 3 TB, and a minimum throughput that ranges from "slightly lower" to "half as much" depending on the volume size.

@dustymabe dustymabe added the jira for syncing to jira label Jun 14, 2023
@quentin9696
Copy link

@bgilbert At my job, we already use gp3 with default IOPS option on FCOS in production and we don't have any complains about using gp3

@bgilbert
Copy link
Contributor

@quentin9696 My point wasn't that we shouldn't switch, just that we need to announce that we're doing so.

@quentin9696
Copy link

@bgilbert this can also reassure people who are using it with the current disk

@dustymabe dustymabe added the status/pending-next-release Fixed upstream. Waiting on a next release. label Sep 16, 2023
@dustymabe
Copy link
Member

Some docs for the IMDSV2 changes:

@dustymabe dustymabe changed the title F39: Updates to AWS EC2 AMI defaults Updates to AWS EC2 AMI defaults Sep 18, 2023
@dustymabe
Copy link
Member

The fix for this went into next stream release 39.20230916.1.1. Please try out the new release and report issues.

@dustymabe dustymabe added status/pending-testing-release Fixed upstream. Waiting on a testing release. F39 and removed status/pending-next-release Fixed upstream. Waiting on a next release. F39 labels Sep 20, 2023
@travier
Copy link
Member

travier commented Oct 17, 2023

See: #1491 (comment)

@dustymabe
Copy link
Member

The fix for this went into testing stream release 39.20231101.2.0. Please try out the new release and report issues.

@dustymabe dustymabe added status/pending-stable-release Fixed upstream and in testing. Waiting on stable release. and removed status/pending-testing-release Fixed upstream. Waiting on a testing release. labels Nov 7, 2023
@dustymabe
Copy link
Member

The fix for this went into stable stream release 39.20231101.3.0.

@dustymabe dustymabe removed the status/pending-stable-release Fixed upstream and in testing. Waiting on stable release. label Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants