Problem Creating a cluster in an AWS VPC with CloudFormation and the default CoreOS cluster template

141 views
Skip to first unread message

hapn...@gmail.com

unread,
Mar 2, 2015, 7:28:53 PM3/2/15
to coreo...@googlegroups.com
It appears that CoreOS has a problem with its use of AutoScale when used to create a cluster in a VPC. The correct VpcId and SubnetId parameters for the VPC have been provided to CloudFormation create. It appears that the attributes CoreOSServerAutoScale uses doesn't work for a VPC. You may want to update your docs with an example of a template that works for a VPC cluster.

15:57:51 UTC-0800CREATE_FAILEDAWS::AutoScaling::AutoScalingGroupCoreOSServerAutoScaleThe specified instance type can only be used in a VPC. A subnet ID or network interface ID is required to carry out the request. Launching EC2 instance failed.



Reply all
Reply to author
Forward
0 new messages