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

--associate-public-ip-address option does not work #501

Closed
ryuzee opened this issue Nov 22, 2013 · 0 comments · Fixed by #502
Closed

--associate-public-ip-address option does not work #501

ryuzee opened this issue Nov 22, 2013 · 0 comments · Fixed by #502

Comments

@ryuzee
Copy link

ryuzee commented Nov 22, 2013

when runnning aws ec2 run-instances as follows

aws ec2 run-instances --output text
--image-id ami-xxxxxxxx
--key-name ap-southeast-2
--security-group-ids sg-zzzzzzzz
--instance-type t1.micro
--subnet-id subnet-yyyyyyyy
--disable-api-termination
--no-ebs-optimized
--associate-public-ip-address
--count 1
--region ap-southeast-2 --debug

the error message is shown like below.

Network interfaces and an instance-level subnet ID may not be specified on the same request

I compared the https API request between ec2-api-tools and awscli and in this case there are some differences between them as follow. It seems that the paramers such as subnet-id and security-group-ids is not handled correctly.

ec2-api-tools

NetworkInterface.1.AssociatePublicIpAddress=true&
NetworkInterface.1.DeviceIndex=0&
NetworkInterface.1.SecurityGroupId.1=sg-zzzzzzzz&
NetworkInterface.1.SubnetId=subnet-yyyyyyyy&

awscli

NetworkInterface.1.AssociatePublicIpAddress=true&
NetworkInterface.1.DeviceIndex=0&
SecurityGroupId.1=sg-zzzzzzzz&
SubnetId=subnet-yyyyyyyy&

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant