This article will help you understand AWS Service Catalog portfolios, what they are, how they are used by the service and how you can best make use of them whilst using the Service Catalog Tools.
Within AWS Service Catalog a portfolio is a logical grouping of products.
It makes sense to group products that provision similar or complimentary resources together, but this may not give you the flexibility you need:
When using the Service Catalog Tools we recommend you think about how your products will be consumed. If you are going to offer a ‘service catalog’ or build a vending machine we recommend grouping those products together into a portfolio.
When using the Service Catalog Tools to provision resources into an account we recommend grouping those products into a portfolio.
When you have multiple teams building products we recommend each team having their own portfolios.
This normally results in at least two portfolios per team:
The teams we have worked with normally group the products into mandatory products and self service products. For example, if the team using Service Catalog Tools is a cloud engineering / CCOE team they would provision products like AWS Security Hub Enabler into an account - this would be mandatory. If the same team had some optional products like Encrypted S3 Bucket then this would go into an optional portfolio. This results in the following structure:
The names of the portfolios are for you to chose as you know your audience better than we do but we have found the following names work well:
If you would like to share your portfolio names raise a github issue to share