Repository navigation
feat: add aggregator_regions and aggregator_authorization_region inputs - #143
Open
Elad (hemzaz) wants to merge 1 commit into
Open
Elad (hemzaz) wants to merge 1 commit into
Elad (hemzaz) wants to merge 1 commit into
Conversation
Allow limiting the configuration aggregator to a list of source regions instead of all_regions, and authorizing an aggregator in a region other than global_resource_collector_region. Both default to null, keeping the current behaviour.
Elad (hemzaz)
requested review from
Andriy Knysh (aknysh),
Jeremy White (dudymas) and
PePe Amengual (jamengual)
November 13, 2026 19:37
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
what
aggregator_regions(list(string), defaultnull): when set, the configuration aggregator's account or organization aggregation source usesregions = var.aggregator_regionsinstead ofall_regions = true. The variable is validated to benullor a non-empty list of AWS region names.aggregator_authorization_region(string, defaultnull): when set, theaws_config_aggregate_authorizationresources (childandcentral) authorize an aggregator in this region instead ofglobal_resource_collector_region.global_resource_collector_regionstill decides where global resources such as IAM are recorded and where this module creates the aggregator. The variable is validated to benullor an AWS region name.null, so existing configurations plan exactly as before:all_regions = true,regionsunset, andauthorized_aws_region = global_resource_collector_region.why
all_regions = true, so an aggregator in a US region also pulls EU-region data, and the input to stop that is missing.aggregator_regions, a central account can run one aggregator per residency zone. For example, one aggregator limited to US regions and one limited to EU regions, each deployed as a separate module instance.global_resource_collector_region. Its recorders in other regions currently can only authorize the aggregator in that same region.aggregator_authorization_regionlets such a recorder (for example, ineu-west-1) authorize the EU aggregator instead. That keeps its data inside the EU without moving global-resource recording, which would record IAM twice.disabled_aggregation_regionsand re-create the aggregator and authorization outside the module. These inputs remove that workaround.references
AccountAggregationSource/OrganizationAggregationSourceAwsRegions: https://docs.aws.amazon.com/config/latest/APIReference/API_AccountAggregationSource.htmlaws_config_configuration_aggregator: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/config_configuration_aggregatoraws_config_aggregate_authorization: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/config_aggregate_authorization