AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Container for the parameters to the DisableAWSServiceAccess operation.
Disables the integration of an Amazon Web Services service (the service that is specified
by
We strongly recommend that you don't use this command to disable integration
between Organizations and the specified Amazon Web Services service. Instead, use
the console or commands that are provided by the specified service. This lets the
trusted service perform any required initialization when enabling trusted access,
such as creating any required resources and any required clean up of resources when
disabling trusted access.
For information about how to disable trusted service access to your organization using
the trusted service, see the Learn more link under the Supports Trusted
Access column at Amazon
Web Services services that you can use with Organizations. on this page.
If you disable access by using this command, it causes the following actions to occur:
The service can no longer create a service-linked role in the accounts in your organization.
This means that the service can't perform operations on your behalf on any new accounts
in your organization. The service can still perform operations in older accounts until
the service completes its clean-up from Organizations.
The service can no longer perform tasks in the member accounts in the organization,
unless those operations are explicitly permitted by the IAM policies that are attached
to your roles. This includes any data aggregation from the member accounts to the
management account, or to a delegated administrator account, where relevant.
Some services detect this and clean up any remaining data or resources related to
the integration, while other services stop accessing the organization but leave any
historical data and configuration in place to support a possible re-enabling of the
integration.
Using the other service's console or commands to disable the integration ensures that
the other service is aware that it can clean up any resources that are required only
for the integration. How the service cleans up its resources in the organization's
accounts depends on that service. For more information, see the documentation for
the other Amazon Web Services service.
ServicePrincipal
) with Organizations. When you disable integration, the
specified service no longer can create a service-linked
role in new accounts in your organization. This means the service can't
perform operations on your behalf on any new accounts in your organization. The service
can still perform operations in older accounts until the service completes its clean-up
from Organizations.
After you perform the DisableAWSServiceAccess
operation, the specified service
can no longer perform operations in your organization's accounts
For more information about integrating other services with Organizations, including the list of services that work with Organizations, see Using Organizations with other Amazon Web Services services in the Organizations User Guide.
This operation can be called only from the organization's management account.
Namespace: Amazon.Organizations.Model
Assembly: AWSSDK.Organizations.dll
Version: 3.x.y.z
public class DisableAWSServiceAccessRequest : AmazonOrganizationsRequest IAmazonWebServiceRequest
The DisableAWSServiceAccessRequest type exposes the following members
Name | Description | |
---|---|---|
![]() |
DisableAWSServiceAccessRequest() |
Name | Type | Description | |
---|---|---|---|
![]() |
ServicePrincipal | System.String |
Gets and sets the property ServicePrincipal.
The service principal name of the Amazon Web Services service for which you want to
disable integration with your organization. This is typically in the form of a URL,
such as |
.NET:
Supported in: 8.0 and newer, Core 3.1
.NET Standard:
Supported in: 2.0
.NET Framework:
Supported in: 4.5 and newer, 3.5