-
-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does aws_zone has to match the subnet availability zone? #232
Comments
@kayma-hl I am not complete sure why we have splitted those two variables. I doubled checked the docker machine docs for EC2 (https://docs.docker.com/machine/drivers/aws/) and it seems we really have to set the zone paramters. Would you like to propose a PR to replace the logic by a lookup? |
Closed
This was referenced Jul 6, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
by accident I set the aws_zone to "b" but used a subnet_id_runners from availability zone eu-central-1a. As a result no runner was created. So if both variables are related I propose to remove the aws_zone variable and read the availability zone of the subnet via
data aws_subnet runners { id = var.subnet_id_runners }
Best regards
Matthias Kay
Hapag-Lloyd AG
The text was updated successfully, but these errors were encountered: