Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Associating on secondary subnet not possible #224

Open
cthorner opened this issue Jul 7, 2015 · 0 comments
Open

Associating on secondary subnet not possible #224

cthorner opened this issue Jul 7, 2015 · 0 comments

Comments

@cthorner
Copy link

cthorner commented Jul 7, 2015

Can someone confirm that it is not possible to use the discovery mechanism to associate with a secondary IP address in EC2?

Turning on logging, it looks like the security groups and tags are used for finding the correct server instances, but then the first IP is used even if it does not belong to the security group or tag specified.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cthorner