3 ms·
There’s zero reason why AWS can’t pop up a warning if it detects this behavior though. It should clearly explain the implications to the end user. I mean EKS ha
by SOLAR_FIELDS 11mo ago
There’s zero reason why AWS can’t pop up a warning if it detects this behavior though. It should clearly explain the implications to the end user. I mean EKS has all sorts of these warning flags it pops up on cluster health there’s really no reason why they can’t do the same here.
- Spivak 11mo agoI am 100% in agreement, they could even make adding endpoints part of the VPC creation wizard.
- otterley 11mo agoIt's already in there!
- Spivak 11mo agoFantastic! Shows how long it's been since I've made a VPC by clicking around in the GUI.
- raw_anon_1111 11mo agoHow much good does that do if you are using IAC instead of the console - as they are doing? I wouldn’t even think about doing ClickOps. I’ve worked with AWS for 8 years and I doubt I’ve ever created a resource manually in the console.
- snoman 11mo agoThe second someone doesn’t pay attention to that warning and suffers an exfiltration, like the cap1 s3 incident, it’s aws’ fault as far as the media is concerned.
- mystifyingpoi 11mo agoTo be fair, while EKS warnings are useful, I've grown a habit to ignore them completely, since I've seen every single RDS cluster littered with "create a read replica please" and "enable performance insights" bs warnings.