I can't find even a single example of AWS shutting down a service. In fact, one example, showing a potentially different philosophy across companies is AWS Sim

I can't find even a single example of AWS shutting down a service. In fact, one example, showing a potentially different philosophy across companies is AWS SimpleDB. SimpleDB is no longer on the AWS console - DynamoDB has replaced it, as AWS believes DynamoDB is a superior service. That said, SimpleDB still functions perfectly fine. In fact, I recently spoke to an AWS manager who stated that they will leave SimpleDB out there as long as people keep using it. Just one metric: How many services has Google Cloud shut down and how many has AWS shut down? Off the top of my head, I know of two Google Cloud services, and after Googling (Thanks!) I can't find a single AWS example. The fact remains: If Google knows that this reputation is in the populace but still doesn't believe it's worth it to fight that with more than 12 months notice with (what appears) a small investment - is the reputation undeserved? If larger Google Cloud services start losing money, why should customers count on Google to keep those services up? AWS comes out with new services all the time, and even if they are smaller / niche, I feel comfortable recommending them to my clients. For example Data Pipeline never really seemed that popular, and AWS has recently come out with a better product, AWS Glue, which the former Data Pipeline team has transitioned to. Will AWS force customers to switch to the new, better AWS Glue? No, they will leave Data Pipeline, and their customers' investments alone.