Skip to main content

Component: aws-config

This component is responsible for configuring AWS Config.

AWS Config service enables you to track changes to your AWS resources over time. It continuously monitors and records configuration changes to your AWS resources and provides you with a detailed view of the relationships between those resources. With AWS Config, you can assess, audit, and evaluate the configurations of your AWS resources for compliance, security, and governance purposes.

Some of the key features of AWS Config include:

  • Configuration history: AWS Config maintains a detailed history of changes to your AWS resources, allowing you to see when changes were made, who made them, and what the changes were.
  • Configuration snapshots: AWS Config can take periodic snapshots of your AWS resources configurations, giving you a point-in-time view of their configuration.
  • Compliance monitoring: AWS Config provides a range of pre-built rules and checks to monitor your resources for compliance with best practices and industry standards.
  • Relationship mapping: AWS Config can map the relationships between your AWS resources, enabling you to see how changes to one resource can impact others.
  • Notifications and alerts: AWS Config can send notifications and alerts when changes are made to your AWS resources that could impact their compliance or security posture.
AWS Config Limitations

You'll also want to be aware of some limitations with AWS Config:

  • The maximum number of AWS Config rules that can be evaluated in a single account is 1000.
    • This can be mitigated by removing rules that are duplicated across packs. You'll have to manually search for these duplicates.
    • You can also look for rules that do not apply to any resources and remove those. You'll have to manually click through rules in the AWS Config interface to see which rules are not being evaluated.
    • If you end up still needing more than 1000 rules, one recommendation is to only run packs on a schedule with a lambda that removes the pack after results are collected. If you had different schedule for each day of the week, that would mean 7000 rules over the week. The aggregators would not be able to handle this, so you would need to make sure to store them somewhere else (i.e. S3) so the findings are not lost.
    • See the Audit Manager docs if you think you would like to convert conformance packs to custom Audit Manager assessments.
  • The maximum number of AWS Config conformance packs that can be created in a single account is 50.

Overall, AWS Config provides you with a powerful toolset to help you monitor and manage the configurations of your AWS resources, ensuring that they remain compliant, secure, and properly configured over time.


As part of CIS AWS Foundations 1.20, this component assumes that a designated support IAM role with the following permissions has been deployed to every account in the organization:

