aws-samples / aws-samples/aws-control-tower-config-customization

AWS AutoScaling AutoScalingGroup and AWS AutoScaling LaunchConfiguration are recorded despite using include

Closed
#41 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
52
Forks
51
Avg merge
2m
Merged PRs (30d)
4

Description

Hello,
I am on Landing Zone 4.0
I just configured the stack with the following parameters:
{
"AccountSelectionMode": "EXCLUSION",
"ExcludedAccounts": "['XXXXXXXX5431', 'XXXXXXXX4052', 'XXXXXXXX7336']",
"IncludedAccounts": "[]",
"ConfigRecorderStrategy": "INCLUSION",
"ConfigRecorderIncludedResourceTypes": "AWS::S3::Bucket",
"ConfigRecorderDefaultRecordingFrequency": "DAILY",
"ConfigRecorderDailyGlobalResourceTypes": "AWS::IAM::Policy,AWS::IAM::User,AWS::IAM::Role,AWS::IAM::Group"
}

I can confirm everything works as excepted.
The IAM resources are recorded in Frankfurt, our Home region.
The only problem I found, that beside S3, both resource types:
AWS AutoScaling AutoScalingGroup
AWS AutoScaling LaunchConfiguration

are recorded. Not sure why?
Any idea?

Thanks!

Contributor guide

Open the contributing guide

Research direction

Start by reviewing how ConfigRecorderStrategy and ConfigRecorderIncludedResourceTypes are parsed and applied, then reproduce the configuration with only AWS::S3::Bucket included. Confirm whether AutoScaling resources are intentionally default-recorded or identify the configuration behavior that causes them to appear; done means the behavior is explained and, if incorrect, verified against the intended inclusion list.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.