Skip to content

feat(security): add Amazon GuardDuty integration to security service#19

Open
cdaniluk wants to merge 1 commit into
masterfrom
feat/guardduty-integration
Open

feat(security): add Amazon GuardDuty integration to security service#19
cdaniluk wants to merge 1 commit into
masterfrom
feat/guardduty-integration

Conversation

@cdaniluk

Copy link
Copy Markdown
Contributor

What

Adds a native PagerDuty Amazon GuardDuty integration on the existing security service (alongside the Datadog integration) and exposes its Events API URL as a new output security_guardduty_integration_url.

Why

Lets us deliver full GuardDuty finding payloads to PagerDuty via an EventBridge → SNS path (one incident per finding), replacing Datadog log forwarding that rolled unrelated findings into a single, payload-stripped alert. Structured to extend to AWS Security Hub later.

Changes

  • data.tf: pagerduty_vendor.guardduty ("Amazon GuardDuty")
  • security.tf: pagerduty_service_integration.security_guardduty on pagerduty_service.security
  • output.tf: security_guardduty_integration_url
  • README.md: regenerated via terraform-docs

Release

Pre-released as v0.8.6-rc1 for consumption by managed-rhythmic. Cut v0.8.6 on merge.

Test

terraform validate passes (only the pre-existing pagerduty_business_service.type deprecation warning). Consumed end-to-end from managed-rhythmic via local module override.

🤖 Generated with Claude Code

Adds a native PagerDuty "Amazon GuardDuty" integration on the existing
security service alongside the Datadog integration, and exposes its
Events API URL as security_guardduty_integration_url. This lets an
EventBridge -> SNS path deliver full GuardDuty finding payloads to
PagerDuty (one incident per finding), replacing the Datadog log
forwarding that rolled findings up and stripped the payload. Structured
to extend to AWS Security Hub later.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cdaniluk cdaniluk requested a review from a team as a code owner June 24, 2026 21:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants