AWS products and services naming nomenclature starting with 'Amazon' vs 'AWS'

As far as I understand, the prefix AWS is used for PaaS ( Platform as a Service) and prefix Amazon is used for IaaS (Infrastructure as a Service). The term AWS(Amazon Web Service) is used whenever it is offered in terms of service/platform, where as Amazon is used whenever a hardware resource/infrastructure is provided.

For example: In the product page of AWS site, in compute category the Amazon EC2 is IaaS providing compute capacity where as AWS Elastic BeanStalk is PaaS which is a platform for deploying web services and web-apps/wesites, likewise AWS Lambda is PaaS for server-less computing which lets us run code without provisioning or managing servers. Similarly in Storage category Amazon S3 is an IaaS which provides storage capabilities where as AWS Snownball is a petabyte-scale data transport solution that uses secure appliances to transfer large amounts of data into and out of the AWS cloud,which is kind of PaaS.

Although this is just a logical assumption, as we never really know about how Amazon has named it's products and services. So please forgive if there are difference of opinions regarding this.

Managed to find an answer on naming analogy for AWS products and services from another similar question posted here. Response provided by a Senior Technical Trainer working at Amazon Web Services.

The pattern is that utility services are prefixed with AWS, while standalone services are prefixed by "Amazon".

Services prefixed with AWS typically use other services, for example:

• AWS Elastic Beanstalk, AWS OpsWorks and AWS CloudFormation launch other services

• AWS Lambda is triggered by other services

• AWS Data Pipeline moves data between other services

• AWS CloudFormation launches other services

The AWS documentation page is a great reference for determining the official name of a service.