GuardDuty
Protocol: REST JSON
Endpoint: http://localhost:4566
Floci implements the GuardDuty detector management lifecycle, organization-configuration readback, and Malware Protection plans for local SDK, CLI, Terraform and CloudFormation workflows. Detectors and plans are isolated by account and region and use the configured Floci storage mode.
Supported Operations
| Operation | Method and path | Description |
|---|---|---|
CreateDetector |
POST /detector |
Create the account's detector (one per account and region) |
GetDetector |
GET /detector/{detectorId} |
Return detector status, frequency, features, and tags |
UpdateDetector |
POST /detector/{detectorId} |
Update status, frequency, and features |
DeleteDetector |
DELETE /detector/{detectorId} |
Delete the detector |
ListDetectors |
GET /detector |
List detector IDs with pagination |
DescribeOrganizationConfiguration |
GET /detector/{detectorId}/admin |
Return organization auto-enablement configuration |
UpdateOrganizationConfiguration |
POST /detector/{detectorId}/admin |
Update organization auto-enablement configuration |
EnableOrganizationAdminAccount |
POST /admin/enable |
Designate the delegated administrator account |
DisableOrganizationAdminAccount |
POST /admin/disable |
Remove the delegated administrator account |
ListOrganizationAdminAccounts |
GET /admin |
List the delegated administrator account |
CreateMembers |
POST /detector/{detectorId}/member |
Create GuardDuty member accounts for a detector |
ListMembers |
GET /detector/{detectorId}/member |
List detector members with pagination and association filtering |
CreateMalwareProtectionPlan |
POST /malware-protection-plan |
Create a Malware Protection plan for an S3 bucket |
GetMalwareProtectionPlan |
GET /malware-protection-plan/{malwareProtectionPlanId} |
Return a plan's role, protected bucket, actions, status, and tags |
UpdateMalwareProtectionPlan |
PATCH /malware-protection-plan/{malwareProtectionPlanId} |
Update a plan's role, object prefixes, and tagging action |
DeleteMalwareProtectionPlan |
DELETE /malware-protection-plan/{malwareProtectionPlanId} |
Delete a plan |
ListMalwareProtectionPlans |
GET /malware-protection-plan |
List plan ids with pagination |
CreatePublishingDestination |
POST /detector/{detectorId}/publishingDestination |
Create an S3 findings export destination |
DescribePublishingDestination |
GET /detector/{detectorId}/publishingDestination/{destinationId} |
Return the destination's properties and status |
UpdatePublishingDestination |
POST /detector/{detectorId}/publishingDestination/{destinationId} |
Update the destination ARN or KMS key ARN |
DeletePublishingDestination |
DELETE /detector/{detectorId}/publishingDestination/{destinationId} |
Delete the destination |
ListPublishingDestinations |
GET /detector/{detectorId}/publishingDestination |
List destinations with pagination |
TagResource |
POST /tags/{resourceArn} |
Add tags to a detector or Malware Protection plan |
UntagResource |
DELETE /tags/{resourceArn} |
Remove tags from a detector or Malware Protection plan |
ListTagsForResource |
GET /tags/{resourceArn} |
List detector or Malware Protection plan tags |
Feature lists and each feature's additionalConfiguration list are returned in the order
they were submitted, so Terraform's ordered list blocks re-plan cleanly. A missing detector
is reported as BadRequestException with the exact message the Terraform AWS provider
matches for not-found detection, mirroring AWS.
Malware Protection plans
Plans are management plane only. Floci stores the plan and answers the five operations above, and
AWS::GuardDuty::MalwareProtectionPlan is provisioned from CloudFormation (Ref and
Fn::GetAtt MalwareProtectionPlanId are the plan id; Arn, CreatedAt, Status and
StatusReasons are also set). No object is scanned, no GuardDutyMalwareScanStatus tag is written,
and no scan-result event is published, so a plan stays ACTIVE with no status reasons.
A bucket has at most one plan per account and region: a second CreateMalwareProtectionPlan for
the same bucket fails with ConflictException, unless it repeats the earlier request's
clientToken, which returns the existing plan. The bucket cannot be changed on an existing plan;
UpdateMalwareProtectionPlan changes the role, object prefixes (at most 5), and the tagging action.
The role must be an IAM role ARN. An update is applied all-or-nothing: if any supplied field is invalid, none of them are stored.
ListMalwareProtectionPlans returns up to 100 ids per page, and its nextToken survives plans being created or deleted between pages. In a CloudFormation stack, dropping ObjectPrefixes or Actions from the template clears them on the plan, and a failed stack update restores the plan's previous role, prefixes, tagging action and tags.
Plan tag keys follow GuardDuty's TagKey pattern (no aws: prefix, no spaces), and the tag
routes accept a plan's ARN only when it matches the stored plan's exactly, account and partition
included. The plan routes are served only to requests signed for guardduty, by the Authorization
header or the X-Amz-Credential query parameter, so a path-style S3 request for a bucket named
malware-protection-plan still reaches S3.
Publishing destinations
Publishing destinations report PUBLISHING as soon as they are created: Floci does not
verify the bucket or key, and no findings are exported to it.
Configuration
| Variable | Default | Description |
|---|---|---|
FLOCI_SERVICES_GUARDDUTY_ENABLED |
true |
Enable or disable GuardDuty |
FLOCI_STORAGE_SERVICES_GUARDDUTY_MODE |
(inherits global) | Optional GuardDuty storage-mode override |
FLOCI_STORAGE_SERVICES_GUARDDUTY_FLUSH_INTERVAL_MS |
5000 |
Hybrid storage flush interval in milliseconds |
Unless a GuardDuty-specific override is set, detector state follows the global
FLOCI_STORAGE_MODE setting. Persistent, hybrid, and write-ahead-log modes restore
detectors across restarts.
Example
export AWS_ENDPOINT_URL=http://localhost:4566
DETECTOR_ID=$(aws guardduty create-detector \
--enable \
--finding-publishing-frequency SIX_HOURS \
--tags env=local \
--query DetectorId --output text)
aws guardduty get-detector --detector-id "$DETECTOR_ID"
aws guardduty list-detectors
aws guardduty update-organization-configuration \
--detector-id "$DETECTOR_ID" \
--auto-enable-organization-members ALL
aws guardduty describe-organization-configuration --detector-id "$DETECTOR_ID"
aws guardduty delete-detector --detector-id "$DETECTOR_ID"
Current Scope
- Detector status, finding-publishing frequency, features (including
additionalConfigurationsub-features), tags, and timestamps are modeled. - Organization semantics are readback-only. Floci has no Organizations service, so
adminAccountIdmembership is not validated, delegated-administrator permissions are not enforced on the organization endpoints, and auto-enablement is never fanned out to member accounts. Organization configuration is stored per calling account and echoed back as submitted — sufficient for Terraform'saws_guardduty_organization_configuration,aws_guardduty_organization_configuration_feature, andaws_guardduty_organization_admin_accountresources in a single-account workflow. - No findings are generated: detection, malware scans, and the findings APIs
(
ListFindings,GetFindings, filters, and publishing destinations) are not implemented. - Member creation and listing are implemented. Invitation, IP-set, threat-intel, and coverage APIs are not implemented.
- The deprecated
dataSourcesrequest/response structures are not modeled; the Terraform provider treats their absence as "not configured".