Amazon Web Services in Plain English
Sure, a lot of AWS services could have been named better. But a lot of these are terrible, downright misleading names.<p>Some examples:<p>S3 as "Amazon Unlimited FTP Server": S3 has nothing to do with the FTP protocol.<p>VPC as "Amazon Virtual Collocated Rack": VPCs don't have anything to do with either collocation (they can span AZs), much less physical racks.<p>Lambda as "AWS App Scripts": <i>really</i> disagree with this one. Their intent is to be microservices or event handling functions, not scripts. "Scripts" isn't really descriptive but usually implies a manually invoked automation that modifies some kind of stateful resource (such as files). Lambda is basically the exact opposite.<p>There are lots more that are problematic or overly simplified as well.<p>I don't say this to crap on the effort, just... be careful if you're relying on this for your understanding of what AWS does.