This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 121
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
aws: allow instances with no public_ip
Fixes #16
- Loading branch information
1 parent
d970d96
commit 51a8c13
Showing
1 changed file
with
3 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
51a8c13
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only have a second to really glance at this and I can run a test in a little bit, but won't this fail if you're running Terraform + Ansible from outside the VPC and without a VPN which is where the situation arose in the first place. You'll get host communication failures since you're defaulting to the private_ip which is inaccessible in that situation (which is actually how I ran into this in the first place).