Closed kinghuang closed 6 years ago
Thanks for pointing this out! Those templates are unmaintained and have a variety of problems: they use coreos-cloudinit (deprecated) to enable etcd2 and fleet (both removed from Container Linux). I've removed the "Launch Stack" buttons from the EC2 docs page in https://github.com/coreos/docs/pull/1255.
The template files are now set to private as well. If needed, #1255 has their original contents. Thanks for reporting.
The Running CoreOS Container Linux on EC2 has links to launch CloudFormation stacks of CoreOS Container Linux. I used the link for us-west-2 HVM to launch a stack with
m5.large
instance types, but was stymied by an error that the image didn't support ENA. It turns out the CloudFormation stack hasami-4c49f22c
(CoreOS-stable-1235.9.0-hvm) instead of `ami-256c375d (CoreOS-stable-1800.5.0-hcm) as listed on the documentation page, and the older image did not support ENA.It looks like the CloudFormation template references old images for all regions. It would be useful if the template referenced the same images as those listed on the documentation page, or if the page noted that the templates use old images.