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.

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

[1.2.11][ec2][run-instances] secondary-private-ip-address-count - InvalidParameterCombination #613

Closed
marekjagielski opened this issue Jan 27, 2014 · 2 comments
Labels
feature-request A feature should be added or improved.

Comments

@marekjagielski
Copy link

When running command with --secondary-private-ip-address-count 1:

aws ec2 run-instances --image-id ami-eef31499 --security-group-ids sg-bp8eo6dd --user-data data --instance-type t1.micro --subnet-id subnet-14d4uc63 --iam-instance-profile Name=gateway --count 1 --secondary-private-ip-address-count 1 --region eu-west-1 --profile int

I get:

A client error (InvalidParameterCombination) occurred when calling the RunInstances operation: Network interfaces and an instance-level subnet ID may not be specified on the same request

However setting separately --secondary-private-ip-address-count 1:

aws ec2 assign-private-ip-addresses --network-interface-id eni-243a2357 --secondary-private-ip-address-count 1 --region eu-west-1 --profile int

everything goes fine.

@jamesls
Copy link
Member

jamesls commented Jan 16, 2015

Looks like we need to expand on #222 and account for a subnet id being specified.

@jamesls jamesls added the feature-request A feature should be added or improved. label Jan 16, 2015
@kyleknap
Copy link
Contributor

Fixed via referenced merged PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

3 participants