AWS Service Catalog

Name: AWS Service Catalog
Brand: Amazon Web Services (AWS)
Rating: 4.1 (31 reviews)

Leader

Official Global LinkedIn page for Amazon Web Services (AWS).

Est 2006|Valuation $2560B|1 Ref Customers

LinkedIn 10.9M|Website|Web traffic 1.1M|FTEs 148,001|HQ Seattle, Washington, US

01Competitive Landscape

Narrative analysis

Where AWS Service Catalog is most suitable - When the organization is primarily operating on AWS and requires a native, permissions-driven mechanism to publish standardized products. - When integration with AWS accounts, IAM policies, tagging strategies, and Control Tower/Organizations patterns is important. Where alternatives may be preferred - **Terraform ecosystem**: Often selected for multi-cloud environments, a larger module ecosystem, and unified workflows across clouds. - **ServiceNow/JSM**: Frequently used as a front-end service request experience for approvals, request management, and enterprise workflows; Service Catalog can provide the provisioning backend. - **Multi-cloud CMPs** (e.g., Morpheus/BMC): Chosen when governance and catalog coverage must include AWS, Azure, and on-premises infrastructure. Competitor perspectives - ServiceNow markets its catalog and workflow capabilities as a storefront and emphasizes operational outcomes, while Terraform emphasizes a multi-cloud IaC ecosystem. Pricing and implementation effort vary significantly across these options. Adoption trends (directional) - Growth in platform engineering and internal developer platform initiatives has increased interest in catalogs. Many teams combine developer portals (e.g., Backstage) with Terraform/GitOps rather than relying solely on Service Catalog.

	AWS Service Catalog	HashiCorp Terraform (incl. Terraform Cloud)	ServiceNow Service Catalog (ITSM)
Starting Price	API-call based; vendor provides a limited free-tier API quota	Varies by edition; open-source edition available; commercial cloud offering is subscription-based	Pricing typically quote-based; public estimates vary widely and depend on selected modules/users
Primary Use Case	AWS-scoped governed self-service provisioning for multi-account AWS environments	IaC standardization across teams; broad ecosystem and multi-cloud capability	Enterprise request/approval workflows, service fulfillment, ITIL/ITSM catalog front-end
Key Strength	Native AWS guardrails (IAM/constraints/tagging), portfolio sharing, AWS integrations	Strong IaC workflow tooling, broad ecosystem, multi-cloud support	Mature enterprise workflow and approval UX; extensive IT process integration
Key Weakness	Steep learning curve; CloudFormation-centric patterns; AWS-only scope	Requires governance discipline; drift and lifecycle management depend on implementation	Potentially high implementation and licensing cost; not a native AWS provisioning backend by itself

01Competitive Landscape

Narrative analysis

Where AWS Service Catalog is most suitable

When the organization is primarily operating on AWS and requires a native, permissions-driven mechanism to publish standardized products.
When integration with AWS accounts, IAM policies, tagging strategies, and Control Tower/Organizations patterns is important.

Where alternatives may be preferred

Terraform ecosystem: Often selected for multi-cloud environments, a larger module ecosystem, and unified workflows across clouds.
ServiceNow/JSM: Frequently used as a front-end service request experience for approvals, request management, and enterprise workflows; Service Catalog can provide the provisioning backend.
Multi-cloud CMPs (e.g., Morpheus/BMC): Chosen when governance and catalog coverage must include AWS, Azure, and on-premises infrastructure.

Competitor perspectives

ServiceNow markets its catalog and workflow capabilities as a storefront and emphasizes operational outcomes, while Terraform emphasizes a multi-cloud IaC ecosystem. Pricing and implementation effort vary significantly across these options.

Adoption trends (directional)

Growth in platform engineering and internal developer platform initiatives has increased interest in catalogs. Many teams combine developer portals (e.g., Backstage) with Terraform/GitOps rather than relying solely on Service Catalog.

	AWS Service Catalog	HashiCorp Terraform (incl. Terraform Cloud)	ServiceNow Service Catalog (ITSM)
Starting Price	API-call based; vendor provides a limited free-tier API quota	Varies by edition; open-source edition available; commercial cloud offering is subscription-based	Pricing typically quote-based; public estimates vary widely and depend on selected modules/users
Primary Use Case	AWS-scoped governed self-service provisioning for multi-account AWS environments	IaC standardization across teams; broad ecosystem and multi-cloud capability	Enterprise request/approval workflows, service fulfillment, ITIL/ITSM catalog front-end
Key Strength	Native AWS guardrails (IAM/constraints/tagging), portfolio sharing, AWS integrations	Strong IaC workflow tooling, broad ecosystem, multi-cloud support	Mature enterprise workflow and approval UX; extensive IT process integration
Key Weakness	Steep learning curve; CloudFormation-centric patterns; AWS-only scope	Requires governance discipline; drift and lifecycle management depend on implementation	Potentially high implementation and licensing cost; not a native AWS provisioning backend by itself

AWS Service Catalog

01Competitive Landscape

Narrative analysis

02Market Map

01Competitive Landscape

Narrative analysis

02Market Map