feat: migrate EC2 userdata + RegionMap from Amazon Linux 2 to AL2023 - #20
Merged
Conversation
This was referenced Jun 11, 2026
Amazon Linux 2 reaches end of support on 2026-06-30. Changes: - RegionMap: regenerated for all 17 regions with the latest AL2023 kernel-default AMIs (x86_64 + arm64 everywhere), via the AL2023-updated cfn/vpn/ami logic (SSM /aws/service/ami-amazon-linux-latest/ al2023-ami-kernel-default-<arch>). - userdata: yum install docker from the AL2023 core repos (amazon-linux-extras is AL2-only); IMDSv2 token-based metadata curls (AL2023 AMIs default to IMDSv2-required, bare curls return 401); yum install aws-cfn-bootstrap (update was a silent no-op when the helper scripts are not preinstalled). - EnableL2TP: replaced the host install of openswan/xl2tpd from EPEL (which AL2023 does not ship) with the containerized server alexzhangs/xl2tpd-libreswan (libreswan + xl2tpd + bundled chap-manager, env-configured). Requires the xl2tpd-libreswan image to be published on DockerHub first. - README: AL2023 is the recommended/tested AMI now. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
alexzhangs
force-pushed
the
feature/al2023-migration
branch
from
June 11, 2026 06:21
335f03e to
8410ea2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Amazon Linux 2 reaches end of support on 2026-06-30. Existing stacks keep running (security-update cliff, not an outage cliff), but new deployments should land on AL2023.
What
kernel-defaultAMIs (al2023-ami-2023.12.20260608.0-kernel-6.1), x86_64 + arm64 in every region. Generated with the AL2023-updatedcfn/vpn/amilogic (feat(cfn/vpn/ami): fetch AL2023 AMIs instead of Amazon Linux 2 xsh-lib/aws#14); same key order/indentation, so thex-file-injectanchors contract is intact.yum install -y dockerfrom the AL2023 core repos (amazon-linux-extrasis AL2-only and gone).public_ip/private_ip.yum install -y aws-cfn-bootstrap—updatewas a silent no-op when the helper scripts aren't preinstalled, leaving thecfn-signalEXIT trap broken.alexzhangs/xl2tpd-libreswan(libreswan + xl2tpd + bundled chap-manager, env-configured) — the new standalone image repo that supersedes aws-ec2-xl2tpd, mirroring the aws-ec2-shadowsocks-libev → shadowsocks-libev-v2ray relationship.xl2tpd-libreswanimage being published to DockerHub first (repo needs DOCKERHUB_USERNAME var + DOCKERHUB_TOKEN secret, then a release to trigger ci-docker).Not included / follow-ups
🤖 Generated with Claude Code