> My gut is telling me ECS is the better choice for this team - simpler, no operational maintenance, almost no additional abstractions beyond the AWS primitives

> My gut is telling me ECS is the better choice for this team - simpler, no operational maintenance, almost no additional abstractions beyond the AWS primitives people will need to learn anyway. A consulting team hired before I was brought in are pushing EKS, but I’m not convinced that the improved devex is worth the increase in complexity and operational burden for our team. Yes, I'd say 100% ECS given what you've said here. Don't add complexity until you need it. When you have a larger and more mature devops team you can always reassess if it's time to consider EKS. Also, definitely have multiple AWS accounts either way. This is very standard and arguably best practice. AWS have management accounts specifically for this reason. Keep developers off prod and on a AWS separate account where you (and they) can be 100% certain they can't do any harm. But at the end of the day, neither are strictly wrong and what you're asking here is largely a question of corporate politics. If you don't feel you have a strong voice yet, then just try to have a good sense of the pros and cons of the different options you're considering and present a well reasoned opinion. If you're told you're wrong or you're overruled, then that's okay! Ultimately either will work, and right now it's probably better that you focus on building trust before being too opinionated.