DisableHealthServiceAccessForOrganization - Amazon Health
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.

DisableHealthServiceAccessForOrganization

Disables Amazon Health from working with Amazon Organizations. To call this operation, you must sign in as an Amazon Identity and Access Management (IAM) user, assume an IAM role, or sign in as the root user (not recommended) in the organization's management account. For more information, see Aggregating Amazon Health events in the Amazon Health User Guide.

This operation doesn't remove the service-linked role from the management account in your organization. You must use the IAM console, API, or Amazon Command Line Interface (Amazon CLI) to remove the service-linked role. For more information, see Deleting a Service-Linked Role in the IAM User Guide.

Note

You can also disable the organizational feature by using the Organizations DisableAWSServiceAccess API operation. After you call this operation, Amazon Health stops aggregating events for all other Amazon Web Services accounts in your organization. If you call the Amazon Health API operations for organizational view, Amazon Health returns an error. Amazon Health continues to aggregate health events for your Amazon Web Services account.

Response Elements

If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.

Errors

For information about the errors that are common to all actions, see Common Errors.

ConcurrentModificationException

EnableHealthServiceAccessForOrganization is already in progress. Wait for the action to complete before trying again. To get the current status, use the DescribeHealthServiceStatusForOrganization operation.

HTTP Status Code: 400

See Also

For more information about using this API in one of the language-specific Amazon SDKs, see the following: