Smaws_Client_ConfigService.PutConfigurationAggregatorval request :
Smaws_Lib.Context.t ->
put_configuration_aggregator_request ->
(put_configuration_aggregator_response,
[> Smaws_Lib.Protocols.AwsJson.error
| `InvalidParameterValueException of invalid_parameter_value_exception
| `InvalidRoleException of invalid_role_exception
| `LimitExceededException of limit_exceeded_exception
| `NoAvailableOrganizationException of no_available_organization_exception
| `OrganizationAccessDeniedException of
organization_access_denied_exception
| `OrganizationAllFeaturesNotEnabledException of
organization_all_features_not_enabled_exception ])
Stdlib.resultCreates and updates the configuration aggregator with the selected source accounts and regions. The source account can be individual account(s) or an organization.
accountIds that are passed will be replaced with existing accounts. If you want to add additional accounts into the aggregator, call DescribeConfigurationAggregators to get the previous accounts and then append new ones.
Config should be enabled in source accounts and regions you want to aggregate.
If your source type is an organization, you must be signed in to the management account or a registered delegated administrator and all the features must be enabled in your organization. If the caller is a management account, Config calls EnableAwsServiceAccess API to enable integration between Config and Organizations. If the caller is a registered delegated administrator, Config calls ListDelegatedAdministrators API to verify whether the caller is a valid delegated administrator.
To register a delegated administrator, see Register a Delegated Administrator in the Config developer guide.
PutConfigurationAggregator is an idempotent API. Subsequent requests won’t create a duplicate resource if one was already created. If a following request has different tags values, Config will ignore these differences and treat it as an idempotent request of the previous. In this case, tags will not be updated, even if they are different.