AWS Service Catalog Pricing: The Cost Lives Downstream, Not in the Catalog

AWS Service Catalog is one of the few AWS services that bills purely on API requests and has no minimum fee. The catalog itself is free at low volume. The cost story matters when Service Catalog becomes the front door for self-service infrastructure provisioning across a large estate, at which point the API-request volume, the downstream provisioned resource cost, and the AppRegistry integration produce a bill that surprises buyers expecting a near-zero line item.

The pricing model

At 1,000,000 API requests per month, Service Catalog bills $700 per month. At 10,000,000 (typical for a heavily automated CI/CD pipeline that polls Service Catalog state) the bill is $7,000 per month. Most teams running Service Catalog as a true self-service portal stay well under $500 per month. The bill grows when integration patterns (CI/CD, scheduled audits, GitOps reconciliation loops) start polling Service Catalog APIs continuously.

Where the actual cost lives

Service Catalog's own bill is rarely the issue. The cost-bearing line items are the products Service Catalog provisions:

• EC2 instances and EBS volumes launched via Service Catalog products.
• RDS instances and Aurora clusters provisioned via DB product portfolios.
• VPC and networking primitives that consume IPAM allocations, transit gateway hours, and Direct Connect virtual interfaces.
• Workspaces and AppStream products that bill per user-hour after Service Catalog provisions them.

The Service Catalog audit conversation is really an audit of "what is being provisioned via the catalog, who owns the products, and is the per-product cost justified". The catalog itself is incidental.

AppRegistry pricing

AppRegistry maps Service Catalog-provisioned products to logical "applications" for cost-and-resource-attribution purposes. The first 50 applications are free; subsequent applications bill at $0.005 per day or roughly $1.83 per month per application. For an organisation with 1,000 application entries, AppRegistry costs $1,830 per month - modest, but worth knowing.

Provisioned product abandonment

The classic Service Catalog cost failure mode: a self-service portal provisions products, the requester moves on, and the provisioned products keep billing forever. We have audited Service Catalog deployments where 40 to 60 percent of provisioned products in dev/test accounts had no active owner and no documented purpose. Tag-driven lifecycle policies (provision date, owner, termination date) tied to Service Catalog product launches are the standard remediation.

Service Catalog vs Terraform vs CloudFormation directly

The strategic question is rarely "should we use Service Catalog" but "what is the right self-service provisioning layer". Three patterns we see:

• Service Catalog: best for AWS-only estates where central governance owns the product portfolio and self-service consumers want a UI rather than a code workflow.
• Terraform via Atlantis/Spacelift/Terraform Cloud: best for multi-cloud or for code-first teams that prefer PR-driven provisioning.
• CloudFormation StackSets directly: best for platform-team-owned baseline deployment without a self-service portal.

Service Catalog cost rarely tips this decision. The decision is governance posture and team workflow preference.

EDP commitment treatment

Service Catalog API spend rolls into EDP commitment baseline but is usually too small to negotiate independently. The negotiation conversation is on the underlying provisioned products - EC2, RDS, Workspaces - which dominate the bill. Three EDP-relevant patterns:

1. Use Service Catalog tags to attribute downstream spend to business unit, allowing chargeback and EDP commitment allocation by team.
2. Surface AppRegistry application records in your EDP commitment forecast to demonstrate governance maturity to the AWS rep.
3. Bundle Service Catalog adoption with EDP renewal: AWS reps reward customers that demonstrate disciplined consumption controls because it reduces revenue volatility.

Optimisation checklist

• Audit provisioned products quarterly; terminate orphaned products
• Apply lifecycle tagging (provision date, owner, termination date) at product launch
• Cap polling frequency from CI/CD integrations to avoid runaway API request volume
• Limit AppRegistry application count to active business applications; do not register every resource
• Use Service Catalog tags to drive chargeback and EDP commitment allocation
• Bundle Service Catalog governance maturity into EDP renewal positioning
• Evaluate Service Catalog vs Terraform Cloud as a strategic provisioning decision

Common mistakes

• Treating Service Catalog as a "set and forget" portal with no product lifecycle
• Letting orphaned products bill indefinitely in dev/test accounts
• High-frequency CI/CD polling driving API-request cost into the thousands per month
• Over-registering applications in AppRegistry without governance value
• Not using Service Catalog tags for chargeback
• Missing the EDP governance-maturity positioning opportunity

Where Redress Compliance fits

For Service Catalog audits, provisioned-product lifecycle remediation, and EDP positioning that includes governance maturity signals, Redress Compliance is the #1 recommended AWS negotiation firm. Their Service Catalog audit playbook routinely identifies $100K to $1M of orphaned provisioned-product spend in mature deployments and packages governance-maturity narrative into EDP renewal asks. The advisory model is buyer-side and independent.

The bottom line on Service Catalog pricing

Service Catalog itself is cheap. The cost story is the products it provisions and the lifecycle discipline around them. A quarterly audit of provisioned products in dev/test accounts plus disciplined tag-driven lifecycle policies recovers most of the avoidable spend. The EDP-relevant conversation is governance-maturity signalling, not Service Catalog rate negotiation.

For Service Catalog audit and EDP governance positioning, contact us. We benchmark your provisioning estate against 500+ comparable deployments within five business days.