Getting Error while creating EKS cluster in AWS Playground using CLI

Hi , while i am trying to create a EKS cluster using CLI in AWS Playground Labs I am getting following error , the command I am using is

eksctl create cluster --name eks-demo1 --version 1.21 --region us-west-2 --nodegroup-name default-ng --node-type t3.micro --nodes 1

And the error I am getting is, can someone please look into this issue?

2022-09-16 05:47:18 [✖]  AWS::EC2::RouteTable/PrivateRouteTableUSEAST1A: CREATE_FAILED – "Resource creation cancelled"
2022-09-16 05:47:18 [✖]  AWS::EC2::RouteTable/PrivateRouteTableUSEAST1C: CREATE_FAILED – "Resource creation cancelled"
2022-09-16 05:47:18 [✖]  AWS::EC2::RouteTable/PublicRouteTable: CREATE_FAILED – "Resource creation cancelled"
2022-09-16 05:47:18 [✖]  AWS::EC2::VPCGatewayAttachment/VPCGatewayAttachment: CREATE_FAILED – "Resource creation cancelled"
2022-09-16 05:47:18 [✖]  AWS::IAM::Policy/PolicyCloudWatchMetrics: CREATE_FAILED – "API: iam:PutRolePolicy User: arn:aws:iam::234696253577:user/odl_user_732321 is not authorized to perform: iam:PutRolePolicy on resource: role eksctl-dev-cluster-ServiceRole-1CPYLLR7P31PB with an explicit deny in an identity-based policy"
2022-09-16 05:47:18 [✖]  AWS::IAM::Policy/PolicyELBPermissions: CREATE_FAILED – "API: iam:PutRolePolicy User: arn:aws:iam::234696253577:user/odl_user_732321 is not authorized to perform: iam:PutRolePolicy on resource: role eksctl-dev-cluster-ServiceRole-1CPYLLR7P31PB with an explicit deny in an identity-based policy"

@Prabhjyot_KodeKloud Hi, can you please suggest to whom I can tag here to look into this issue?

Hey sure, we are getting this checked.

Hi Jasmeet,

When you are using eksctl cli it automatically tries to configure cloudwatch metrics and currently cloudwatch service is not enabled in AWS playground so that is the reason you are getting this error. As workaround you can create EKS cluster using AWS console

Hi saikrishnayerramsett ,
Thanks for your reply but unfortunately when we tried to create EKS cluster from AWS Console it also throws errors at some points when we try to deploy something. But I was able to create cluster using Console…

Facing the same issue here:


This will be possible in a near future?

Hi @Richardbmk,
Please check the above comment.

Definitely, Yes.

I’m also getting the same error. The reason is while creating EKS cluster, AWS need a IAM user but by default create and view access to IAM service is blocked for us