Fix EC2 security groups where SSH inbound rule isn't first #71
Conversation
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
|
Great fix thanks @ayumi |
lanej
added a commit
that referenced
this pull request
Mar 13, 2015
Fix EC2 security groups where SSH inbound rule isn't first
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue with provisioning EC2 instances where security group's SSH inbound 0.0.0.0/0 permission is not at index 0.
Repro:
gems/excon-0.44.4/lib/excon/middlewares/expects.rb:6:inresponse_call': Duplicate => the specified rule "peer: 0.0.0.0/0, TCP, from port: 22, to port: 22, ALLOW" already exists (Fog::Compute::AWS::Error)` from fog/aws/models/compute/servers.rb:205This fixes it by checking all ip ranges, not just the first one.