Empty AMIs list for eu-north-1 region

[hmlkao]

I followed Terraform Getting Started Guide with module and I have encountered two problems:

1. "aws_region" is not a valid argument This issue may not be related to this repository but I didn't found link where I can report it...

   $ terraform apply
   Error: module "consul": "aws_region" is not a valid argument

2. When I set own region in aws provider ("eu-north-1") empty AMIs list is returned.

   
   $ terraform apply
   data.template_file.user_data_server: Refreshing state...
   data.template_file.user_data_client: Refreshing state...
   data.aws_region.current: Refreshing state...
   data.aws_vpc.default: Refreshing state...
   data.aws_iam_policy_document.auto_discover_cluster: Refreshing state...
   data.aws_iam_policy_document.auto_discover_cluster: Refreshing state...
   data.aws_iam_policy_document.instance_role: Refreshing state...
   data.aws_ami.consul: Refreshing state...
   data.aws_iam_policy_document.instance_role: Refreshing state...
   data.aws_subnet_ids.default: Refreshing state...

Error: Error refreshing state: 1 error(s) occurred:

• module.consul.data.aws_ami.consul: 1 error(s) occurred:

• module.consul.data.aws_ami.consul: data.aws_ami.consul: Your query returned no results. Please change your search criteria and try again.

  
  With "eu-west-1" it works as expected.

[josh-padnick]

Regarding the aws_region issue, the Getting Started Guide is wrong. If you look at the consul-cluster module's variables.tf file, you'll see that there is no aws_region variable defined. Instead, it's enough to supply the AWS region to the provider block.

Regarding the AMI issue, it looks like eu-north-1 just launched in December 2018, and the main issue is that we haven't issued a new release since Nov 16, 2018.

@Etiene Could you look into adding support for eu-north-1 by issuing a new release?