Security Group will not show up for EC2 if one with same name exists in VPC about asgard HOT 3 OPEN

I did some more research into this and one possible fix that looks quite uninvasive is to change the 'key' property of the Entity SecurityGroup to groupId instead of groupName.
I will submit a pull request with the required changes.

from asgard.

This is a known problem, but it hasn't bothered us enough yet to fix. You are correct about the cache being keyed by name rather than id. The invasive part is finding all the cache lookups and making sure they are all done by id. In many EC2 cases you won't even have ids. You may need to do a lookup or have caches for name and id.
A pull request would be welcomed.

from asgard.

I agree with this suggestion and could use this functionality as well. In our case, we might also have multiple VPCs (since EC2-Classic is going away). I suggest the following changes:

• change all internal code security group references to use groupId
• make sure all generated url link references are groupId as well
• change the UI presentation for security groups to include a scoped name as well as an Id. Something like: "tools:secure [sg-1234]"

from asgard.