"Version": "2012-10-17",
"Statement": [
"Sid": "AllowSupport",
"Effect": "Allow",
"Action": ["support:*"],
"Resource": "*"
"Sid": "AllowTrustedAdvisor",
"Effect": "Allow",
"Action": "trustedadvisor:Describe*",
"Resource": "*"

Before deploying this AWS Config component config-bucket and cloudtrail-bucket should be deployed first.


Stack Level: Regional or Global

This component has a default_scope variable for configuring if it will be an organization-wide or account-level component by default. Note that this can be overridden by the scope variable in the conformance_packs items.

Using the account default_scope

If default_scope == account, AWS Config is regional AWS service, so this component needs to be deployed to all regions. If an individual conformance_packs item has scope set to organization, that particular pack will be deployed to the organization level.

Using the organization default_scope

If default_scope == organization, AWS Config is global unless overriden in the conformance_packs items. You will need to update your org to allow the service access principal for this to work. If you are using our account component, just add that principal to the aws_service_access_principals variable.

At the AWS Organizational level, the Components designate an account to be the central collection account and a single region to be the central collection region so that compliance information can be aggregated into a central location.

Logs are typically written to the audit account and AWS Config deployed into to the security account.

Here's an example snippet for how to use this component:

enabled: true
account_map_tenant: core
az_abbreviation_type: fixed
# In each AWS account, an IAM role should be created in the main region.
# If the main region is set to us-east-1, the value of the var.create_iam_role variable should be true.
# For all other regions, the value of var.create_iam_role should be false.
create_iam_role: false
central_resource_collector_account: core-security
global_resource_collector_region: us-east-1
config_bucket_env: ue1
config_bucket_stage: audit
config_bucket_tenant: core
- name: Operational-Best-Practices-for-CIS-AWS-v1.4-Level2
AccessKeysRotatedParamMaxAccessKeyAge: '45'
- name: Operational-Best-Practices-for-HIPAA-Security.yaml
description: "Checks whether the active access keys are rotated within the number of days specified in maxAccessKeyAge. The rule is NON_COMPLIANT if the access keys have not been rotated for more than maxAccessKeyAge number of days."
maxAccessKeyAge: "30"
enabled: true
tags: { }


Apply to your central region security account

atmos terraform plan aws-config-{central-region} --stack core-{central-region}-security -var=create_iam_role=true

For example when central region is us-east-1:

atmos terraform plan aws-config-ue1 --stack core-ue1-security -var=create_iam_role=true

Apply aws-config to all stacks in all stages.

atmos terraform plan aws-config-{each region} --stack {each region}-{each stage}


terraform>= 1.0.0
aws>= 4.0
awsutils>= 0.16.0


aws>= 4.0




aws_caller_identity.thisdata source
aws_partition.thisdata source
aws_region.thisdata source


account_map_tenant(Optional) The tenant where the account_map component required by remote-state is deployed.string""no
additional_tag_mapAdditional key-value pairs to add to each map in tags_as_list_of_maps. Not added to tags or id.
This is for some rare cases where resources want additional configuration of tags
and therefore take a list of maps with tag key, value, and additional configuration.
attributesID element. Additional attributes (e.g. workers or cluster) to add to id,
in the order they appear in the list. New attributes are appended to the
end of the list. The elements of the list are joined by the delimiter
and treated as a single ID element.
az_abbreviation_typeAZ abbreviation type, fixed or shortstring"fixed"no
central_resource_collector_accountThe name of the account that is the centralized aggregation account.stringn/ayes
config_bucket_envThe environment of the AWS Config S3 Bucketstringn/ayes
config_bucket_stageThe stage of the AWS Config S3 Bucketstringn/ayes
config_bucket_tenant(Optional) The tenant of the AWS Config S3 Bucketstring""no
conformance_packsList of conformance packs. Each conformance pack is a map with the following keys: name, conformance_pack, parameter_overrides.

For example:
conformance_packs = [
name = "Operational-Best-Practices-for-CIS-AWS-v1.4-Level1"
conformance_pack = ""
parameter_overrides = {
"AccessKeysRotatedParamMaxAccessKeyAge" = "45"
name = "Operational-Best-Practices-for-CIS-AWS-v1.4-Level2"
conformance_pack = ""
parameter_overrides = {
"IamPasswordPolicyParamMaxPasswordAge" = "45"

Complete list of AWS Conformance Packs managed by AWSLabs can be found here:
name = string
conformance_pack = string
parameter_overrides = map(string)
scope = optional(string, null)
contextSingle object for setting entire context at once.
See description of individual variables for details.
Leave string and numeric variables as null to use default value.
Individual variable settings (non-null) override settings in context object,
except for attributes, tags, and additional_tag_map, which are merged.
"additional_tag_map": {},
"attributes": [],
"delimiter": null,
"descriptor_formats": {},
"enabled": true,
"environment": null,
"id_length_limit": null,
"label_key_case": null,
"label_order": [],
"label_value_case": null,
"labels_as_tags": [
"name": null,
"namespace": null,
"regex_replace_chars": null,
"stage": null,
"tags": {},
"tenant": null
create_iam_roleFlag to indicate whether an IAM Role should be created to grant the proper permissions for AWS Configboolfalseno
default_scopeThe default scope of the conformance pack. Valid values are account and organization.string"account"no
delegated_accountsThe account IDs of other accounts that will send their AWS Configuration or Security Hub data to this accountset(string)nullno
delimiterDelimiter to be used between ID elements.
Defaults to - (hyphen). Set to "" to use no delimiter at all.
descriptor_formatsDescribe additional descriptors to be output in the descriptors output map.
Map of maps. Keys are names of descriptors. Values are maps of the form
{<br/> format = string<br/> labels = list(string)<br/>}
(Type is any so the map values can later be enhanced to provide additional options.)
format is a Terraform format string to be passed to the format() function.
labels is a list of labels, in order, to pass to format() function.
Label values will be normalized before being passed to format() so they will be
identical to how they appear in id.
Default is {} (descriptors output will be empty).
enabledSet to false to prevent the module from creating any resourcesboolnullno
environmentID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'stringnullno
global_environmentGlobal environment namestring"gbl"no
global_resource_collector_regionThe region that collects AWS Config data for global resources such as IAMstringn/ayes
iam_role_arnThe ARN for an IAM Role AWS Config uses to make read or write requests to the delivery channel and to describe the
AWS resources associated with the account. This is only used if create_iam_role is false.

If you want to use an existing IAM Role, set the variable to the ARN of the existing role and set create_iam_role to false.

See the AWS Docs for further information:
iam_roles_environment_nameThe name of the environment where the IAM roles are provisionedstring"gbl"no
id_length_limitLimit id to this many characters (minimum 6).
Set to 0 for unlimited length.
Set to null for keep the existing setting, which defaults to 0.
Does not affect id_full.
label_key_caseControls the letter case of the tags keys (label names) for tags generated by this module.
Does not affect keys of tags passed in via the tags input.
Possible values: lower, title, upper.
Default value: title.
label_orderThe order in which the labels (ID elements) appear in the id.
Defaults to ["namespace", "environment", "stage", "name", "attributes"].
You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.
label_value_caseControls the letter case of ID elements (labels) as included in id,
set as tag values, and output by this module individually.
Does not affect values of tags passed in via the tags input.
Possible values: lower, title, upper and none (no transformation).
Set this to title and set delimiter to "" to yield Pascal Case IDs.
Default value: lower.
labels_as_tagsSet of labels (ID elements) to include as tags in the tags output.
Default is to include all labels.
Tags with empty values will not be included in the tags output.
Set to [] to suppress all generated tags.
The value of the name tag, if included, will be the id, not the name.
Unlike other null-label inputs, the initial setting of labels_as_tags cannot be
changed in later chained modules. Attempts to change it will be silently ignored.
managed_rulesA list of AWS Managed Rules that should be enabled on the account.

See the following for a list of possible rules to enable:

managed_rules = {
access-keys-rotated = {
identifier = "ACCESS_KEYS_ROTATED"
description = "Checks whether the active access keys are rotated within the number of days specified in maxAccessKeyAge. The rule is NON_COMPLIANT if the access keys have not been rotated for more than maxAccessKeyAge number of days."
input_parameters = {
maxAccessKeyAge : "90"
enabled = true
tags = {}
description = string
identifier = string
input_parameters = any
tags = map(string)
enabled = bool
nameID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.
This is the only ID element not also included as a tag.
The "name" tag is set to the full id string. There is no tag with the value of the name input.
namespaceID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally uniquestringnullno
privilegedTrue if the default provider already has access to the backendboolfalseno
regex_replace_charsTerraform regular expression (regex) string.
Characters matching the regex will be removed from the ID elements.
If not set, "/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits.
regionAWS Regionstringn/ayes
root_account_stageThe stage name for the Organization root (master) accountstring"root"no
stageID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'stringnullno
tagsAdditional tags (e.g. {'BusinessUnit': 'XYZ'}).
Neither the tag keys nor the tag values will be modified by this module.
tenantID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is forstringnullno


aws_config_configuration_recorder_idThe ID of the AWS Config Recorder
aws_config_iam_roleThe ARN of the IAM Role used for AWS Config
storage_bucket_arnStorage Config bucket ARN
storage_bucket_idStorage Config bucket ID