Future Development idea - have Security Groups use "reference" container
We have a setup where there may be multiple Security Groups in different VPCs, Regions, or Accounts that we have to put in the same IP information.
For example, AWS Admin "Joe" has IP of 126.96.36.199, and we have to enter this in seven different Security Groups.
My question is this, are there any thoughts of improving this in the future by centralizing it somewhat? So in this example, there would be a "Central Admin" group/file/config setting somewhere that we enter "Joe" and "188.8.131.52" once, and in all the seven different security groups, we just put in the reference "Joe".
That way, if Joe's IP changes, you just have to change it in one place.
Just thought this might be a good enhancement, simpler management of this type of thing...any thoughts/plans/critiques?
Closing this thread, it somehow ended up in wrong forum
East/west security & Transit GatewayAccepted Answerasked 2 years ago
Querying nested json arrays in Cloudtrail logs to find open security groups - Is there a better way?asked 3 months ago
New account has subnets, security groups, and VPCs in 17 regions.asked 2 months ago
Should I use one account or multiple accounts?Accepted Answerasked 4 months ago
Networking and Security Groups issueasked 3 years ago
[ECS] Do you need to configure security groups to communicate over localhost?Accepted Answerasked 6 months ago
Future Development idea - have Security Groups use "reference" containerasked 3 years ago
How to have multiple VPCs in different AWS accounts use the same physical AWS Direct Connect circuit.Accepted Answerasked 4 years ago
Can metric filter stats between different AWS regions be aggregated?asked 3 months ago
IAM users/roles/groups policies reportsAccepted Answerasked 6 months ago