From 77d3c976440e0eb9f3e4652a56d3bc9aaca9423a Mon Sep 17 00:00:00 2001 From: zizizach Date: Sat, 11 Dec 2021 23:09:55 +0800 Subject: [PATCH] Remove additional whitespace in some commands aws-cli is now rejecting some of the command with double whitespace ``` An error occurred (InvalidInput) when calling the AttachRolePolicy operation: ARN arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly is not valid. ``` --- kubernetes/cloud/amazon/getting-started.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/kubernetes/cloud/amazon/getting-started.md b/kubernetes/cloud/amazon/getting-started.md index 3a6e702..05e4245 100644 --- a/kubernetes/cloud/amazon/getting-started.md +++ b/kubernetes/cloud/amazon/getting-started.md @@ -49,7 +49,7 @@ Follow "Create your Amazon EKS cluster IAM role" [here](https://docs.aws.amazon. # create our role for EKS role_arn=$(aws iam create-role --role-name getting-started-eks-role --assume-role-policy-document file://assume-policy.json | jq .Role.Arn | sed s/\"//g) -aws iam attach-role-policy --role-name getting-started-eks-role --policy-arn arn:aws:iam::aws:policy/AmazonEKSClusterPolicy +aws iam attach-role-policy --role-name getting-started-eks-role --policy-arn arn:aws:iam::aws:policy/AmazonEKSClusterPolicy # create the cluster VPC @@ -92,9 +92,9 @@ chmod +x ./kubectl && mv ./kubectl /usr/local/bin/kubectl # create our role for nodes role_arn=$(aws iam create-role --role-name getting-started-eks-role-nodes --assume-role-policy-document file://assume-node-policy.json | jq .Role.Arn | sed s/\"//g) -aws iam attach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy -aws iam attach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy -aws iam attach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly +aws iam attach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy +aws iam attach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy +aws iam attach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly ``` More details on node permissions [here](https://docs.aws.amazon.com/eks/latest/userguide/worker_node_IAM_role.html) @@ -164,14 +164,14 @@ eksctl delete cluster --name getting-started-eks-1 aws eks delete-nodegroup --cluster-name getting-started-eks --nodegroup-name test aws eks delete-cluster --name getting-started-eks -aws iam detach-role-policy --role-name getting-started-eks-role --policy-arn arn:aws:iam::aws:policy/AmazonEKSClusterPolicy +aws iam detach-role-policy --role-name getting-started-eks-role --policy-arn arn:aws:iam::aws:policy/AmazonEKSClusterPolicy aws iam delete-role --role-name getting-started-eks-role aws iam detach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy -aws iam detach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy -aws iam detach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly +aws iam detach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy +aws iam detach-role-policy --role-name getting-started-eks-role-nodes --policy-arn arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly aws iam delete-role --role-name getting-started-eks-role-nodes aws cloudformation delete-stack --stack-name getting-started-eks -``` \ No newline at end of file +```