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

Question

Just curious to understand if there are any logical reasoning behind in naming AWS products and services. For example, it has been named as AWS Lambda and not Amazo

Answer 1

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.