DescribeOrganizationConfigurationResponse
¶
Source code in docs_src/capo_guardduty/types/describe_organization_configuration_response.py
auto_enable
instance-attribute
¶
auto_enable: NotRequired[Boolean]
Indicates whether GuardDuty is automatically enabled for accounts added to the organization.
Even though this is still supported, we recommend using AutoEnableOrganizationMembers to achieve the similar results.
auto_enable_organization_members
instance-attribute
¶
auto_enable_organization_members: NotRequired[AutoEnableMembers]
Indicates the auto-enablement configuration of GuardDuty or any of the corresponding protection plans for the member accounts in the organization.
-
NEW: Indicates that when a new account joins the organization, they will have GuardDuty or any of the corresponding protection plans enabled automatically. -
ALL: Indicates that all accounts in the organization have GuardDuty and any of the corresponding protection plans enabled automatically. This includesNEWaccounts that join the organization and accounts that may have been suspended or removed from the organization in GuardDuty. -
NONE: Indicates that GuardDuty or any of the corresponding protection plans will not be automatically enabled for any account in the organization. The administrator must manage GuardDuty for each account in the organization individually.When you update the auto-enable setting from
ALLorNEWtoNONE, this action doesn't disable the corresponding option for your existing accounts. This configuration will apply to the new accounts that join the organization. After you update the auto-enable settings, no new account will have the corresponding option as enabled.
data_sources
instance-attribute
¶
data_sources: NotRequired[OrganizationDataSourceConfigurationsResult]
Describes which data sources are enabled automatically for member accounts.
features
instance-attribute
¶
features: NotRequired[OrganizationFeaturesConfigurationsResults]
A list of features that are configured for this organization.