Replace or Augment EC2_SECURITY_GROUP_RULES_PER_GROUP_LIMIT Usage with Service Quotas Information

[bflad]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Certain testing requires knowing account/region specific quotas about rules per EC2 Security Group. Currently the testing uses a default of 50 with an override via the EC2_SECURITY_GROUP_RULES_PER_GROUP_LIMIT environment variable. The Service Quotas service does provide this information, e.g.

        {
            "ServiceCode": "vpc",
            "ServiceName": "Amazon Virtual Private Cloud (Amazon VPC)",
            "QuotaArn": "arn:aws:servicequotas:us-west-2:--OMITTED--:vpc/L-0EA8095F",
            "QuotaCode": "L-0EA8095F",
            "QuotaName": "Inbound or outbound rules per security group",
            "Value": 60.0,
            "Unit": "None",
            "Adjustable": true,
            "GlobalQuota": false
        },

We should replace or augment the existing handling to try an automatically lookup the correct quota for the testing.

Affected Resource(s)

• aws_security_group

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.