4 ms·
(One of the authors here) That's absolutely true. Not easy to summarize the hard work involved on all sides in a short title: finding an issue, communicating it
by stefreak 3y ago
(One of the authors here) That's absolutely true. Not easy to summarize the hard work involved on all sides in a short title: finding an issue, communicating it to the security team and then resolving the issue.
A slightly longer version of 'this': AWS really swiftly acknowledged the issue and fixed it in the latest version of AWS CDK. In case you use the `eks.Cluster` component of the AWS CDK, and you use AWS CDK <v2.80.0 or <v1.202.0 you are affected by this issue, Update the CDK to resolve it.
If you want to learn more about what the issue was exactly, I'd be happy if you give the blog post a read :)
- leetrout 3y agoYou are going for click bait and the post you are replying to is reacting to that to save those of us who wont click through.
- _8j50 3y agoTotally agree, I was expecting AWS to have done something shocking in response to their finding. No need to undermine their own work with a clickbait title.