Service Catalog
Definition
Managed service for publishing pre-approved cloud resource portfolios that users deploy via self-service while enforcing governance and compliance.
Use Cases
- Capital One: Standardizing how internal teams provision secure cloud infrastructure — Capital One has publicly described building strong cloud governance and self-service patterns on AWS. A service catalog approach fits this model by letting platform teams publish approved infrastructure templates and application stacks for developers to deploy without manual ticketing. (Faster provisioning, more consistent security controls, and reduced operational friction for development teams.)
- Siemens: Providing governed self-service cloud environments for multiple engineering and business teams — Large enterprises such as Siemens commonly use centralized cloud platform teams to define approved deployment patterns. In practice, a service catalog model allows reusable application environments, network baselines, and compliant infrastructure stacks to be offered through self-service. (Improved compliance, reduced configuration drift, and quicker onboarding for new projects.)
- Accenture: Delivering repeatable cloud environments across many client engagements — Global consulting firms often create internal catalogs of approved landing zones, development environments, and application blueprints so teams can launch standardized infrastructure repeatedly across accounts and regions. (Greater deployment consistency, lower setup time, and easier cost and policy enforcement.)
Provider Equivalents
- AWS: AWS Service Catalog
- Azure: Azure Managed Applications
- GCP: Google Cloud Service Catalog
- OCI: Oracle Cloud Infrastructure Marketplace
Frequently Asked Questions
- What's the difference between Service Catalog and Infrastructure as Code?
- Infrastructure as Code is the method of defining infrastructure in files or templates, such as CloudFormation, Terraform, or ARM/Bicep. A Service Catalog sits on top of that idea and provides a governed self-service experience. In simple terms, Infrastructure as Code is how the resource is defined, while Service Catalog is how approved versions of those definitions are packaged, shared, and deployed by end users.
- When should I use Service Catalog?
- Use Service Catalog when many teams need to deploy cloud resources quickly but your organization also needs standardization, security guardrails, and cost control. It is especially useful in enterprises, regulated environments, platform engineering teams, and any organization that wants self-service without allowing every user to build infrastructure from scratch.
- How much does Service Catalog cost?
- Cost depends on the cloud provider and the resources being deployed. In AWS, AWS Service Catalog itself does not typically add major standalone infrastructure cost compared with the products it provisions, but you still pay for the underlying AWS resources such as EC2, RDS, and networking. In Azure, GCP, and OCI, the main cost is also usually the deployed resources, plus any related management or marketplace charges. Always check current provider pricing pages because pricing models and service availability can change.
Category: cloud
Difficulty: intermediate
Related Terms
See Also