Fix panic when security group ID is not known

[rifelpet]

Fixes #17421

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hakman]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[homie-du]

@rifelpet @hakman

I’m on kops v1.32.1. kops get assets --copy still fails because kOps calls DescribeSecurityGroupRules with the unsupported vpc-id filter.

Error: error running tasks: deadline exceeded executing task SecurityGroup/api-elb.homie-test.com. Example error: operation error EC2: DescribeSecurityGroupRules, https response error StatusCode: 400, RequestID: efffabdb-fe73-411e-8415-b6557d0246eb, api error InvalidParameterValue: The filter 'vpc-id' is invalid

According to the AWS SDK, DescribeSecurityGroupRules only accepts three filters:

• group-id
• security-group-rule-id
• tag:<key>

Please cherry-pick commit ca9fa29 (from PR #17432) to release-1.32 and drop the vpc-id filter so v1.32 users can mirror assets without this error.

Thanks!

[diane-devops]

@rifelpet @hakman
DescribeSecurityGroupRulesInput type does not allow vpc-id and group-name in filters.
Security group IDs are unique in all of accounts, specifying just the security group ID should be enough.

https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2#DescribeSecurityGroupRulesInput