Skip to content

feat: add aggregator_regions and aggregator_authorization_region inputs - #143

Open
Elad (hemzaz) wants to merge 1 commit into
cloudposse:mainfrom
hemzaz:feat/aggregator-regions
Open

Elad (hemzaz) wants to merge 1 commit into
cloudposse:mainfrom
hemzaz:feat/aggregator-regions

Conversation

@hemzaz

Copy link
Copy Markdown

what

  • Add aggregator_regions (list(string), default null): when set, the configuration aggregator's account or organization aggregation source uses regions = var.aggregator_regions instead of all_regions = true. The variable is validated to be null or a non-empty list of AWS region names.
  • Add aggregator_authorization_region (string, default null): when set, the aws_config_aggregate_authorization resources (child and central) authorize an aggregator in this region instead of global_resource_collector_region. global_resource_collector_region still decides where global resources such as IAM are recorded and where this module creates the aggregator. The variable is validated to be null or an AWS region name.
  • Both default to null, so existing configurations plan exactly as before: all_regions = true, regions unset, and authorized_aws_region = global_resource_collector_region.
  • README inputs table updated with the two new rows.

why

  • Data residency (for example, GDPR) can require that AWS Config data from one set of regions is aggregated only within those regions. Today the aggregator always uses all_regions = true, so an aggregator in a US region also pulls EU-region data, and the input to stop that is missing.
  • With 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.
  • A member account records global resources (IAM) once, in its global_resource_collector_region. Its recorders in other regions currently can only authorize the aggregator in that same region. aggregator_authorization_region lets such a recorder (for example, in eu-west-1) authorize the EU aggregator instead. That keeps its data inside the EU without moving global-resource recording, which would record IAM twice.
  • Today this needs a workaround: disable the module's aggregation through disabled_aggregation_regions and re-create the aggregator and authorization outside the module. These inputs remove that workaround.

references

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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Needs triage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant