Open dstynchula opened 8 years ago
The interface defaults to t2.micro which according to this requires a VPC: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html As a quick fix, changing the default selection would work for the time being, but ultimately, adding the ability to select/create a VPC would be really helpful.
When attempting to create a remote deployment target in AWS using both the coreOS and Kubernetes clusters, I receive similar errors: Provisioning cluster in Amazon EC2 AMI Used: ami-212e0911 The specified instance type can only be used in a VPC. A subnet ID or network interface ID is required to carry out the request. (VPCResourceNotSpecified)