Amazon Config and Amazon Organizations - Amazon Organizations
Service-linked rolesEnable 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 Config and Amazon Organizations

Multi-account, multi-region data aggregation in Amazon Config enables you to aggregate Amazon Config data from multiple accounts and Amazon Web Services Regions into a single account. Multi-account, multi-region data aggregation is useful for central IT administrators to monitor compliance for multiple Amazon Web Services accounts in the enterprise. An aggregator is a resource type in Amazon Config that collects Amazon Config data from multiple source accounts and Regions. Create an aggregator in the Region where you want to see the aggregated Amazon Config data. While creating an aggregator, you can choose to add either individual account IDs or your organization. For more information about Amazon Config, see the Amazon Config Developer Guide.

You can also use Amazon Config APIs to manage Amazon Config rules across all Amazon Web Services accounts in your organization. For more information, see Enabling Amazon Config Rules Across All Accounts in Your Organization in the Amazon Config Developer Guide.

Use the following information to help you integrate Amazon Config with Amazon Organizations.

Service-linked roles created when you enable integration

The following service-linked role is created in your organization's accounts when you enable trusted access. This role allows Amazon Config to perform supported operations within the accounts in your organization.

  • AWSServiceRoleForConfig

This role is created when you enable Amazon Config in your organization by creating a multi-account aggregator. Amazon Config asks you to select or create a role and for you to provide the name. There is no automatically generated name.

You can delete or modify this role only if you disable trusted access between Amazon Config and Organizations, or if you remove the member account from the organization.

Enabling trusted access with Amazon Config

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

Important

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

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

To enable trusted access using the Amazon Config console

To enable trusted access to Amazon Organizations using Amazon Config, create a multi-account aggregator and add the organization. For information on how to configure a multi-account aggregator, see Setting up an aggregator using the console in the Amazon Config Developer Guide.

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 Config in the list of services.

  4. Choose Enable trusted access.

  5. In the Enable trusted access for Amazon Config 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 Config 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 Config as a trusted service with Organizations.

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

    This command produces no output when successful.

  • Amazon API: EnableAWSServiceAccess

Disabling trusted access with Amazon Config

For information about the permissions needed to disable trusted access, see Permissions required to disable trusted access.

You can disable trusted access using only the Organizations tools.

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

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 Config as a trusted service with Organizations.

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

    This command produces no output when successful.

  • Amazon API: DisableAWSServiceAccess