The HUGE Problem with Amazon EKS (SECURITY FLAW)

What most people DONT realize about EKS. Dont open your firm up to risk.

hello avatars, sorry for the delays in getting content out. Had some rough times, dealing with family issues etc. Going off that, i am unpausing billing now that we are hopefully back to regular scheduling. If not, ill pause billing again and run the same playbook.

Today we are going to talk about Elastic Kubernetes Service (EKS) on AWS. There is a massive limitation with EKS that most people do not realize the consequences of.

I was recently working with a vendor that has a software my firm is thinking about purchasing to use. Part of the due diligence process is this celt doing a technical analysis on their architecture and security to ensure everything aligns with our requirements, goals, and aws environment. Immediately i saw this error, to which the vendor did not realize. Unfortunately they are going to have to make a key change to the SaaS product’s design if they want my firm to purchase it. So lets get into it so you dont end up being embarrassed by a cartoon celt in a call like this poor VP of Product did.