Unless you're Werner Vogels, in which case you mandate whatever the implementation team feels like using, as long as it scales and adheres to the service interface specifications.
I've heard Werner Vogels talk about this subject before. He chose Ruby for one of their projects specifically because they wanted very fast iterations, even though they new it wouldn't scale and they would have technical debt down the line. I don't think you are accurately describing how Amazon does things.
