|
|
|
|
|
|
by Waterluvian
2478 days ago
|
|
|
Purely from speculation: AWS console looks and feels like it was designed and built by a ton of different teams that did a poor job working with and empowering each other. When services intermingle the console gets really confusing. Like "why am I in EC2? I'm making security groups and have zero EC2 systems." Any truth to this sense I get? |
|
|
Security Groups were initially an EC2 only concept. You couldn't write security groups for SQS or S3, and they came about alongside EC2.
Obviously EC2 is no longer the only service that utilize security groups, but it's an artifact of when they were.
(I'm not saying this is how it should be, just answering the 'why' part of the question ;))