> For the complete documentation index, see [llms.txt](https://ysfang82.gitbook.io/development-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ysfang82.gitbook.io/development-notes/aws-notes/service/management-tools/catalog.md).

# Catalog

**Introduction**

* Centrally manage catalogs of approved IT services on AWS for governance. Ex:
  * VM images
  * Servers
  * Software
  * DB
  * Regions
  * IP address ranges
  * **Not for: AMI id**
* Helps users to quickly deploy only the approved IT services
* For two parts:
  * Admin
    * Define compliant prodcut portfolio / IAM with CloudFormation templates to define who can use a certain kind of services.
    * Use [TagOptions ](https://docs.aws.amazon.com/servicecatalog/latest/adminguide/tagoptions-launching.html)to provide the users a list from which they can select their cost center.
    * Activate the cost center tag in the Billing Console.
  * Users
    * Are going to see the product list they are authorized to use, then **provision services which are properly tagged / configured**.

**Feature**

* Can integrate with AWS ServiceNow (enterprise service management platform, "self-service portal")
* [License management](https://aws.amazon.com/blogs/mt/tracking-software-licenses-with-aws-service-catalog-and-aws-step-functions/) for applications deployed on AWS
  * **A Lambda trigger is not currently available for Service Catalog product deployments.**
    * Have Amazon CloudWatch detect when a user deploys a Service Catalog product. 
    * Launch an **AWS Step Functions** process to increment license counts in the DB table
    * Send notifications when overage thresholds are met
* For Service Catalog products to be successfully launched
  * A launch constraint must be assigned and have sufficient permission to deploy the product
  * the user must have the same required permissions