
It always applies the most restrictive constraint among all constraints applied to the portfolio and the product. You use a simple editor to create template constraints, and you apply them to individual products.ĪWS Service Catalog applies constraints when provisioning a new product or updating a product that is already in use. These rules are called template constraints because they constrain how the AWS CloudFormation template for the product is deployed. You can define rules that limit the parameter values that a user enters when launching a product. Q: Can I restrict the AWS resources that users can provision? For information about creating a product, see “How do I create a product?” in the Administrator FAQ. These templates define the AWS resources that the product needs to work, the relationships between components, and the parameters that the end user chooses when launching the product to configure security groups, create key pairs, and perform other customizations.Īn end user with access to a portfolio can use the AWS Management Console to find a standard dev/test environment product, for example, in the form of an AWS CloudFormation template, then manage the resulting resources using the AWS CloudFormation console. Administrators create catalogs of products by importing AWS CloudFormation templates. It can be a single compute instance running AWS Linux, a fully configured multitier web application running in its own environment, or anything in between.Īdministrators distribute products to end users in portfolios.

A product can comprise one or more AWS resources, such as Amazon Elastic Compute Cloud (Amazon EC2) instances, storage volumes, databases, monitoring configurations, and networking components. A catalog is a collection of products that the administrator creates, adds to portfolios, and provides updates for using AWS Service Catalog. A product is a service or application for end users.
