AWS Service Catalog and AWS Organizations
Service Catalog enables you to create and manage catalogs of IT services that are approved for use on AWS.
The integration of Service Catalog with AWS Organizations simplifies the sharing of portfolios and copying of products across an organization. Service Catalog administrators can reference an existing organization in AWS Organizations when sharing a portfolio, and they can share the portfolio with any trusted organizational unit (OU) in the organization's tree structure. This eliminates the need to share portfolio IDs, and for the receiving account to manually reference the portfolio ID when importing the portfolio. Portfolios shared via this mechanism are listed in the shared-to account in the administrator’s Imported Portfolio view in Service Catalog.
For more information about Service Catalog, see the Service Catalog Administrator Guide.
Use the following information to help you integrate AWS Service Catalog with AWS Organizations.
Service-linked roles created when you enable integration
AWS Service Catalog doesn't create any service-linked roles as part of enabling trusted access.
Service principals used to grant permissions
To enable trusted access, you must specify the following service principal:
-
servicecatalog.amazonaws.com
Enabling trusted access with Service Catalog
For information about the permissions needed to enable trusted access, see Permissions required to enable trusted access.
You can enable trusted access using either the AWS Service Catalog console or the AWS Organizations console.
Important
We strongly recommend that whenever possible, you use the AWS Service Catalog console or tools to enable integration with Organizations. This lets AWS Service Catalog perform any configuration that it requires, such as creating resources needed by the service. Proceed with these steps only if you can’t enable integration using the tools provided by AWS Service Catalog. For more information, see this note.
If you enable trusted access by using the AWS Service Catalog console or tools then you don’t need to complete these steps.
To enable trusted access using the Service Catalog CLI or AWS SDK
Call one of the following commands or operations:
You can enable trusted access by using either the AWS Organizations console, by running a AWS CLI command, or by calling an API operation in one of the AWS SDKs.
Disabling trusted access with Service Catalog
For information about the permissions needed to disable trusted access, see Permissions required to disable trusted access.
If you disable trusted access using AWS Organizations while you are using Service Catalog, it doesn't delete your current shares, but it prevents you from creating new shares throughout your organization. Current shares won't be in sync with your organization structure if it changes after you call this action.
You can disable trusted access using either the AWS Service Catalog or AWS Organizations tools.
Important
We strongly recommend that whenever possible, you use the AWS Service Catalog console or tools to disable integration with Organizations. This lets AWS Service Catalog perform any clean up that it requires, such as deleting resources or access roles that are no longer needed by the service. Proceed with these steps only if you can’t disable integration using the tools provided by AWS Service Catalog.
If you disable trusted access by using the AWS Service Catalog console or tools then you don’t need to complete these steps.
To disable trusted access using the Service Catalog CLI or AWS SDK
Call one of the following commands or operations:
-
AWS CLI: aws servicecatalog disable-aws-organizations-access
-
AWS SDKs: DisableAWSOrganizationsAccess
You can disable trusted access by using either the AWS Organizations console, by running an Organizations AWS CLI command, or by calling an Organizations API operation in one of the AWS SDKs.
