You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe. AWS Security HUB, into PCI DSS v3.2.1 check has failed with:
"Config.1", "AWS Config should be enabled and use the service-linked role for resource recording".
Even though when terraform-aws-config is rightly configure and working.
The problem happens because this module creates a new role instead of using the one provided by aws.
Describe the solution you'd like
We could add an option to this module for giving the user the choice to opt for aws service-linked role (default) or to create a new one. The image in additional context shows the data governance area of aws config edit page.
When using this module, the "choose a role from your account" is marked, making AWS Security Hub fail.
Describe alternatives you've considered Disable control of this check in AWS Security Hub.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
AWS Security HUB
, intoPCI DSS v3.2.1
check has failed with:"Config.1", "AWS Config should be enabled and use the service-linked role for resource recording".
Even though when
terraform-aws-config
is rightly configure and working.The problem happens because this module creates a new role instead of using the one provided by aws.
Describe the solution you'd like
We could add an option to this module for giving the user the choice to opt for aws service-linked role (default) or to create a new one. The image in additional context shows the
data governance
area of aws config edit page.When using this module, the "choose a role from your account" is marked, making AWS Security Hub fail.
Describe alternatives you've considered
Disable control
of this check in AWS Security Hub.Additional context
The text was updated successfully, but these errors were encountered: