Creating Products - Service Catalog

Creating Products

You create products from the Products page in the Service Catalog administrator console.

To create a new Service Catalog product
  1. Navigate to the Products list page.

  2. Choose Create product, and the choose Create product.

  3. Product details contains the metadata that appears when you search for and view products in a list or detail page. Enter the following:

    • Product name – The name of the product.

    • Product description – The description shows in the product listing to help you choose the correct product.

    • Owner – The person or organization that publishes this product. The owner could be the name of your IT organization, or administrator.

    • Distributor (optional) – The name of the application's publisher. This field allows you to sort the products list to make it easier to find products.

  4. Version details enables you to add your template file and build your product. Enter the following:

    • Choose method – There are three ways to add a template file.

      • Use a template file - Upload an AWS CloudFormation template from a local drive.

      • Use a CloudFormation template - Specify a URL that points to a template stored in Amazon S3. If you specify an Amazon S3 URL, it must begin with https://.

      • Use an existing CloudFormation stack - Enter the ARN for an existing CloudFormation stack.

    • Version name (optional) – The name of the product version (e.g., "v1", "v2beta"). No spaces are allowed.

    • Description (optional) – A description of the product version, including how this version differs from the other versions.

    • Guidance – Managed in the versions tab on a Product details page. When a product version is created—during the create product workflow—guidance for that version is set to default. To learn more about guidance, see Managing Versions.

  5. Support details identifies the organization within your company, and provides a point of contact for support. Enter the following:

    • Email contact (optional) – The email address for reporting issues with the product.

    • Support link (optional) – An URL to a site where users can find support information or file tickets. The URL must begin with http:// or https://.

    • Support description (optional) – A description of how you should use the Email contact and Support link.

  6. Manage tags (optional) – In addition to using tags to categorize your resources, you can also use them to authenticate your permissions to create this resource.

  7. Create product – When you have completed the form, select Create product. After a few seconds, the product appears on the Products list page. You might need to refresh your browser to see the product.

You can also use CodePipeline to create and configure a pipeline to deploy your product template to Service Catalog and deliver changes you have made in your source repository. For more information, see Tutorial: Create a Pipeline That Deploys to Service Catalog.

You can define parameter properties in your AWS CloudFormation template and enforce those rules during provisioning. These properties can define the minimum and maximum length, minimum and maximum values, allowed values, and a regular expression for the value. Service Catalog issues a warning during provisioning if the value provided does not adhere to the parameter property. To learn more about parameter properties, see Parameters in the AWS CloudFormation User Guide.


You must have permission to retrieve objects from Amazon S3 buckets. Otherwise, you might encounter the following error when launching or updating a product.

Error: failed to process product version s3 access denied exception

If you encounter this message, make sure that you have permission to to retrieve objects from the following buckets:

  • The bucket where the provisioning artifact template is stored.

  • The bucket that begins with "cf-templates-*" and where Service Catalog stores the provisioning artifact template.

  • The internal bucket that begins with "sc-*" and where Service Catalog stores metadata. You won't be able to see this bucket from your account.

The following example policy shows the minimum permissions that are required to retrieve objects from the previously mentioned buckets.

{ "Sid": "VisualEditor1", "Effect": "Allow", "Action": "s3:GetObject*", "Resource": [ "arn:aws:s3:::YOUR_TEMPLATE_BUCKET", "arn:aws:s3:::YOUR_TEMPLATE_BUCKET/*", "arn:aws:s3:::cf-templates-*", "arn:aws:s3:::cf-templates-*/*", "arn:aws:s3:::sc-*", "arn:aws:s3:::sc-*/*" ] }