Amazon CloudWatch and Amazon Organizations - Amazon Organizations
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 CloudWatch and Amazon Organizations

You can use Amazon Organizations for Amazon CloudWatch for the following use cases:

  • Discover and understand the state of telemetry configuration for your Amazon resources from a central view in the CloudWatch console. This simplifies the process of auditing your telemetry collection configurations for multiple resource types across your Amazon organization or account. You must turn on trusted access to use telemetry config across your organization.

    For more information, see Auditing CloudWatch telemetry configurations in the Amazon CloudWatch User Guide.

  • Work with multiple accounts in Network Flow Monitor, a feature of Amazon CloudWatch Network Monitoring. Network Flow Monitor provides near real-time visibility into network performance for traffic between Amazon EC2 instances. After you turn on trusted access to integrate with Organizations, you can create a monitor to visualize network performance details across multiple accounts.

    For more information, see Initialize Network Flow Monitor for multi-account monitoring in the Amazon CloudWatch User Guide.

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

Service-linked roles created when you enable integration

Create the following service-linked role in your organization's management account. The service-linked role is automatically created in member accounts when you enable trusted access. This role allows CloudWatch to perform supported operations within your organization's accounts in your organization. You can delete or modify this role only if you disable trusted access between CloudWatch and Organizations, or if you remove the member account from the organization.

  • AWSServiceRoleForObservabilityAdmin

Service principals used by the service-linked roles

The service-linked role in the previous section can be assumed only by the service principals authorized by the trust relationships defined for the role. The service-linked roles used by CloudWatch grant access to the following service principals:

  • observabilityadmin.amazonaws.com

  • networkflowmonitor.amazonaws.com

  • topology.networkflowmonitor.amazonaws.com

Enabling trusted access with CloudWatch

For information about the permissions that you need to turn on trusted access, see Permissions required to enable trusted access.

You can enable trusted access using either the Amazon CloudWatch console or the Amazon Organizations console.

Important

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

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

To turn on trusted access using the CloudWatch console

See Turning on CloudWatch telemetry auditing in the Amazon CloudWatch User Guide.

When you turn on trusted access in CloudWatch, you enable telemetry auditing and you can work with multiple accounts in Network Flow Monitor.

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

  4. Choose Enable trusted access.

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

  6. If you are the administrator of only Amazon Organizations, tell the administrator of Amazon CloudWatch that they can now enable that service to work with Amazon Organizations from the service console .

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

Use the following Amazon CLI commands or API operations to enable trusted service access:

  • Amazon CLI: enable-aws-service-access

    Run the following command to enable Amazon CloudWatch as a trusted service with Organizations.

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

    This command produces no output when successful.

  • Amazon API: EnableAWSServiceAccess

Turn off trusted access with CloudWatch

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

You can disable trusted access using either the Amazon CloudWatch or the Amazon Organizations tools.

Important

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

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

To turn off trusted access using the CloudWatch console

See Turning off CloudWatch telemetry auditing in the Amazon CloudWatch User Guide

When you turn off trusted access in CloudWatch, telemetry auditing is no longer active and you can no longer work with multiple accounts in Network Flow Monitor.

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

Use the following Amazon CLI commands or API operations to disable trusted service access:

  • Amazon CLI: disable-aws-service-access

    Run the following command to disable Amazon CloudWatch as a trusted service with Organizations.

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

    This command produces no output when successful.

  • Amazon API: DisableAWSServiceAccess

Registering a delegated administrator account for CloudWatch

When you register a member account as a delegated administrator account for the organization, users and roles from that account can perform administrative actions for CloudWatch that otherwise can be performed only by users or roles signed in with the organization's management account. Using a delegated administrator account helps you to separate management of the organization from management of features in CloudWatch.

Minimum permissions

Only an administrator in the Organizations management account can register a member account as a delegated administrator account for CloudWatch in the organization.

You can register a delegated administrator account using the CloudWatch console, or by using the Organizations RegisterDelegatedAdministrator API operation with the Amazon Command Line Interface or an SDK.

For information on how to register a delegated administrator account by using the CloudWatch console, see Turning on CloudWatch telemetry auditing in the Amazon CloudWatch User Guide.

When you register a delegated administrator account in CloudWatch, you can use the account for management operations with telemetry auditing and with Network Flow Monitor.

Deregister a delegated administrator for CloudWatch

Minimum permissions

Only an administrator signed in with the Organizations management account can deregister a delegated administrator account for CloudWatch in the organization.

You can deregister the delegated administrator account by using either the CloudWatch console, or by using the Organizations DeregisterDelegatedAdministrator API operation with the Amazon Command Line Interface or an SDK. For more information, see Deregistering a delegated administrator account in the Amazon CloudWatch User Guide.

When you deregister a delegated administrator account in CloudWatch, you can no longer use the account for management operations with telemetry auditing and with Network Flow Monitor.