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

describe-security-groups not taking vpc-id as filter #3225

Closed
churnikorn opened this issue Mar 28, 2018 · 2 comments
Closed

describe-security-groups not taking vpc-id as filter #3225

churnikorn opened this issue Mar 28, 2018 · 2 comments
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made.

Comments

@churnikorn
Copy link

I first list all group names to ensure what I try to filter by is correct. It works just fine when I filter by vpc id here. The names expected are listed. However, when I attempt to narrow this down by using the --group-names along with the vpc-id as filter, the cli attempts to use a completely different vpc-id than what is passed in.
`
➜ ~ echo ${vpc_id}
vpc-1234123e
➜ ~
➜ ~ aws ec2 describe-security-groups
--filters "Name=vpc-id,Values=vpc-1234123e" --query "SecurityGroups[*].GroupName"
[
"foo",
"default"
]
➜ ~ aws ec2 describe-security-groups --group-names foo
--filters "Name=vpc-1234123e,Values=vpc-1234123e"

An error occurred (InvalidGroup.NotFound) when calling the DescribeSecurityGroups operation: The security group 'foo' does not exist in default VPC 'vpc-9999111e'
`

@kyleknap
Copy link
Contributor

@churnikorn Could you provide debugs for running this command? I suspect this is just service-side behavior where the --group-names and --filters parameters are not compatible for some permutation of it.

@kyleknap kyleknap added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Mar 29, 2018
@kyleknap
Copy link
Contributor

Closing due to inactivity

thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this issue Feb 12, 2022
* Revert "fix: Dependency and runtime mismatch at init now displays the correct error message (aws#3211)"

This reverts commit 17ef26d.

* Revert "feat: SAM Init interactive flow redesign (aws#2958)"

This reverts commit 307ded6.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made.
Projects
None yet
Development

No branches or pull requests

2 participants