-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
"Network interfaces and an instance-level subnet ID may not be specified on the same request" #518
Comments
http://drewblas.com/2012/08/24/aws-vpc-error-client-invalidparametercombination/ Luckily, my company has premium AWS support and a quick 10 minute chat got the answer I needed. You must use the --network-attachment param, which takes the place of --group, --private-ip-address, and --subnet The resulting command looks like this: ec2-run-instances ami-abc123 Good luck, I hope this helps! |
The comment above from @JPalmerGithub applies to the legacy EC2 CLI tool, not AWS CLI. The specific issue with using |
just confirmed it works as expected with 1.2.6 (I was running 1.2.5). Thanks! |
Thank You & Best Regards: JPalmer |
This problem has reappeared. I just upgraded from 1.3.2 to 1.3.21 and both manifest this problem. These are the parameters I am passing in to
|
I'm also running into this issue on 1.5.3 |
same aws ec2 run-instances --key-name csbeanstalk --security-groups ****-v1 --instance-type m3.medium --associate-public-ip-address --image-id ami-d05e75b8 --placement Tenancy=dedicated --subnet-id subnet-*********a A client error (InvalidParameterCombination) occurred when calling the RunInstances operation: Network interfaces and an instance-level security groups may not be specified on the same request |
the new --associate-public-ip-address introduced in #479 doesn't seem to work for VPC instances
the error is noted in the title above
The text was updated successfully, but these errors were encountered: