search

hashicorp / terraform-aws-consul

A Terraform Module for how to run Consul on AWS using Terraform and Packer
Apache License 2.0
401 stars 484 forks source link

Latest public AMIs not available (Consul Connect) #76

Closed awesome closed 6 years ago

awesome commented 6 years ago

Was making initial experiments with this module and got an AMI-not-found error by setting the var ami_id = "ami-0cefe1c6ca6cb38f6". Double checked via AWS web-console for us-east-1 and us-east-2 and did not find public AMIs referenced in _docs: https://github.com/hashicorp/terraform-aws-consul/blame/v0.3.8/_docs/amazon-linux-ami-list.md#L19

Via AWS web-console looked up owner account 562637147889 filtered to 2018 which resulted with no public Consul AMIs… https://github.com/hashicorp/terraform-aws-consul/blame/v0.3.8/main.tf#L33

This is probably a backlog issue, but thought mentioning it would be helpful for those wanting to easily try Consul Connect or new UI without using Packer to build AMIs.

Error: Error applying plan:

2 error(s) occurred:

* module.consul.module.consul_servers.aws_launch_configuration.launch_configuration: 1 error(s) occurred:

* aws_launch_configuration.launch_configuration: Expected to find a Root Device name for AMI (ami-0cefe1c6ca6cb38f6), but got none
* module.consul.module.consul_clients.aws_launch_configuration.launch_configuration: 1 error(s) occurred:

* aws_launch_configuration.launch_configuration: Expected to find a Root Device name for AMI (ami-0cefe1c6ca6cb38f6), but got none
brikis98 commented 6 years ago

Thanks for the report. Something has indeed broken with our AMI publishing code. I'll look into it.

brikis98 commented 6 years ago

OK, took a few tries, but I think this was fixed by #77 and #78.