Amazon Service Catalog and Amazon Organizations - Amazon Organizations
Service-linked rolesService principalsEnable trusted accessDisable trusted access
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon Service Catalog and Amazon Organizations

Service Catalog enables you to create and manage catalogs of IT services that are approved for use on Amazon.

The integration of Service Catalog with Amazon Organizations simplifies the sharing of portfolios and copying of products across an organization. Service Catalog administrators can reference an existing organization in Amazon 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 Amazon Service Catalog with Amazon Organizations.

Service-linked roles created when you enable integration

Amazon 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 Amazon Service Catalog console or the Amazon Organizations console.

Important

We strongly recommend that whenever possible, you use the Amazon Service Catalog console or tools to enable integration with Organizations. This lets Amazon 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 Amazon Service Catalog. For more information, see this note.

If you enable trusted access by using the Amazon Service Catalog console or tools then you don’t need to complete these steps.

To enable trusted access using the Service Catalog CLI or Amazon SDK

Call one of the following commands or operations:

You can enable trusted access by using either the Amazon Organizations console, by running a Amazon CLI command, or by calling an API operation in one of the Amazon SDKs.

Amazon Web Services Management Console
To enable trusted service access using the Organizations console

  1. Sign in to the Amazon Organizations console. You must sign in as an IAM user, assume an IAM role, or sign in as the root user (not recommended) in the organization’s management account.

  2. In the navigation pane, choose Services.

  3. Choose Amazon Service Catalog in the list of services.

  4. Choose Enable trusted access.

  5. In the Enable trusted access for Amazon Service Catalog dialog box, type enable to confirm it, and then choose Enable trusted access.

  6. If you are the administrator of only Amazon Organizations, tell the administrator of Amazon Service Catalog that they can now enable that service using its console to work with Amazon Organizations.

Amazon CLI, Amazon API
To enable trusted service access using the OrganizationsCLI/SDK

You can use the following Amazon CLI commands or API operations to enable trusted service access:

  • Amazon CLI: enable-aws-service-access

    You can run the following command to enable Amazon Service Catalog as a trusted service with Organizations.

    $ aws organizations enable-aws-service-access \ 
    --service-principal servicecatalog.amazonaws.com

    This command produces no output when successful.

  • Amazon API: EnableAWSServiceAccess

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 Amazon 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 Amazon Service Catalog or Amazon Organizations tools.

Important

We strongly recommend that whenever possible, you use the Amazon Service Catalog console or tools to disable integration with Organizations. This lets Amazon 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 Amazon Service Catalog.

If you disable trusted access by using the Amazon Service Catalog console or tools then you don’t need to complete these steps.

To disable trusted access using the Service Catalog CLI or Amazon SDK

Call one of the following commands or operations:

You can disable trusted access by using either the Amazon Organizations console, by running an Organizations Amazon CLI command, or by calling an Organizations API operation in one of the Amazon SDKs.

Amazon Web Services Management Console
To disable trusted service access using the Organizations console

  1. Sign in to the Amazon Organizations console. You must sign in as an IAM user, assume an IAM role, or sign in as the root user (not recommended) in the organization’s management account.

  2. In the navigation pane, choose Services.

  3. Choose Amazon Service Catalog in the list of services.

  4. Choose Disable trusted access.

  5. In the Disable trusted access for Amazon Service Catalog dialog box, type disable to confirm it, and then choose Disable trusted access.

  6. If you are the administrator of only Amazon Organizations, tell the administrator of Amazon Service Catalog that they can now disable that service using its console or tools from working with Amazon Organizations.

Amazon CLI, Amazon API
To disable trusted service access using the Organizations CLI/SDK

You can use the following Amazon CLI commands or API operations to disable trusted service access:

  • Amazon CLI: disable-aws-service-access

    You can run the following command to disable Amazon Service Catalog as a trusted service with Organizations.

    $ aws organizations disable-aws-service-access \
    --service-principal servicecatalog.amazonaws.com

    This command produces no output when successful.

  • Amazon API: DisableAWSServiceAccess