Skip to content

[AWS GuardDuty] - Updated docs to address data duplication issue when using GuardDuty API #15858

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[AWS GuardDuty] - Updated docs to address data duplication issue when using GuardDuty API #15858

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion packages/aws/_dev/build/docs/guardduty.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,10 @@ The Amazon GuardDuty integration can be used in three different modes to collect
## What do I need to use this integration?

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.
**Note**: It is recommended to use AWS SQS for Amazon GuardDuty.

**Note**:
- It is recommended to use AWS SQS for Amazon GuardDuty.
- When using the Amazon GuardDuty API to collect logs, there is a known issue where data duplication can occur due to certain API limitations.
Copy link
Contributor

@efd6 efd6 Nov 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- When using the Amazon GuardDuty API to collect logs, there is a known issue where data duplication can occur due to certain API limitations.
- When using the Amazon GuardDuty API to collect logs, data duplication can occur due to limitations with the current input.


### Agentless Enabled Integration

Expand Down
5 changes: 4 additions & 1 deletion packages/aws/docs/guardduty.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,10 @@ The Amazon GuardDuty integration can be used in three different modes to collect
## What do I need to use this integration?

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.
**Note**: It is recommended to use AWS SQS for Amazon GuardDuty.

**Note**:
- It is recommended to use AWS SQS for Amazon GuardDuty.
- When using the Amazon GuardDuty API to collect logs, there is a known issue where data duplication can occur due to certain API limitations.

### Agentless Enabled Integration

Expand Down