You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 'VPC security groups per Region' usage value is not correct in combination with VPC sharing. In tested account the result['EC2']['VPC security groups per Region'].get_current_usage()[0].get_value() returns a value over 2500 although there was no quota increase. (default limit is 2500)
Version
awslimitchecker version 10.0.0
Expected Output
Awslimitchecker should not count all VPC security groups available in a region for one account. This number includes SGs that are owned by other accounts if the VPC is shared between accounts. For the correct number of SGs, it should be filtered by the owner account.
Testing Assistance
I'm able to assist in testing pre-release.
The text was updated successfully, but these errors were encountered:
aperov9
added a commit
to aperov9/awslimitchecker
that referenced
this issue
Jan 9, 2021
Bug Report
The 'VPC security groups per Region' usage value is not correct in combination with VPC sharing. In tested account the
result['EC2']['VPC security groups per Region'].get_current_usage()[0].get_value()
returns a value over 2500 although there was no quota increase. (default limit is 2500)Version
awslimitchecker version 10.0.0
Expected Output
Awslimitchecker should not count all VPC security groups available in a region for one account. This number includes SGs that are owned by other accounts if the VPC is shared between accounts. For the correct number of SGs, it should be filtered by the owner account.
Testing Assistance
I'm able to assist in testing pre-release.
The text was updated successfully, but these errors were encountered: