I'm convinced Amazon has many teams crapping out new features but they don't have the political clout (or manpower) to create a comprehensive product. They are mandated by management to use existing services, and thus we the users suffer because we have to manage all this extra crap and noise just to enable basic functionality.
It's maddening. And then also it's maddening to see another service from a different team that was able to throw off these shackles and actually make a product that is self contained. You get a taste of how good things could be, and then you're thrown right back into the IAM/SQS/Cloudwatch/Cloudformation/Policy/everything else under the sun soup.
So you get a lot of disconnected services that work fairly well on their own and provide you GREAT building blocks if you're a developer. For example, 10 years ago, I wrote a task orchestration service that used CloudWatch Logs for task log storage. The viewer simply used the CW APIs to tail the logs from tasks, not having to worry about storage, updates, etc.
But the reverse side is that cross-team projects often languish. Especially in the UI section. Obvious things like showing logs in the reverse order (newest entries first) get overlooked and ignored.
Build the rest yourself. In many cases their higher level service is just the same open source package you would run, just managed worse.