Skip to main content
In this lesson we’ll cover AWS Service Catalog: what it is, why it matters, and how teams use it to deliver consistent, governed, self‑service cloud resources. At a high level, AWS Service Catalog acts like a library catalog for IT resources. Instead of books, administrators curate approved IT services — from single EC2 instances to databases, software packages, and full multi‑tier application stacks. The cloud administrator (the “librarian”) decides which offerings are available and which users or teams can provision them. This approach reduces inconsistencies, enforces governance, controls spend, and speeds up provisioning. Problems without a Service Catalog:
  • Inconsistent deployments and drift
  • Difficulty enforcing governance and compliance
  • Untracked or uncontrolled cloud spending
  • Complexity managing resources across multiple AWS accounts
  • Slow, manual provisioning that impacts developer velocity
A slide titled "Without Service Catalog" showing AWS Service Catalog icons on the left and a dotted panel on the right with orange icons listing problems: inconsistent deployments, lack of governance and compliance, uncontrolled spending, multi-account complexity, and slow resource deployment.
Service Catalog provides a curated catalog of approved IT services. Users see only the subset they’re allowed to access, ensuring that only compliant, preapproved resources are provisioned.

​
Core concepts

  • Product
    A product is an IT service you publish for deployment. In AWS Service Catalog a product is typically defined by a CloudFormation template that declares all resources and relationships (EC2 instances, RDS databases, networking, S3 buckets, monitoring, IAM roles, etc.). Administrators can expose configuration parameters (key pairs, instance sizes, subnets, tags, and more) while keeping other settings fixed to guarantee consistency and compliance. Products can range from a single resource to a full multi‑tier application.
  • Portfolio
    A portfolio groups related products and contains configuration and access control information. Portfolios let administrators manage which users, roles, or accounts can view, launch, or modify the included products. Portfolios can be shared across AWS accounts to provide consistent, organization‑wide offerings.
You create a product by importing a CloudFormation template that defines resources, dependencies, and launch parameters. Publishing a new product version makes that version available to users who have access to the portfolio.
A schematic "Service Catalog" diagram showing Product X, Y, and Z, with Product X containing AWS icons for VPC, EC2, RDS, and S3. On the right are Portfolios A and B that list Product X and Product Y.

​
Roles and workflow

Two primary user roles:
  • Catalog administrator
    Creates and manages products and portfolios, prepares CloudFormation templates, configures launch constraints and IAM roles, and grants access to users or roles.
  • End user
    Searches the catalog, selects an approved product, launches it, and manages the lifecycle of the provisioned product within their allowed permissions.
Typical workflow:
  1. Catalog administrator creates a product (CloudFormation template).
  2. Administrator organizes products into a portfolio and configures access.
  3. Administrator distributes the portfolio, optionally sharing it with other AWS accounts.
  4. End user discovers and selects a product from the catalog.
  5. End user launches the product; Service Catalog creates a CloudFormation stack for that product.
  6. End user manages the lifecycle of the provisioned product according to permissions.
A two-row workflow diagram showing "Catalog Administrators" and "End User" roles. It maps admin steps (Create Product → Organize Portfolio → Manage Portfolio → Distribute Portfolio) and user steps (Discover Product → Select Product → Launch Product → Manage Product Lifecycle).

​
How Service Catalog maps to AWS services

Service Catalog integrates closely with several core AWS services to provide governance, provisioning, and automation. Service Catalog centralizes approved templates and enforces governance while offering a self‑service experience for provisioning consistent environments.
A diagram titled "Service Catalog" showing AWS Service Catalog icons connected by arrows to AWS CloudFormation, IAM, and AWS service icons. It illustrates provisioning of portfolios and products (e.g., Product X/Y) into AWS resources like compute, database, and S3.

​
Features and components (summary)

  • Products — Collections of AWS resources defined and deployed together via CloudFormation.
  • Stack / Resource Group — Product deployments result in CloudFormation stacks representing provisioned resources.
  • Portfolios — Group products and manage access for users, groups, or accounts.
  • Granular access control — Use IAM policies and launch constraints to control permitted operations on products and portfolios.
  • Service Actions — Allow end users to run approved operational workflows (runbooks or Lambda functions) against provisioned products without granting direct access to underlying resources.
A "Features" slide with five numbered cards showing Products, Stack or Resource Group, Portfolios, Granular Access Control, and Service Actions, each paired with a colorful circular icon. The layout uses rounded pale rectangles and gradient icon circles.
Products in Service Catalog are expressed as CloudFormation templates. Make sure templates are validated, parameterized appropriately, and include required tagging and IAM controls for governance and cost allocation.
Service Actions can be configured to run centralized automation (for example, Systems Manager Automation runbooks or Lambda‑backed operations). This enables end users to perform routine tasks—troubleshooting, applying approved updates, or requesting escalations—without direct access to the underlying AWS resources. Use this guide to design Service Catalog products with consistent templates, enforce governance via portfolios and IAM, and enable self‑service provisioning that scales across your organization.

Watch Video