Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Comments

@RothAndrew
Copy link

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:

AvailabilityZone:
        Fn::Select:
        - '0'
        - Fn::GetAZs:
            Ref: AWS::Region

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.

@nrdlngr
Copy link

nrdlngr commented Jun 18, 2018

The VPC template creates subnets in 3 AZs. You specify the subnets when you create the EKS cluster.

You must specify at least 2 subnets, so specify 2 of the subnets that are in the supported AZs in your error message.

@nisartahir
Copy link

I got the same error using:

aws eks create-cluster --name eks-cluster --role-arn arn:aws:iam::123456789:role/eksServiceRole --resources-vpc-config subnetIds=subnet-adf123,subnet-e512b456,subnet-cbd37789,securityGroupIds=sg-51234567

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

The cluster can now be created

@bchav
Copy link

bchav commented Aug 8, 2018

EKS is currently only available in a subset of us-east-1 availability zones.

For all accounts, us-east-1a, 1b, 1c, and 1d are randomized. However, despite this randomization, EKS is always available in 3 of these 4 AZs.

EKS will be expanding into additional zones in us-east-1 this year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants