-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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-vpc-endpoints does not support service-name filter #8391
Comments
Hi @kchik-confluent, thanks for reaching out. I had some trouble reproducing this behavior. Could you provide debug logs of this behavior? You can get debug logs by adding |
|
Thanks for your patience. I'm still not able to reproduce the issue (nor my colleague on macOS), but another AWS user reported it as well. I have reached out to the service team about this behavior. In the meantime, could you try this command using Boto3 to check if it's just an issue with the CLI? |
Could you try the following workaround?
|
This issue was fixed by the service team, and the workaround should no longer be required. If you're still having this problem on the most recent version of the CLI, feel free to reopen the issue. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the bug
Getting
Unsupported filter attribute: [service-name]
when using thedescribe-vpc-endpoints
command, which contradicts the documentation.The VPC endpoint exists and can be queried from the AWS console using the service name filter.
Other filters work as intended, only
service-name
results in an error.Cannot reproduce using other AWS accounts. The
service-name
filter works as intended when another account is used.Expected Behavior
The command returns a list of VPC endpoints that have the service name
com.amazonaws.us-west-2.s3
Current Behavior
Reproduction Steps
Run
aws ec2 describe-vpc-endpoints --filters "Name=service-name,Values=com.amazonaws.us-west-2.s3"
Possible Solution
No response
Additional Information/Context
Traceback from using
--debug
CLI version used
2.14.5
Environment details (OS name and version, etc.)
macOS Monterey 12.7.1
The text was updated successfully, but these errors were encountered: