AWS Service Catalog App Registry

Name: AWS Service Catalog App Registry API
Brand: AWS Service Catalog App Registry
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeapiKey24 EndpointsREST

For Agents

Catalogue applications, attach metadata attribute groups, and bind AWS resources to applications in App Registry. Agents can register applications and discover all resources tied to a given application.

Connect the AWS Service Catalog App Registry to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Service Catalog App Registry, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AWS Service Catalog App Registry API.

Attach reusable JSON metadata via attribute groups using CreateAttributeGroup and AssociateAttributeGroup

Bind AWS resources (CloudFormation stacks, resource groups) to an application with AssociateResource

Query an application's associated resources, attribute groups, and tags with ListAssociated* operations

GET STARTED

Start building with AWS Service Catalog App Registry API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AWS Service Catalog App Registry, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Service Catalog App Registry, keeping it validated and agent-ready. App Registry gives organisations a structured repository of their applications, the AWS resources that compose them, and the metadata needed to operate and govern them. Agents can create applications, attach attribute groups that carry custom JSON schemas, associate or disassociate AWS resources, and query the resulting application graph. The 24 operations cover applications, attribute groups, resource associations, sync, and tag management.

Use Cases

Patterns agents use AWS Service Catalog App Registry API for, with concrete tasks.

★ Application Inventory for a Multi-Service System

Platform teams use App Registry to declare each business application as a first-class entity, then attach the CloudFormation stacks, EC2 instances, and other resources that implement it. Once associated, ListAssociatedResources gives a complete view of which AWS resources belong to which application — useful for cost allocation, change management, and runbooks.

CreateApplication named 'checkout-service', then AssociateResource to bind two CloudFormation stack ARNs to it, and call ListAssociatedResources to verify.

Standardised Application Metadata via Attribute Groups

Governance teams define attribute groups that capture required metadata (tier, owner, data classification, compliance scope) and attach them to many applications. Because attribute groups carry a JSON schema, downstream automation can rely on the shape of the data without per-team variation.

CreateAttributeGroup with a JSON schema for {tier, owner, compliance}, then AssociateAttributeGroup to bind it to applications 'checkout-service' and 'orders-service'.

Resource Reconciliation Across CloudFormation Updates

When CloudFormation stacks change, App Registry can be kept in sync so that the application's resource list reflects reality. SyncResource refreshes the latest state for a specific associated resource, and ListAssociatedResources reveals drift between declared and actual membership.

Call SyncResource for resourceType=CFN_STACK and resource=<stack-arn> on application 'orders-service', then ListAssociatedResources to confirm the refreshed status.

AI Agent Application Discovery via Jentic

AI agents using Jentic can answer questions like 'which resources belong to the checkout application?' by calling App Registry through Jentic. The agent searches by intent, loads the operation schema, and executes List operations against the agent's AWS credentials in the vault.

Search Jentic for 'list resources associated with an appregistry application', execute GetApplication for 'checkout-service', then call the associated-resources listing to return the bound CloudFormation stacks.

Key Endpoints

24 endpoints — jentic publishes the only available openapi specification for aws service catalog app registry, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/applications

Create an App Registry application

GET

/applications

List all applications in the account

PATCH

/applications/{application}

Update an application's name or description

PUT

/applications/{application}/attribute-groups/{attributeGroup}

Attach an attribute group to an application

PUT

/applications/{application}/resources/{resourceType}/{resource}

Associate an AWS resource with an application

GET

/applications/{application}/resources/{resourceType}/{resource}

Get details for an associated resource

POST

/attribute-groups

Create a reusable attribute group

POST

/applications

Create an App Registry application

GET

/applications

List all applications in the account

PATCH

/applications/{application}

Update an application's name or description

PUT

/applications/{application}/attribute-groups/{attributeGroup}

Attach an attribute group to an application

PUT

/applications/{application}/resources/{resourceType}/{resource}

Associate an AWS resource with an application

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS IAM credentials are stored encrypted in the Jentic vault. Each App Registry call is signed by Jentic using SigV4 — the agent never handles the raw key or secret.

Intent-based discovery

Agents search by intent (for example, 'register an application' or 'list resources for an application') and Jentic returns the matching App Registry operations with input schemas, so the agent invokes CreateApplication or AssociateResource directly.

Time to first call

Direct App Registry integration: 1-2 days for IAM, SigV4 signing, and resource type wiring. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Resource Groups

Tag-based resource grouping that App Registry references for resource membership

Use Resource Groups to define a tag-based resource set, then associate that group with an App Registry application

Complementary

AWS Resource Groups Tagging API

Bulk tag management across AWS resources that App Registry references

Apply or audit tags through the Tagging API before associating resources to App Registry applications

Alternative

AWS Resource Access Manager

Cross-account resource sharing; targets sharing rather than per-application cataloguing

Use RAM when the goal is sharing resources across accounts; use App Registry when the goal is grouping resources by application

FAQs

Specific to using AWS Service Catalog App Registry API through Jentic.

Why is there no official OpenAPI spec for AWS Service Catalog App Registry?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Service Catalog App Registry via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AWS Service Catalog App Registry use?

App Registry uses AWS Signature Version 4 with IAM credentials and permissions on the servicecatalog:* and resource-groups:* actions. Through Jentic, the AWS access key and secret are stored encrypted in the vault and signed into each request — agents never see the raw credentials.

Can I associate any AWS resource with an App Registry application?

App Registry supports specific resource types — CloudFormation stacks (CFN_STACK) and AWS Resource Groups (RESOURCE_TAG_VALUE) — bound via AssociateResource at /applications/{application}/resources/{resourceType}/{resource}. Other AWS services are tracked indirectly through the CloudFormation stacks that create them.

What are the rate limits for the AWS Service Catalog App Registry?

App Registry uses standard AWS API throttling — most operations are limited to roughly 5-10 requests per second per account per region with brief burst capacity. Throttled requests return a ThrottlingException; clients should retry with exponential backoff.

How do I list every resource bound to an application through Jentic?

Through Jentic, search for 'list associated resources appregistry', load the operation schema, and execute against /applications/{application} with the application name. Jentic returns the resource list along with each association's lastSyncTime.

Is AWS Service Catalog App Registry free?

App Registry itself is offered at no additional charge — you pay only for the underlying resources you catalogue. Standard AWS Service Catalog product pricing applies if you also use Service Catalog provisioned products.