Eksctl: AWS::AutoScaling::AutoScalingGroup/NodeGroup: CREATE_FAILED

[xakraz]

What happened?

While trying to create a cluster:

eksctl create cluster \          
--name poc-1 \  
--region eu-west-3 \
--nodes=3 \
--auto-kubeconfig \
--node-type=c4.xlarge \
--ssh-access --ssh-public-key=/PATH/TO/PUBLIC_KEYpub \
--full-ecr-access 

It through the following error when trying to run the 2nd stack (the node-group)

[✖]  AWS::AutoScaling::AutoScalingGroup/NodeGroup: CREATE_FAILED – "You must use a valid fully-formed launch template. The requested configuration is currently not supported. Please check the documentation for supported configurations. (Service: AmazonAutoScaling; Status Code: 400; Error Code: ValidationError; Request ID: cb6144fc-200b-11ea-b20c-a56135770c68)"

What you expected to happen?

Just run the Cloudformation stack without error

How to reproduce it?

• [x] I have checked that my AWS IAM user has all the needed permissions. (AdminFullAccess last check).
• [x] Download the eksctl
• [x] Run the specified command

Anything else we need to know?

• OS: Linux
• Kernel: 5.4.2-1-MANJARO
• Downloaded binary from Github Release page
• AWS "shared" credentials from config file (named profile)

Versions
Please paste in the output of these commands:

$ eksctl version
[ℹ]  version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.9.0"}

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3", GitCommit:"b3cbbae08ec52a7fc73d334838e18d17e8512749", GitTreeState:"clean", BuildDate:"2019-11-18T14:56:51Z", GoVersion:"go1.12.13", Compiler:"gc", Platform:"linux/amd64"}
The connection to the server localhost:8080 was refused - did you specify the right host or port?

Logs

eksctl get clusters -v 4  
2019-12-16T15:35:10+01:00 [▶]  role ARN for the current session is "arn:aws:iam::392366066546:user/cli-xavier"
NAME    REGION
poc-1   eu-west-3

...
[ℹ]  deploying stack "eksctl-poc-1-nodegroup-ng-59ebe4d4"
[✖]  unexpected status "ROLLBACK_COMPLETE" while waiting for CloudFormation stack "eksctl-poc-1-nodegroup-ng-59ebe4d4"
[ℹ]  fetching stack events in attempt to troubleshoot the root cause of the failure
[!]  AWS::IAM::Role/NodeInstanceRole: DELETE_IN_PROGRESS
[!]  AWS::IAM::InstanceProfile/NodeInstanceProfile: DELETE_IN_PROGRESS
[!]  AWS::EC2::SecurityGroup/SG: DELETE_IN_PROGRESS
[!]  AWS::EC2::LaunchTemplate/NodeGroupLaunchTemplate: DELETE_IN_PROGRESS
[!]  AWS::EC2::SecurityGroupIngress/SSHIPv4: DELETE_IN_PROGRESS
[!]  AWS::EC2::SecurityGroupEgress/EgressInterCluster: DELETE_IN_PROGRESS
[!]  AWS::EC2::SecurityGroupIngress/IngressInterClusterCP: DELETE_IN_PROGRESS
[!]  AWS::EC2::SecurityGroupEgress/EgressInterClusterAPI: DELETE_IN_PROGRESS
[!]  AWS::EC2::SecurityGroupIngress/SSHIPv6: DELETE_IN_PROGRESS
[!]  AWS::EC2::SecurityGroupIngress/IngressInterClusterAPI: DELETE_IN_PROGRESS
[!]  AWS::EC2::SecurityGroupIngress/IngressInterCluster: DELETE_IN_PROGRESS
[✖]  AWS::AutoScaling::AutoScalingGroup/NodeGroup: CREATE_FAILED – "You must use a valid fully-formed launch template. The requested configuration is currently not supported. Please check the documentation for supported configurations. (Service: AmazonAutoScaling; Status Code: 400; Error Code: ValidationError; Request ID: cb6144fc-200b-11ea-b20c-a56135770c68)"
[ℹ]  1 error(s) occurred and cluster hasn't been created properly, you may wish to check CloudFormation console
[ℹ]  to cleanup resources, run 'eksctl delete cluster --region=eu-west-3 --name=poc-1'
[✖]  waiting for CloudFormation stack "eksctl-poc-1-nodegroup-ng-59ebe4d4" to reach "CREATE_COMPLETE" status: ResourceNotReady: failed waiting for successful resource state
[✖]  failed to create cluster "poc-1"

https://gist.github.com/xakraz/216f9718c615dca206d6e5d9f5a8813e

[xakraz]

Still not working with

$ eksctl version 

[ℹ]  version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.11.1"}

:cry:

[xakraz]

Issue was due to the node-type ...

[shravspy]

How did you resolve it ?

[trnaviwala]

How did you resolve it ?

I faced the same error - I had set the node-type to t2.micro but it isn't an option in my selected region - replaced with t3.micro and it solved the issue.