From 0ecefc6563c12867a8be047f3ea42758642e8228 Mon Sep 17 00:00:00 2001 From: Jianan Wang Date: Tue, 12 Aug 2025 11:04:23 -0700 Subject: [PATCH] fix(docs): aws network-interfaces is an array --- docs/content/getting-started/kamaji-aws.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/getting-started/kamaji-aws.md b/docs/content/getting-started/kamaji-aws.md index 33ac5ae..02d8c99 100644 --- a/docs/content/getting-started/kamaji-aws.md +++ b/docs/content/getting-started/kamaji-aws.md @@ -359,7 +359,7 @@ cat <> worker-user-data.sh $JOIN_CMD EOF -aws ec2 run-instances --image-id $WORKER_AMI --instance-type "t2.medium" --user-data $(cat worker-user-data.sh | base64 -w0) --network-interfaces '{"SubnetId":'"'${KAMAJI_PRIVATE_SUBNET_ID}'"',"AssociatePublicIpAddress":false,"DeviceIndex":0,"Groups":[""]}' --count "1" +aws ec2 run-instances --image-id $WORKER_AMI --instance-type "t2.medium" --user-data $(cat worker-user-data.sh | base64 -w0) --network-interfaces '[{"SubnetId":'"'${KAMAJI_PRIVATE_SUBNET_ID}'"',"AssociatePublicIpAddress":false,"DeviceIndex":0,"Groups":[""]}]' --count "1" ``` We have used user data to run the `kubeadm join` command on the instance boot. This will make sure that the worker node will join the cluster automatically.