fixing UnsupportedAvailabilityZoneException error in us-east-1

Author: dalbhanj

01-path-basics/101-start-here/readme.adoc

@@ -35,7 +35,11 @@ a| image::./deploy-to-aws.png[link=https://console.aws.amazon.com/cloudformation
 
 |===
 
-To open the Cloud9 IDE environment, click on the "Outputs" tab in CloudFormation Console and click on the "Cloud9IDE" URL.
+Accept the default stack name and Click *Next*. You can give Tags such as Key=Name, Value=k8s-workshop, and click *Next*. Make sure
+to check *I acknowledge that AWS CloudFormation might create IAM resources with custom names* and click *Create*.
+
+CloudFormation creates nested stacks and builds several resources that are required for this workshop. Wait until all the resources are created. Once the status for *k8s-workshop* changes to *CREATE_COMPLETE*,
+you can open Cloud9 IDE. To open the Cloud9 IDE environment, click on the "Outputs" tab in CloudFormation Console and click on the "Cloud9IDE" URL.
 
 image:cloudformation-output-tab.png[CloudFormation Output Tab]
 

01-path-basics/102-your-first-cluster/readme.adoc

@@ -68,6 +68,51 @@ echo $EKS_SECURITY_GROUPS
 ```
 If any of those environment variables are blank, please re-run the "Build Script" section of the link:../101-start-here[Cloud9 Environment Setup].
 
+If you receive an *UnsupportedAvailabilityZoneException* error during EKS cluster creation, your account is using an AZ that is currently resource constrained. This occurs mostly in N.Virginia region (us-east-1).
+
+    An error occurred (UnsupportedAvailabilityZoneException) when calling the CreateCluster operation: Cannot create cluster 'k8s-workshop' because us-east-1c, the targeted availability zone, does not currently have sufficient capacity to support the clust er. Retry and choose from these availability zones: us-east-1a, us-east-1b, us-east-1d
+
+If you receive this error, you need to remove the constrained AZ (us-east-1c in my case) from *`EKS_SUBNET_IDS`* environment variable. Follow these steps to update your environment variable
+
+Save the EKS recommended AZ's that is referred in your CLI output in an environment variable.
+Note: you only need two AZ's defined to create EKS cluster
+
+    $ export EKS_VALID_AZS=us-east-1a,us-east-1b
+
+Run the command below to determine subnet ID's
+
+    $ aws ec2 describe-subnets --filters "Name=vpc-id,Values=$EKS_VPC_ID" "Name=availabilityZone,Values=$EKS_VALID_AZS" --query 'Subnets[*].[SubnetId]' --output text
+    subnet-6e672524
+    subnet-18b10e44
+
+Save this output as `*EKS_SUBNET_IDS*` environment variable
+
+    $ export EKS_SUBNET_IDS=subnet-6e672524,subnet-18b10e44
+
+Re-run EKS create-cluster and you should now be able to create cluster. The output should look similar to this
+
+    {
+    "cluster": {
+        "status": "CREATING",
+        "name": "k8s-workshop",
+        "certificateAuthority": {},
+        "roleArn": "arn:aws:iam::123456789012:role/k8s-workshop-EksServiceRo-AWSServiceRoleForAmazonE-1PCSJFFFAF4BL",
+        "resourcesVpcConfig": {
+            "subnetIds": [
+                "subnet-6e672524",
+                "subnet-18b10e44"
+            ],
+            "vpcId": "vpc-a779b4dd",
+            "securityGroupIds": [
+                "sg-d093de9a"
+            ]
+        },
+        "version": "1.10",
+        "arn": "arn:aws:eks:us-east-1:123456789012:cluster/k8s-workshop",
+        "createdAt": 1532734869.147
+    }
+    }
+
 === Create the configuration file
 
 In order to access the cluster locally, use a configuration file (sometimes referred to as a `kubeconfig` file). This configuration file can be created automatically.