"Exceeded" VPC security groups limit when launching instances with one sg

Hi there,

It sounds like you’ve simply hit your VPC quota limit. In most cases you can simply request a limit increase. First, I’d recommend taking a look at this page in our VPC docs which goes over limits:

https://docs.aws.amazon.com/vpc/latest/userguide/amazon-vpc-limits.html#vpc-limits-security-groups

Here’s how to check your limits in the EC2 console:

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html

AWS-Nate

Any advice on which limit I have hit?
I have read the limits documentation and the limits page in the AWS Console for this account. My problem is that it's not immediately obvious which of the 30+ limits I have hit.

I am fairly certain it's not the stated "Security Group per instance" but I don't have any evidence for the others... My gut feel is that I hit the "vCPU for running instance" but the math didn't work out...

Want to close the loop on this: the problem has been identified in our application that uses SDK.
We failed to clear the Security Group list in between loops, so while I thought I was launching 6 instance with 1 group each; I am in reality launching 1 instance with 1 group, 1 instance with 2 groups... And the 6th instance with 6 groups fails.

The only complaint is that the error message was a little misleading:
This is the error:
"errorCode": "Client.SecurityGroupLimitExceeded",
"errorMessage": "You have exceeded the number of VPC security groups allowed per instance.",

But in reality, we didn't hit the "Security groups per instance" limit (which is 8); we hit the "VPC security groups per elastic network interface" limit (which is 5).

Thanks