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

--associate-public-ip-address option with --security-group-ids #504

Closed
ryuzee opened this issue Nov 22, 2013 · 1 comment · Fixed by #506
Closed

--associate-public-ip-address option with --security-group-ids #504

ryuzee opened this issue Nov 22, 2013 · 1 comment · Fixed by #506

Comments

@ryuzee
Copy link

ryuzee commented Nov 22, 2013

#501 #502

when I ran command with --subnet-id, it works fine but when I add --security-group-ids, it does not work.
It seems that same modifications are required.
@garnaat garnaat mentioned this issue Nov 23, 2013
Merged
@garnaat
Copy link
Contributor

garnaat commented Nov 23, 2013

Yes, sorry about that. The RunInstances request has become quite complicated.

jamesls added a commit that referenced this issue Nov 26, 2013
@jamesls
Merge branch 'release-1.2.6'
762b925 
* release-1.2.6: (37 commits)
  Bumping version to 1.2.6
  Bump bcdoc version
  Update changelog with latest features
  Update changelog with configure list PR
  Correct grammar/typos in comments
  Added create-environment example for elastic beanstalk
  Updated examples from the doc team
  Add docs for the aws configure list command
  Add an 'aws configure list' command
  Remove unused function
  Update ec2 modify-instance-attribute example
  Notify user when broken symlinks are encountered
  Add issue 484 to changelog
  Only document the simpler shorthand syntax
  Fix infinite loop in python3
  Pull up structure(scalar) bools into top level args
  Add more shorthand syntax support
  If we are constructing a NetworkInterfaces structure for the user in run-instances, we need to make sure that any security groups specified via --security-group-ids are moved into the NetworkInterfaces structure.  Otherwise we get a client error from EC2.  Fixes #504.
  Update changelog to add issue 501
  Add entry to changelog for fix
  ...
@ryuzee ryuzee mentioned this issue Dec 2, 2013
Closed
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

Successfully merging a pull request may close this issue.

Move --security-group-ids value to NetworkInterfaces structure if necessary
2 participants
@garnaat @ryuzee