Naming convention for service groups

Question

What is the deciding feature that determines whether a service has the **Amazon** or **AWS** prefix? Looking at the answers online, there does not appear to be a consensus. From my exploration of the platform, it seems that **AWS** often refers to **IaaS** and **PaaS** services, while Amazon tends to be reserved for **SaaS**. Is this about right? Is there a better way to think about the naming convention? Thanks!

Accepted Answer

The answer is not very specific unfortunately, but for the majority of services:
- **AWS Prefix** - These are services that typically link or operate with other services. (AWS Cost Explorer, AWS IAM, AWS Budgets, AWS IAM, etc.)
- **Amazon Prefix** - These are services that function completely on their own. (Amazon RDS, Amazon SQS, Amazon EC2, etc.)

A single service on AWS may be defined as multiple (I/P/S/F)aaS interpretations, so most services are ambiguous to these terms.

Naming convention for service groups

Relevanter Inhalt