Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

--private-ip-address option at run-instances does not work #520

Closed
ryuzee opened this Issue Dec 2, 2013 · 1 comment

Comments

Projects
None yet
2 participants

ryuzee commented Dec 2, 2013

I think --private-ip-address option can accept private ip address to assign.
but when I ran the command as follows,

aws ec2 run-instances
--image-id ami-b1fe9bb0
--subnet-id subnet-00xxxxxx
--key-name keypair1
--security-group-ids sg-yyyyyy
--region ap-northeast-1
--instance-type t1.micro
--associate-public-ip-address
--private-ip-address 10.0.0.222
--debug

Error message was show as follows.

ClientError: A client error (InvalidParameterCombination) occurred: Network interfaces and an instance-level private IP address may not be specified on the same request

On the other hand, when executed same command by ec2-api-tools, it worked fine.

Bellow is the differences in API request between awscli and ec2-api-tools

ec2-api-tools

NetworkInterface.1.PrivateIpAddresses.1.Primary=true&
NetworkInterface.1.PrivateIpAddresses.1.PrivateIpAddress=10.0.0.222&

awscli

PrivateIpAddress=10.0.0.222&

This seems to be same as #504.

Contributor

garnaat commented Dec 2, 2013

It does work as long as you do not specify it in combination with the --associate-public-ip-address. If both are specified, we end up with a similar conflict as that discovered in #504.

I'm working on a fix now. Thanks for reporting.

@ghost ghost assigned garnaat Dec 2, 2013

@garnaat garnaat closed this in 7edca37 Dec 2, 2013

@jamesls jamesls added a commit that referenced this issue Dec 6, 2013

@jamesls jamesls Merge branch 'release-1.2.7'
* release-1.2.7: (21 commits)
  Bumping version to 1.2.7
  Update changelog with the latest changes
  Change mututally to mutually
  Allow the --protocol option of ec2 create-network-acl-entry command to accept tcp|udp|icmp|all in addition to the numeric protocol numbers.  The docs for the command already say it does this but the actual EC2 operation supports only integer values.
  Fix bug when filtering s3 locations
  Clean up existing filter unit tests
  Add unittest for website redirect location
  Add unit test for recursive download
  Remove extraneous log statements.
  Fix an assumption in argprocess.py that all map types will have an enum of possible keys.  Also change the import of json to come from the botocore.compat module and also set the object_pairs_hook to use OrderedDict so unit tests can be compared properly.  Dependent on boto/botocore#185. Fixes #407.
  Add tests that verify what ops were called
  Add a short circuit path for listing a specific s3 object
  Remove newline between task fail and error messages
  Add attributes to exception in errorhandler
  Remove src/dest resource existence check
  If --private-ip-address is specified with any other options that require the creation of a NetworkInterfaces structure, move the value of --private-ip-address into the NetworkInterfaces structure.  Fixes #520.
  Log CLI/botocore version in the debug logs
  Add changelog entry for issue 516
  Handle a list of strings from a dict in text output
  Remove tutorial in favor of user guide
  ...
6b62d91
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment