aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

[AWS::GuardDuty::Filter] - [Coverage] - add support for Matches and NotMatches operators

Open
#2,499 0 comments 1 reaction 0 assignees View on GitHub
Coverage
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::GuardDuty::Filter

### Resource name

_No response_

### Description

Currently, the Matches and NotMatches operators are not supported when defining AWS::GuardDuty::Filter resources via CloudFormation.
These operators are essential for creating flexible suppression rules.

References:
https://docs.aws.amazon.com/guardduty/latest/ug/create-suppression-rules-guardduty.html
https://docs.aws.amazon.com/guardduty/latest/APIReference/API_Condition.html#:~:text=Required%3A%20No-,matches,-Represents%20the%20match

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the two linked AWS GuardDuty documentation pages and inspect this repository's coverage-roadmap conventions for AWS::GuardDuty::Filter. Determine how Matches and NotMatches are tracked here and what validation or implementation repository is involved. Done means support for both operators is documented or implemented according to the project's established process.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.