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

aws ec2 attach-internet-gateway: The parameter vpcId is not recognized #16

Closed
satotech opened this issue Dec 29, 2012 · 4 comments
Closed
Milestone

Comments

@satotech
Copy link

When using tab completion with attach-internet-gateway it shows --vpc-id as a possible option, but when I try to use it, I get this error below.

$ aws ec2 attach-internet-gateway --vpc-id vpc-XXXXXXXX --internet-gateway-id igw-XXXXXXXX
{
    "Response": {
        "Errors": {
            "Error": {
                "Message": "The parameter vpcId is not recognized", 
                "Code": "UnknownParameter"
            }
        },
        "RequestID": "64ffb471-ef85-4a77-a542-6b7141ea04d7"
    }
}
A client error (UnknownParameter) occurred: The parameter vpcId is not recognized
@satotech
Copy link
Author

This page shows aws-cli support for Amazon VPC, but Amazon VPC is not included in README.md. Which is correct?

@jdub
Copy link

jdub commented Jan 1, 2013

Hmm, based on #13, I suspect there's a bunch of camelCase to InitialCamelCase fixes to be made throughout the VPC API support.

@garnaat
Copy link
Contributor

garnaat commented Jan 3, 2013

@satotech - aws-cli does support VPC but all of the VPC functionality is really part of EC2. There is not a separate API or endpoint. However, I will update the README.md to make it clear that VPC support is included.

Also, as @jdub comments, there are a number of cases where the parameter name is getting sent to the service with incorrect case. I will have a new release out today that addresses these issues as well as some others.

Thanks!

@garnaat
Copy link
Contributor

garnaat commented Jan 3, 2013

This should be fixed in the 0.4.5 release and in the develop branch.

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

No branches or pull requests

3 participants