If they had chosen to use their own proprietary platform they risk Google and MSFT peeling customers away who want to work on a well designed open and portable orchestration platform. That might start slow but Amazon didn't get this big by allowing competition to take customers without throwing their own punches. They could have made their own _open source_ platform that would directly compete against k8s but by the time it was clear that demand was huge (I'm thinking early 2016) k8s already had to ton of momentum. Again they probably saw that and figured this was the best move with a high probability of success, even if it meant less lock-in.
They also have a whole slew of other products that serve almost exclusively as lock-in mechanisms. One truly portable product isn't going to be a huge deal.
EDIT: Distinguish proprietary and open source options in the second paragraph.
They have chosen that, but for rather than instead of k8s; they've announced that they are working on a fully managed system for k8s (Fargate for EKS, parallel to their existing ECS Fargate offering.)
I think it makes sense for AWS to jump on the bandwagon because they understand that Google is trying to commodify its complements [1]. The thing that AWS is betting on, I think, is not only surviving but thriving in a commodified environment [2]. The bet that AWS is making is that just like Amazon's retail business, commodification will hurt their competitors more than it hurts them, which will then allow them to make the most of the newly cleared competitive environment once the dust settles. Google's play, on the other hand, is to use the fact that Google is massively profitable elsewhere to allow Google cloud to run at negative profitability for a while in order to try to take a chunk out of AWS. The big loser I see from Kubernetes is Azure. Unlike Google, Microsoft does not have massive and growing profits from elsewhere. Enterprise and consumer Windows sales, while profitable, are on a declining profitability trajectory, according to Microsoft's own estimates. At the same time, Azure, in my estimation, doesn't have to survive extremely low margin environments in the same way that AWS can.
[1]: https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
AWS doesn't act like they can win without obvious lock-in, they act like they can win by extending open technologies with proprietary management layers that customers will depends on and be locked in by, which they do in pretty much every area.
It makes sense for Microsoft/IBM/Oracle to jump on the k8s bandwagon because they're basically doing the worst/newest entrants but why AWS? They already had CloudFormation, along with lots of energy already dumped into SDKs for various tools (ECS, beanstalk, etc).
There are a few other technologies that could have done this before k8s really took off, like pre-k8s openstack -- why didn't that get adopted?