All Services

Mgmt & Governance

AWS Service Catalog

AWS Service Catalog lets platform teams create portfolios of approved products and versions, share them across accounts and Regions, apply launch, notification, template and tag-update constraints, and let authorized users provision governed CloudFormation-backed resources.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with AWS Service Catalog.

AWS Service Catalog pricing and cost programs

Pricing model: Portfolio and provisioned-product usage

On-Demand
Service-specific
Reserved Instances or reserved capacity
Not applicable
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: Portfolio management · Provisioned resources · AppRegistry and related features

Programs and modes: Service Catalog portfolios · Provisioned products · AppRegistry

Service Catalog feature charges and the resources it provisions are separate.

Free Tier: Service-specific — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement AWS Service Catalog?

  • Provides self-service infrastructure from approved templates without granting consumers broad provisioning permissions.
  • Organizes products and versions into portfolios with identity access, cross-account sharing, launch roles, tag options, budgets and constraints.
  • Tracks provisioned-product lifecycle and integrates with CloudFormation, Organizations, Control Tower Account Factory, AppRegistry and notifications.

How to implement AWS Service Catalog

  1. Define product users, service owner, support contract, parameters, outputs, upgrade and deprecation policy, allowed accounts and Regions, data classification, cost, quotas and rollback behavior.
  2. Create a versioned CloudFormation product and portfolio, assign least-privilege launch roles, grant portfolio access, add constraints and tag options, share to governed accounts, and publish support information.
  3. Test launch, update, terminate, role and policy behavior as an end user, monitor CloudFormation and provisioned-product failures, patch active versions, notify consumers and retire obsolete versions only after migration.

AWS Service Catalog best practices

  • Use launch constraints so consumers provision through a controlled service role rather than receiving the permissions required by every product resource.
  • Keep products small, documented, parameter-constrained and versioned; test upgrades and deletion, protect stateful data, publish ownership and support contacts, and avoid mutable artifacts behind an existing version.
  • Control portfolio sharing and principal access, use tag and template constraints where supported, monitor stale provisioned products, and plan deprecation because removing a version does not automatically migrate existing deployments.

AWS Service Catalog use cases and server impact

  • Approved self-service application environments
  • Standard databases, networks, and security products
  • Control Tower account and landing-zone extensions

Replaces custom request portals and privileged provisioning scripts for standardized products, while template quality, product support, upgrades, data protection, permissions, quotas, costs, and consumer lifecycle remain yours.

Official implementation resources

Commonly paired AWS services