You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An error occurred (UnsupportedAvailabilityZoneException) when calling the CreateCluster operation: Cannot create cluster 'rotha-dev-devel' because us-east-1c, the targeted availability zone, does not currently have sufficient capacity to support the cluster.
#8
Closed
RothAndrew opened this issue
Jun 18, 2018
· 3 comments
I've been following the AWS EKS Getting Started Guide to the letter, and when trying to run the aws eks create-cluster step I am receiving the following error:
An error occurred (UnsupportedAvailabilityZoneException) when calling the CreateCluster operation: Cannot create cluster 'rotha-dev-devel' because us-east-1c, the targeted availability zone, does not currently have sufficient capacity to support the cluster. Retry and choose from these availability zones: us-east-1a, us-east-1b, us-east-1d
How do I specify which availability zone the cluster will be deployed to? If I'm understanding correctly, the chosen AZ is specified when creating the VPC.
The amazon-eks-vpc-sample.yaml file used has the following section in it:
This is repeated 3 times, one for each Subnet. The only change is the '0' gets changed to '1' and '2'. I'm guessing the change needs to go here, but I have no idea what needs to be put there instead.
The text was updated successfully, but these errors were encountered:
Cloud Formation creates the 3rd subnet (eks-vpc-Subnet03) in us-east-1c.
I deleted that subnet and created the subnet again (eks-vpc-Subnet03) in us-east-1d
I've been following the AWS EKS Getting Started Guide to the letter, and when trying to run the
aws eks create-cluster
step I am receiving the following error:How do I specify which availability zone the cluster will be deployed to? If I'm understanding correctly, the chosen AZ is specified when creating the VPC.
The amazon-eks-vpc-sample.yaml file used has the following section in it:
This is repeated 3 times, one for each Subnet. The only change is the
'0'
gets changed to'1'
and'2'
. I'm guessing the change needs to go here, but I have no idea what needs to be put there instead.The text was updated successfully, but these errors were encountered: