cloudformation-coverage-roadmap
cloudformation-coverage-roadmap copied to clipboard
AWS::Config::ConfigRule support tagging
-
Title -> AWS::Config::ConfigRule
-
Scope of request -> Cloudformation resource AWS::Config::ConfigRule doesn't appear to support tags (but the API and CLI do support tags).
-
Expected behavior -> It should be possible to tag a config rule (as the IAM conditions for PutConfigRule are based on tags).
-
Test case recommendation (optional)
-
Links to existing API doc (optional) -> PutConfigRule API - https://docs.aws.amazon.com/config/latest/APIReference/API_PutConfigRule.html#config-PutConfigRule-request-Tags CFN Config Rule - https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-config-configrule.html
-
Category tag (optional) -> Management
-
Any additional context (optional)
Any news about this one? Having tags helps a lot to protect some organization-wide rules from being modified while having the freedom to add additional rules in the local account.
Hi team,
Any news? Tags are essential to manage and organize rules.
Any news here? It would be great to have that feature to secure organization-wide rules via SCP without the need to deploy a custom resource to tag the rules
Any news, if this issue is going to be planned on the roadmap? We definitely need this feature.
What do i need to do to get this issue prioritise :)
Hi, This has been opened for a long time already. Any news regarding when this will be supported by CFN? Thanks.
Any updates guys... We are blocked and we are building always alternate solutions which are pretty complex and the tagging could just solve the issue.
Is there an update on this one? It is been a year since the last comment
Any news here? It would be great to have that feature to secure organization-wide rules via SCP without the need to deploy a custom resource to tag the rules
Exactly. Stuck between a rock and a hard place when org rules (which can be protected in a security account) don't support remediation, but local rules (which run locally in less-trusted accounts) do not support protection from modification via SCP.