feat: support guardduty protection features #1018
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
dataSources
in the APIs. However, after March 2023, new GuardDuty protection types are now configured as features and notdataSources
.What
This PR directly adds support for RDS login monitoring, but the component can now configure GuardDuty detection features such as S3 data events, EKS audit logs, RDS login events, EKS runtime monitoring, Lambda network, logs, and EC2 runtime monitoring.
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update
Usage
Testing
Notable comments:
EKS_RUNTIME_MONITORING
) and Runtime Monitoring (RUNTIME_MONITORING
) will cause an error. You can add only one of these two features because Runtime Monitoring already includes the threat detection for Amazon EKS resourcesValidated with
atmos validate stacks
Performed successful
atmos terraform plan
on componentReferences