Naming convention for service groups

1

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!

질문됨 2년 전600회 조회
1개 답변
1
수락된 답변

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.

profile pictureAWS
전문가
Chris_G
답변함 2년 전
  • Great, thank you very much for the clarifications.

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