-
Notifications
You must be signed in to change notification settings - Fork 13
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
Upgrade to AL 2023 #23
Comments
No reason to stay on AL2. We'll upgrade. @oycyc assigning this your way again 😁 |
Possibly related, but I noticed when we used this launch template that the GP3 volume was not marked as encrypted. I think that may be defined in the launch template? |
Seems like both when we use AL2 (default GP2 volume) or or when we use AL3 (default GP3 volume): I can specify the launch template for the volume to be encrypted. AFAIK there is no downside, @Gowiem is there anything that wouldn't make it a good idea to mark as encrypted by default? |
@oycyc encryption by default is always good, go for it 👍 |
Hey @Gowiem , we discovered another IPv6 issue where the AL 2 images used in the tailscale module didn't seem to route IPv6 traffic by default. Tailscale also did not register IPv6 connectivity for the subnet router machines.
From the image this failed with a "network unreachable" error:
We explicitly set the
ami
override to an Amazon Linux 2023 image and it seems to have fixed the issue for us. I don't know if you have a requirement for AL2, but AL2023 seems to be a bit better in this regard. Cheers!The text was updated successfully, but these errors were encountered: