Skip to content

Implement egress-only-internet-gateway filtering using attachment.vpc-id #10866

Closed

Description

@minikocha

Describe the feature

While the internet-gateway has multiple filters(attachment.state, attachment.vpc-id, internet-gateway-id, owner-id, tag, tag-key), the egress-only-internet-gateway has only two(tag, tag-key).
Please implement the same filtering on the egress-only-internet-gateway as internet-gateway.

Use Case

It will be easier to search for Egress-Only Internet Gateways associated with a specific VPC.

Proposed Solution

none

Other Information

none

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

CLI version used

2.39.6

Environment details (OS name and version, etc.)

Python/3.14.8 Darwin/27.2.0 exe/arm64

Activity

  1. added
    feature-requestA feature should be added or improved.
    needs-triageThis issue or PR still needs to be triaged.
    on Nov 9, 2026
  2. added
    service-apiThis issue is due to a problem in a service API, not the SDK implementation.
    p3This is a minor priority issue
    and removed
    needs-triageThis issue or PR still needs to be triaged.
    on Nov 9, 2026
  3. RyanFitzSimmonsAK commented on Nov 9, 2026

    @RyanFitzSimmonsAK
    Contributor

    Hi @minikocha, thanks for reaching out. I've forwarded this feedback to the VPC team for their consideration. Please refer to an AWS SDK changelog or the AWS CLI changelog for updates about this going forward. Thanks!

  4. github-actions commented on Nov 9, 2026

    @github-actions
    Contributor

    This issue is now closed. Comments on closed issues are hard for our team to see.
    If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ec2feature-requestA feature should be added or improved.p3This is a minor priority issueservice-apiThis issue is due to a problem in a service API, not the SDK implementation.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions