Unable to complete networking for lab 3.1 on AWS

The step is step 20. Running the kubeadm command results in an error. The error in question is that the API server doesn't start up after 4 minutes.

[api-check] The API server is not healthy after 4m0.000596035s

Unfortunately, an error has occurred:
        context deadline exceeded

I cannot post the actual command (even using markdown) because it triggers the "security warning" and doesn't let me complete or save the post.

Looking at the list of running containers, I can see that everything has exited, but the kube-apiserver exited much earlier than the others.

69968c287f221       2b0d6572d062c       4 minutes ago       Exited              kube-scheduler            6                   1de31474026ea       kube-scheduler-cp            kube-system
c6da1e0c66ece       019ee182b58e2       7 minutes ago       Running             kube-controller-manager   5                   a0e85ba5d760b       kube-controller-manager-cp   kube-system
5673ac21b58c7       a9e7e6b294baf       8 minutes ago       Running             etcd                      4                   8b7d62088a2ab       etcd-cp                      kube-system
65c6fecaa8628       95c0bda56fc4d       8 minutes ago       Running             kube-apiserver            3                   1b3c410a20a17       kube-apiserver-cp            kube-system
17de06e593ba9       019ee182b58e2       10 minutes ago      Exited              kube-controller-manager   4                   a0e85ba5d760b       kube-controller-manager-cp   kube-system
e50e422e1bd26       a9e7e6b294baf       10 minutes ago      Exited              etcd                      3                   77d03bb90886d       etcd-cp                      kube-system
3cc5053d89f5e       95c0bda56fc4d       13 minutes ago      Exited              kube-apiserver            2                   0d16d8aa3ba48       kube-apiserver-cp            kube-system

systemctl status kubelet returns

Oct 22 23:25:19 ip-172-31-39-252 kubelet[1747]: E1022 23:25:19.118144    1747 pod_workers.go:1301] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"kube-scheduler\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=kube-scheduler pod=kube-scheduler-cp_kube-system(1375b6ec40472d611c4ee61d3c6ead9a)\"" pod="kube-system/kube-scheduler-cp" podUID="1375b6ec40472d611c4ee61d3c6ead9a"
Oct 22 23:25:19 ip-172-31-39-252 kubelet[1747]: I1022 23:25:19.259756    1747 kubelet_node_status.go:76] "Attempting to register node" node="cp"
Oct 22 23:25:20 ip-172-31-39-252 kubelet[1747]: E1022 23:25:20.193246    1747 kubelet_node_status.go:108] "Unable to register node with API server" err="Post \"https://k8scp:6443/api/v1/nodes\": dial tcp 172.31.39.25:6443: connect: no route to host" node="cp"
Oct 22 23:25:20 ip-172-31-39-252 kubelet[1747]: E1022 23:25:20.193278    1747 controller.go:145] "Failed to ensure lease exists, will retry" err="Get \"https://k8scp:6443/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/cp?timeout=10s\": dial tcp 172.31.39.25:6443: connect: no route to host" interval="7s"
Oct 22 23:25:20 ip-172-31-39-252 kubelet[1747]: E1022 23:25:20.193358    1747 event.go:368] "Unable to write event (may retry after sleeping)" err="Patch \"https://k8scp:6443/api/v1/namespaces/default/events/cp.1870f2f1aaacd354\": dial tcp 172.31.39.25:6443: connect: no route to host" event="&Event{ObjectMeta:{cp.1870f2f1aaacd354  default    0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] [] []},InvolvedObject:ObjectReference{Kind:Node,Namespace:,Name:cp,UID:cp,APIVersion:,ResourceVersion:,FieldPath:,},Reason:NodeHasNoDiskPressure,Message:Node cp status is now: NodeHasNoDiskPressure,Source:EventSource{Component:kubelet,Host:cp,},FirstTimestamp:2025-10-22 23:09:34.066357076 +0000 UTC m=+0.514441053,LastTimestamp:2025-10-22 23:09:34.21019066 +0000 UTC m=+0.658274529,Count:2,Type:Normal,EventTime:0001-01-01 00:00:00 +0000 UTC,Series:nil,Action:,Related:nil,ReportingController:kubelet,ReportingInstance:cp,}"
Oct 22 23:25:24 ip-172-31-39-252 kubelet[1747]: E1022 23:25:24.178323    1747 eviction_manager.go:292] "Eviction manager: failed to get summary stats" err="failed to get node info: node \"cp\" not found"