Not a bad stab at it, but SNS is not just for mobile notifications (and I hate that they always put it under "mobile"), and SQS is not "like" RabbitMQ. You need SNS -> SQS to get that analogy right. We have dozens of SNS topics and 3-4x that number of SQS queues subbed to them in order to replicate our old flaky RabbitMQ stack. We have never used them for "push notifications", and in fact when I've tried using SNS for that in the past, it did not scale very elegantly at all.
ElastiCache is not "AWS Memcache" (it supports other caching services), and S3 is not "unlimited FTP" (it does not support FTP protocols).
Amazon RDS is not Amazon SQL (that's what they should have called Aurora), but Amazon Hosted RDBMS.
I'd also argue that EC2 isn't always a virtual server (once you get to a certain size, you're on your own iron), and that SES can be used for more than transactional emails.
I do think this is mainly aimed at developers used to more basic SaaS/PaaS services (like Heroku, which was mentioned a few times). Coming from that angle it really doesn't matter that S3 is not technically FTP, since it's more about "What do I use this for?". Using this list these users can quickly see that if they want to host files they should use S3 and not EC2.
You are right that this simplification is not technically correct anymore.
ElastiCache is not "AWS Memcache" (it supports other caching services), and S3 is not "unlimited FTP" (it does not support FTP protocols).
Amazon RDS is not Amazon SQL (that's what they should have called Aurora), but Amazon Hosted RDBMS.
I'd also argue that EC2 isn't always a virtual server (once you get to a certain size, you're on your own iron), and that SES can be used for more than transactional emails.
But, that aside, not a bad job.