AWS Config adds support for AWS Service Catalog
You can now use AWS Config to record configuration changes to AWS Service Catalog, a service that allows customers to organize, govern, and provision cloud resources on AWS. With AWS Config, you can track changes to the configuration of an AWS Service Catalog portfolio, such as addition or removal of launch constraints, tags and accounts with which the portfolio has been shared.
You can now use AWS Config to record configuration changes to AWS Service Catalog, a service that allows customers to organize, govern, and provision cloud resources on AWS. With AWS Config, you can track changes to the configuration of an AWS Service Catalog portfolio, such as addition or removal of launch constraints, tags and accounts with which the portfolio has been shared.
You can also view the AWS Service Catalog products associated with a portfolio as well as the products provisioned from the portfolio. AWS Config maintains the configuration change history for these AWS Service Catalog resource types, which you can access through the AWS Config console or APIs. This data can be used for audit purposes as well as for operational troubleshooting. For example, you can use this data to understand how a certain AWS Service Catalog user changed a portfolio constraint and when that change occurred.
Support for AWS Service Catalog in AWS Config is available in all AWS public Regions where AWS Service Catalog is offered. For the full list of supported Regions, see AWS Regions and Endpoints in the AWS General Reference.
For more information about AWS Config, see the following:
For more information about AWS Service Catalog, see the following: